Context
context/ holds what every session must know about the product. Each session reads it, so you say each fact once.
| File | It holds |
|---|---|
positioning.md | Who it is for, the problem, what it replaces and what it is not |
non-goals.md | What the product will not do, and why |
glossary.md | One word for each thing. Agents use these words. |
decisions/ | One file for each decision that is hard to change, with its reason |
rules/ | How to work on this product. A rule gives its reason. |
#Who changes it
context/ changes rarely. Three things change it.
- You.
accept, when you accept a change task.- The session for the direction, because you decide each item in it.
All other sessions write each change under ## Context changes of the task:
- The file
- The old text, when there is one
- The new text
- The reason
So build can propose a rule, and you decide when you accept the task.
#What goes in it
Keep a fact in its task. Promote it only when a future task will get it wrong without the fact. A rule that nobody needs makes every session slower.
#Rules that come with the hub
| Rule | It says |
|---|---|
how-we-build.md | The stages and their prompts |
interface-skills.md | When an agent must run each interface skill |
working-with-the-person.md | One decision in each turn, and how to show an edit |
writing.md | Plain English, in short sentences |
ui.md | A page follows the wireframe of its task |
workflow-files.md | What a build can change in workflow files |