neuron-tai/AGENTS.md

Memory

Persistent memory lives in .claude/memory/. Read MEMORY.md there at the start of every session for project context, user preferences, and open work. Write updates back to those files so knowledge carries across devices and sessions.

Agent skills

Issue tracker

Active feature work lives under .scratch/<feature-slug>/. Completed features are merged into docs/issues/ via /close-feature. See docs/agents/issue-tracker.md.

Triage labels

Default mattpocock/skills label strings (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). See docs/agents/triage-labels.md.

Domain docs

Multi-context layout: CONTEXT-MAP.md at root points to per-context CONTEXT.md files; system-wide ADRs in docs/adr/, context-scoped ADRs in src/<context>/docs/adr/. See docs/agents/domain.md.

graphify

This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.

When the user types /graphify, use the installed graphify skill or instructions before doing anything else.

Rules:

• For codebase questions, first run graphify query "<question>" when graphify-out/graph.json exists. Use graphify path "<A>" "<B>" for relationships and graphify explain "<concept>" for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.
• Dirty graphify-out/ files are expected after hooks or incremental updates; dirty graph files are not a reason to skip graphify. Only skip graphify if the task is about stale or incorrect graph output, or the user explicitly says not to use it.
• If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
• Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
• After modifying code, run graphify update . to keep the graph current (AST-only, no API cost).