-
Update the spec when you add features. When a new feature, decision, or constraint is introduced, append it to the plan file at
PLAN.mdbefore (or alongside) implementing it. The plan is the canonical record — don't let it drift. -
Test new behavior in browser before signing off. Use the browser to load the relevant page, exercise the new flow end-to-end, and verify it works visually. Don't claim a feature is done from typecheck + curl alone if there's UI involved.
-
Commit after each milestone. When a cohesive group of changes is verified working (one feature, one bug fix, one refactor — not "all of today's work"), make a git commit with a short, focused message. The commit history should read like a changelog. Don't pile multiple features into one commit. Commit only files relevant to the milestone; never
git add -A. -
Ask Questions. When instructions are unclear, please surface those questions to me.
Created
August 26, 2026 15:51
-
-
Save russianryebread/2e1a5b3cc830ddce040ec37ea1cd5d0f to your computer and use it in GitHub Desktop.
Default Project AGENTS.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment