docs: prefer operational rules over code and document expected repository rules - #1183
Merged
Conversation
…tory rules - Restructure AGENTS_EXTRA.md into a minimal, unambiguous rule set that prefers operational rules over accommodating code, and sync the wbfy-generated agent instruction files. - Add docs/expected-repository-rules.md summarizing the rules wbfy and wb expect of target repositories, linked from README. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
…/styleguide.md Apply review feedback: sync .gemini/styleguide.md with the rewritten AGENTS_EXTRA.md, and correct docs/expected-repository-rules.md (workflow ownership vs deletion, WillBooster-only ruleset, per-organization reusable-workflows mirror, PUBLIC_FNOX_AGE_KEY, .env.cloudflare exception, Takumi Guard lockfile scope, ignore-file deletion, redundant-generation script rewrite, workflow marker prefix, and unparseable-input exceptions). Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Amend the canonical-format rule to allow skip-with-warning, and fix docs/expected-repository-rules.md: mise.toml parse errors are only logged, Python manifests are poetry.lock/uv.lock, git-dependency policy covers package.json only, gen-pr*.yml deletion by filename, published willbooster-configs oxlint.config.ts preservation, postinstall custom segments, fnox root requirement scope, test-layout exemptions, and VERDACCIO_TOKEN for publishers. Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
…paths Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
Co-authored-by: WillBooster (Claude Code) <agent@willbooster.com>
…tory rules Co-authored-by: WillBooster (Claude Code) <agent@willbooster.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.
Customer Summary
wbfyandwbexpect of target repositories, so maintainers know which files they may edit, which are regenerated or deleted, and which deviations fail a run.Technical Summary
AGENTS_EXTRA.mdinto a minimal six-bullet rule set (roughly half the previous token count) and synced all five generated instruction files:AGENTS.md,CLAUDE.md,GEMINI.md,.cursor/rules/general.mdc, and.gemini/styleguide.md.docs/expected-repository-rules.mdcovering repository preconditions, ownership markers (which files a human may edit and where), file-format rules, project structure expected bywb, and GitHub-side conventions; linked it fromREADME.md.mise.tomlparse errors are only logged,gen-pr*.yml/autofix*.yml/sync-init.ymlfilename-based deletion, per-organization reusable-workflows mirrors,install.exact = falsepreservation, Takumi Guard URL scope) were folded into the text.Why
wbfy/wbimplementations minimal, but those rules were only implicit in the code; documenting them makes the constraint enforceable and gives agents and developers a single reference to update alongside new expectations.Testing
bun verify(type checking and linting) passed after each change.Codex,Claude Code,Antigravity) converged with no remaining concerns.