Keep project knowledge in docs

What belongs in docs

• A project brief. What you’re building, who it’s for, and what matters most.
• Decisions. What you decided and why, so no agent undoes it later.
• Plans and specs for bigger features. Claude Code’s guide suggests writing a spec first, then starting a fresh conversation to build it, because “you have a written spec to reference.”
• Handoff notes when you stop in the middle of something. See Start fresh when a conversation gets long.
• Style and tone. Brand colors, voice, words to avoid.

Short rules that apply to every task belong in your project’s Instructions instead. Enjoy sends those with every conversation, while an agent reads a doc only when it needs it. See Write instructions your agent will follow.

How to do it in Enjoy

1. Ask an agent to write it. “Write a doc called ‘Decisions’ listing what we’ve decided so far and why.” Agents can create and update docs with Enjoy’s tools, and the doc appears in Files, under Your documents.
2. Or write it yourself. In Files, select New file, then Markdown file. If a dialog asks where to save it, choose Your documents as the Location.
3. Point agents to it. Type @ in a message and choose the doc under Docs. Enjoy adds a link to the doc. Ask the agent to read it: “Read @Decisions before you start.” You can also name a doc in your project’s Instructions, like “Our colors are in the doc ‘Brand guide’.”
4. Keep it current. After a decision, ask: “Add today’s decision about the checkout to the ‘Decisions’ doc.”
5. Pin the ones you use most. Select Pin document in the doc, and it appears as a shortcut next to the Conversations, Files, and Workflows tabs.
6. Archive what’s out of date. Choose Archive document from the doc’s Document actions menu. Agents no longer see it when they list your docs, and it leaves the @ list. You can restore it from Archived at the end of Your documents.

An example

You’ve spent a week shaping a booking system. You send: “Write a doc called ‘Booking system’ covering how booking works now, the rules we agreed on, like no refunds within 24 hours, and what’s still to do.”

A month later, in a new conversation: “Read @Booking system, then add a waitlist when a class is full. Follow the rules in the doc.”

Common pitfalls

• Expecting agents to read docs on their own. Enjoy doesn’t hand docs to agents automatically. Mention them, or point to them in your instructions.
• Letting docs go stale. An outdated doc misleads every agent that reads it. Update or archive it.
• One giant doc. Several focused docs are easier to keep current and quicker for an agent to read.
• Passwords or keys in docs. Agents send what they read to your AI provider. See Keep passwords and API keys safe.

Good to know

By default, docs are saved in Enjoy’s own storage for the project, outside your project folder, so they aren’t part of your code’s Git history. See Choose where a project’s conversations are stored.