Overview
The Behavior standards: how an agent works and what an agent checks.
- A Go Before Work Elsewhere - never start work in another project, or a session that outlives this one, without an explicit go. "Next is X" names only the topic. Projects come from the director's words, never a recent-folders list
- A Maybe Is A Trigger To Investigate - an idea the director phrases with uncertainty gets investigated in the same pass, never parked
- A Name Describes Its Unit - a name describes its unit clearly and precisely, neither too broad nor too narrow
- A Quiet Tree While A Suite Runs - no source edits while a suite runs on a live dev server
- Always Make No Mistakes - use your standards, own mistakes and strengthen the harness with a rule or check
- Always Verify Before Reporting Done - run the check that matches the change before claiming done
- Always Work From A Plan - work that survives the session or grows out of scope gets a written plan. In a project all work follows the project's workflow
- Anchor Edits After Formatting - no write while a commit hook runs, check every anchor of a batch first, no edit by line number after a formatter
- Backward-Trace Missing Prerequisites - a missing prerequisite is filed above the item. Recurse, never patch around
- Code Review Compounds Into Patterns And Sweeps - a review finding is a pattern: a review check or a standard through healing, and a sweep ticket
- Communication Boundary - never contact users or testers or speak for the director. A follow-up only the director can do goes on the director tasks
- Dev Tiers - the recommended order: build, bugs, debt, features, within the current phase's goal. The director decides, and a pick that skips open bugs or debt gets a reminder
- Docs Hold Only What The Director Decided - docs hold only what the director decided. Ideas go to chat first
- Don't Filter Data Without A Spec - never drop data unless the exclusion is specced and tested
- Don't Introduce Tech Debt - new code follows conventions even when neighbors don't. Fix what your change caused
- Feature Workflow - plan -> doc -> laws -> spec -> failing e2e -> implement -> regression -> proof the director can verify
- File A Change With Coentrify - a contributor files a harness change that holds beyond its project, one point per issue, without project details
- Flag Every Addition Of Your Own - name a decision of your own that no law, rule or guideline settles, for a veto. An impactful change is discussed first
- Free Text Replies, No Buttons - no answer buttons or wrap-up questions. Ask in prose and keep going. No closing prompts where a dashboard shows the director's inboxes
- General Working Rules - honest assessments, the model only for judgment calls, surface conflicts, read before you write, follow the written conventions
- Non-Destructive Documenting And Test Automation - doc, spec and e2e steps never touch production code
- Normal Dashes - always
-, never em or en dashes - Note Issues - write down every finding where the project's workflow says, never only in chat
- Own Ports, Own Processes - own fixed non-default port per project, kill only your own PIDs, stop what you started
- Project Lifecycle - a project is in one phase at a time, the phase decides what matters now, and a phase gate ends it
- Propagate Renames And Convention Changes Everywhere - a rename updates every reference in the same change, grep before and after. A changed convention updates the pages that state it, and its occurrences go to a sweep
- Prose Style - no AI sentence patterns. Calm, concrete, varied. Reports brief
- Prototype Mode Is Speed First - prototyping means speed: no tests, kept apart from the product's code, run it and share the link
- Regular Layered Gap Analysis - walk the doc, spec, test and code layers both ways. Rules against the code too
- Reload The Standards After Compacting - after a compaction, read the Core Rules again, by a hook where the agent has one
- Review Changes Before Reporting Done - before claiming done, check the relevant standards and surface changes you did not make
- Review Every Capture Before Reporting - read every capture for regressions, caption match and unintended shapes
- Standards Maintenance - a periodic sweep for bloat, stale rules, duplicates, drift and dead links, with a word budget per standard. How a standard is added
- Standards Over Skills - on conflict with a skill from outside the project, the standard wins. A wrong line goes into a standard, never into the skill
- Sweeps Enumerate Into Tech-Debt First - a sweep lists every instance in one debt entry before fixing
- Sync The Docs After Every Change - after a landing, grep the docs for its terms and fix what went stale. A plan it conflicts with goes to the director as a question
- The Quality Of The Question - an answer is as good as its question. Suspect the question first, and ask a vector question over a binary one
- Things Of One Kind Are Consistent - things of one kind share a structure and a behavior, and fit with the rest
- Understand The Need - the need before the solution, and the right solution fitted to the need
- Use US English Everywhere - US spelling everywhere. Convert British spellings when touching them
- Verify APIs Against Docs And The Installed Artifact - when a pinned dependency and its docs disagree, the installed artifact decides, or the dependency is updated. Endpoints are checked against the spec, generated assets against their documented rule
- Verify Control Before Rename - trace a control to its handler before relabeling it