Skip to content

[codex] Add agent coding discipline guidelines #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
meekmachine wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[codex] Add agent coding discipline guidelines #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,15 @@ The desired architecture is data-first:
- runtime outputs become observable streams at the JS boundary
- LoomLarge bridges those streams into Effect-managed state

## Karpathy-Style Agent Discipline

- Think before coding: state assumptions, name ambiguity, and ask before implementing when multiple interpretations would change the solution.
- Prefer the smallest change that satisfies the request. Do not add speculative flags, fallbacks, abstractions, or configurability that the user did not ask for.
- Keep PRs surgical. Package identity, runtime behavior, CI wiring, docs, and migration strategy should be separate changes unless the user explicitly asks for one combined PR.
- Every changed line should trace directly to the user's request. If you notice unrelated cleanup, mention it instead of editing it.
- Define success criteria before editing, then verify them with focused checks. For behavior changes, add or update tests that prove the intended behavior.
- Do not present TypeScript compatibility exports, app-side feature flags, or fallback paths as evidence that Polyester has become a CLJS replacement. Replacement means the package behavior is CLJS-backed and verified by parity tests.

## Documentation Discipline

When implementation work exposes a recurring misunderstanding, missing
Expand Down