Documents

Use documents for scripts, specifications, references, and delivery requirements so written content can continue evolving with the project.

What they are

Project documents keep written material that should remain with the project instead of one conversation. You and the Agent can continue reading, editing, and referring to the same content.

Written project content has three distinct roles:

• Ordinary documents: store scripts, character settings, references, delivery specifications, and task notes.
• AGENTS.md: records durable collaboration and production rules for the current project.
• Skill: stores a creation method the Agent can invoke and reuse across projects.

What you can do

• Create and edit Markdown documents inside a project.
• Upload existing documents as read-only references.
• Add a document to the current message so the Agent can work from it.
• Ask the Agent to create, organize, or update ordinary documents and AGENTS.md.
• Turn a stable method into a Skill without treating one-time story details as durable rules.

How to use them

1. In List, select + in the upper-right corner of Project Files and choose New Empty Document. You can also right-click an empty area on Canvas.
2. Name the document and add the script, settings, references, or delivery requirements.
3. Select it in List or Canvas to read and edit it. Use its action menu to rename or move it.
4. When the Agent should use a document, refer to it in the current message and then describe the task.
5. If a method should be reused across projects, ask the Agent to create a Skill from the current experience.

Tips

• Ordinary documents answer “what is in this project,” AGENTS.md answers “how should this project work over time,” and a Skill answers “how should this kind of project usually be made.”
• Keeping a document in the project does not automatically select it for the current message. Refer to it when it is needed.
• Do not turn a one-time task or changing story detail into a durable rule.
• Pasting external Skill content into an ordinary document does not enable it as a Skill.

Related features

• Refer to Project Content: add a project document to the current message.
• Create and Manage Skills: turn a reusable method into a Skill.
• Multiple Conversations: share the same project documents across separate conversations.