A personal assistant that keeps each user’s memory, tools, secrets, and automations isolated.
Kody's 73-line root file is an index to contributor docs and skills. It names one validation command, requires new product areas to follow earlier decisions, and sends preview testing and cloud-agent setup to their own guides.
├── ├── .agents │ └── skills │ ├── control-kody │ │ └── │ ├── preview-manual-test │ │ └── │ ├── remix │ │ └── │ └── visual-recap │ └── └── docs ├── contributing │ ├── architecture │ │ ├── │ │ └── │ ├── decisions │ │ └── │ ├── setup │ │ └── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ └── └── use └──
01 / Pointing at the source of truth
The index names a single validation command instead of repeating the individual checks it contains. Contributors have one place to start, while detailed setup and testing guidance remains in linked documents.
Source excerpt starting at line 7.`npm run validate` is the single authoritative local gate.
02 / Router files
Decision records are presented as a list of steering vetoes, with a trigger to read them before proposing a primitive or surface. This routes design work through earlier constraints before implementation starts.
Source excerpt starting at line 18.- Decision records (steering veto list — open before proposing a new primitive or surface): [docs/contributing/decisions/index.md](./docs/contributing/decisions/index.md)
03 / Router files
Medium- and high-risk work gets manual preview testing with a logged-in user and real data. The index links both the contributor doc and the skill that runs the workflow.
Source excerpt starting at line 23.- Manual PR preview testing (medium/high risk, logged-in user + data):- [docs/contributing/preview-manual-testing.md](./docs/contributing/preview-manual-testing.md) and the [preview-manual-test skill](./.agents/skills/preview-manual-test/SKILL.md)
04 / Router files
The cloud-specific section names runtime setup, browser-install hangs, seeding, and local limitations. It sends those environment details to a separate reference rather than mixing them into every contributor instruction.
Source excerpt starting at line 69.Cloud Agent VM gotchas (Node 26 on `PATH`, the Playwright browser-install hangand manual workaround, dev server, seeding, and local limitations) live in adedicated reference:
These instructions explain how to work in Kody. Modem shows your agents what customers said, who is affected, and what changed.