AGENTS.md: number rules, errors as feedback, and the working method - #417
Merged
Conversation
Three rules from the number-parsing work are stated where every session loads them. Number rules: $(( )) owns bases and checked arithmetic with bash's spellings only; a leading zero is text and every number position refuses it naming the fix; fromjson is JSON-only and no cast builtin or --base flag exists. The error-handling section gains the no-silent- fallback rule, with printf '%d' 0xff printing 0 as the shape to refuse. The writing-style section states the stance behind it: an error is feedback for the next turn, so refusing with the fix named beats degrading quietly. Version control gains the working method: one medium PR per hunk, coding delegated against a written spec with tests that fail first, gates and kaibo review run by the orchestrator, and review claims verified against a built binary. A claim that models habitually write some spelling is a measurable thing: give cheap casts the help text and count before adding syntax. Commit messages: a clinical engineering narrative; design stories and plans live in exomemory and are never referenced from a commit. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A rule names what kaish does. The sentence listing the builtin and flag that were not built dragged discarded ideas into a file every session loads; it is gone. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The two bullets under version control described how one session ran its work, which does not belong in a file every session loads. The measurable half survives as its own short section: a claim about what models or users will write is tested by handing cheap casts or subagents the proposed help text and counting, and one syntax stands until the count says otherwise. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
"exomemory" is the name of one maintainer's memory store; the rule is about where design stories live, so it names agent memory outside the repo instead. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three rules from the number-parsing work, stated where every session loads them.
Number rules:
$(( ))owns bases and checked 64-bit arithmetic with bash's spellings only (0xff,base#digits); a leading zero is text, and every number position refuses it naming the fix;fromjsonis JSON-only. The error-handling section gains the no-silent-fallback rule, with this as the shape to refuse:Writing style states the stance behind it: an error is feedback for the next turn, so refusing with the fix named beats degrading quietly.
A short section, "Test a theory before building it", says a claim about what models or users will write is measurable: hand cheap kaibo casts or subagents the proposed help text and a task list, count, and keep one syntax until the count says otherwise.
Commit messages are a clinical engineering narrative; design stories and plans live outside the repo and are never referenced from a commit.
🤖 Generated with Claude Code