docs(rules): tighten wording to cut always-on token cost (lossless)#20
Merged
Conversation
Wording-only compression of always-on rules 00-06 and scoped 10/11/14: drop filler/redundant phrasing, collapse verbose constructions, merge bullets that share a subject. Every normative clause, enumerated item, tool, flag, code, and command preserved (verified per-file git diff); frontmatter byte-identical. always-on 00-06: 28159 -> 27369 bytes (-790, -2.8%); scoped 10/11/14: -47. Excludes 12-go/13-typescript (in flight in PR #19). check rules / check / build --target all / test all green. by mass-energy equivalence
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.
What
Wording-only compression of the always-on rules
00–06and scoped10/11/14. Filler removed, verbose constructions collapsed, bullets sharing a subject merged. No information removed — every normative clause, enumerated item, tool, flag, error code, and command preserved; frontmatter byte-identical.Excludes
12-go/13-typescript(in flight in #19) to avoid conflict; they get the same pass after #19 lands.Reduction (honest)
00–0610/11/14Small on purpose: the rules were already dense, and the constraint was zero information loss. Lossless wording tweaks are near their floor here.
Verification
git diffreviewed line-by-line — each removed line is filler/redundancy, never a rule. The one structural change (Rust) merges two adjacent bullets keeping both sentences verbatim.check rules·check·build --target all·test— all green. Frontmatter (description/globs/alwaysApply) byte-identical everywhere.The bigger lever (not done here — your call)
If context budget is the real goal, wording isn't where it is.
04-cybersecurityalone is ~29% of the always-on budget (7.8 KB) and loads into every session, including non-security work. Making it glob-scoped (alwaysApply:false) would reclaim far more than this whole PR — but security work lacks a clean file-glob trigger, so it's a policy tradeoff (risk: the rule won't load when needed), not a wording change. I didn't touch it unilaterally. Say the word if you want to explore a trigger for it.by mass-energy equivalence