Projects

Real work rarely fits in one chat. A product launch means a pricing question on Monday, launch copy on Tuesday and a sales one-pager on Thursday. A project groups those chats together with the files, prompts and instructions they share. Every chat you start inside the project already knows the context, so you stop pasting the same brief into every conversation.

app.stickyprompts.com/projects

Create a project

1. Open Projects and choose New project

   Go to Projects in the left sidebar and select New project.

2. Name it and describe it

   Use a name the whole team will recognise, such as Northwind Launch, and a one-line description of the goal: Everything for the 6 October launch: copy, assets, pricing and the sales push. The description shows on the project card.

3. Add the context

   Open the project and fill in the tabs that matter: upload the key Files, add the Prompts you will reuse, and write the project instructions under Configuration. Each is described below.

4. Start chatting

   Type into Start new chat in Northwind Launch at the top of the project. The chat is created inside the project and picks up its context.

Inside a project

app.stickyprompts.com/projects/109 1 New chats land in the project 2 Project instructions 3 Invite colleagues

Tab	What it holds
Chats	Every chat in the project, newest first, with a search box to find one by title or content. Each chat is tagged with the project name.
Files	Documents the project’s chats can refer to: the brief, the price list, the brand guide.
Prompts	Saved prompts that belong to this piece of work.
Configuration	The project instructions: standing guidance that applies to every chat in the project.
Share	Who else can see and work in the project.

The composer at the top works like the one on the home page: Attach files, pick a knowledge base or an agent, set the reasoning effort and choose the model before you Send.

Write good project instructions

Project instructions are the brief you would otherwise repeat at the start of every chat. Keep them to the facts and rules that hold for the whole piece of work. For Northwind Launch:

We are launching Northwind Analytics on Tuesday 6 October 2026.
Audience: operations and finance leads at retailers with 10-200 stores.
Plans: Growth (up to 15 stores) and Scale (up to 60 stores).

Always write in the Northwind brand voice: warm, direct, no jargon.
Never promise features that are not in the launch scope.
If a question needs numbers we have not given you, say so and ask.

Now a question like “Which plan should we pitch to a 42-store chain?” gets an answer grounded in your plans, not a generic one: pitch Scale, because Growth stops at 15 stores.

Move an existing chat into a project

Started a chat before you created the project? Chats can be moved into a project later, and from then on they appear under the project’s Chats tab. See Search, history and sharing.

Share a project

Use the Share tab to bring colleagues in. Everyone works from the same files, prompts and instructions, so the copywriter and the sales lead get answers built on the same brief.

Projects, knowledge bases or agents?

Use a…	When
Project	You have one piece of work with a start and an end: a launch, a tender, a quarterly plan.
Knowledge base	You have a lasting set of documents many chats and agents should search and cite, such as a help center.
Agent	You want a reusable role - a support triager, a researcher - that behaves the same way every time.

They combine well: a project chat can use a knowledge base or an agent from the composer.

Related