2.4 KiB
Agents (Neon Sprawl)
Optional personas for Cursor. Enable by @ mentioning the rule in chat or by asking explicitly (e.g. “review this as the code review agent”).
| Agent | Rule file | When to use |
|---|---|---|
| Code review | .cursor/rules/code-review-agent.md |
PR / diff / pre-merge review; always writes docs/reviews/YYYY-MM-DD-{slug}.md with Documentation checked vs docs/plans/ and docs/decomposition/modules/; when suggestions are fixed, strike through those bullets + Done. in that file (planning-implementation-docs); short chat pointer |
| Docs review | .cursor/rules/docs-review-agent.md |
Coherence / links / dev-guide fitness for docs/ (especially docs/game-design/ + decomposition); writes docs/reviews/YYYY-MM-DD-{slug}.md; when suggestions are fixed, strike through + Done. in that file (planning-implementation-docs); use when working in documents or @ mention |
Project-wide conventions live under .cursor/rules/ (many are alwaysApply). Planning / implementation decisions must be written into docs/plans/ (and related docs)—.cursor/rules/planning-implementation-docs.md. Godot client layout (thin main.gd, split by concern): .cursor/rules/godot-client-script-organization.md. Git: agents may commit at discretion on story/ticket work; never git push unless the user asks — .cursor/rules/commit-and-review.md. Story lifecycle: kickoff .cursor/rules/story-kickoff.md; after merge / end of story — checkout main, pull, delete local story branch — .cursor/rules/story-end.md. Jira: ask In Test vs Done (or wait for the user to say which in the same message) before transitioning the issue; do not guess. PR / push text: no “Made-with: Cursor” boilerplate (same file).
Commits tied to a Jira issue must start the subject with the issue key and a colon (e.g. NEON-5: …). Branch naming and exceptions (chore: when there is no ticket) — .cursor/rules/jira-git-naming.md.