Playbooks

A playbook is a set of rules a person wants followed on their projects. Each play says do it this way, not that way, with the reason and where it applies. Every role that writes or judges code reads the plays. Four sources, in precedence order:

1. The person's own file, ~/.claude/aida/playbook.md. Their preferences, on every project.
2. The project's own file, <projectPath>/playbook.md. What this project decided.
3. Each folder the project declares as a source of playbooks, in the order it declared them. The folder holds playbook.md at its root, in the format below. The project skill's add-source <target> playbooks <folder> declares one. A team with one shared set of plays puts it here: the person's file is per machine and the project's file is per project.
4. Catalog sets, one per framework the project declares, recorded in project.json under playbookSubscriptions. The project skill's subscribe-playbook writes one.

A play's id is its source and its title as a slug, so a play from a folder carries that folder's path. Open the file the id names to read the play in full.