| 1 | # Project Rules |
| 2 | |
| 3 | Conventions and style guides for contributors and AI agents working in this repository. These rules are derived from the de facto patterns in existing code and reference documents. |
| 4 | |
| 5 | | Rule | Scope | |
| 6 | |---|---| |
| 7 | | [`prompt-style.md`](./prompt-style.md) | Style guide for files under `skills/ppt-master/references/` — voice, sectioning, table-first, forbidden patterns | |
| 8 | | [`code-style.md`](./code-style.md) | Style guide for Python under `skills/ppt-master/scripts/` — file headers, imports, CLI entry points, error handling, no-tests rule | |
| 9 | | [`language.md`](./language.md) | Language rule for agent-facing Markdown and `docs/` — one language per file, non-English as content but never as a rule, no hard-coded output language | |
| 10 | |
| 11 | When adding a new rule file: |
| 12 | |
| 13 | - One topic per file |
| 14 | - File name `<topic>.md` (lowercase, hyphenated) |
| 15 | - Add a row to the table above |
| 16 | - The body should be **prescriptive, not descriptive** — tell readers what to do, not what the project happens to look like |
| 17 |