Editing Camelia's behavior with per-project directives

You can shape how Camelia works on a given project by editing its directives — a per-project instruction layer she reads on every request.

Where directives live

Each project stores user-editable directives in its Misc folder (camelia-directives.md). This file is part of your project's encrypted document backbone, so it travels with the project and only applies there.

How they fit into Camelia's prompt

Camelia's instructions are composed in layers: her core identity, capabilities, and routing; her operating principles; the invention and build rubric she evaluates ideas against; and finally your per-project directives. Because your directives are a dedicated layer, they let you steer her without fighting her core behavior.

What to put in them

Use directives for things that should hold true across the whole project — for example, the tone or format you prefer for documents, constraints she should always respect, terminology or naming conventions, or priorities for how she approaches the work. Since directives are just a markdown document in Documents, you can edit them in the file browser or the in-browser IDE, and Camelia herself can update documents on your behalf.

Tips

• Keep directives concise and specific; they're guidance layered on top of her existing rubric, not a full rewrite of it.
• Because they're per-project, you can give each project its own voice and constraints.
• Remember they steer behavior but don't override the safety gates — actions like deleting a document or running an external write still require your approval, regardless of what the directives say.

Updating directives is the cleanest way to make Camelia consistently behave the way you want inside a specific project.