Releases: DarKWinGTM/claude-code-rules
Release list
v9.20 - task-list continuity and accurate-communication trim
Summary
- keep one live task-list surface across the same active objective instead of repeatedly replacing it
- clarify reuse/append retention and completed-task visibility until objective closure
- bundle
accurate-communication.mdwording-only micro-compression below the 40.0k warning threshold
Included wave
- wave 034: task-list continuity and objective-boundary retention
v9.19 - execution continuity and goal review owners
Summary
- promote
high-signal-communication.mdinto the active runtime rule set - add first-class
execution-continuity-and-mode-selectionandgoal-set-review-and-priority-balanceowner chains - sync companion rules, phase/patch artifacts, master surfaces, and installed runtime parity
Included waves
- wave 032: high-signal communication promotion and sync
- wave 033: execution continuity and goal-set review owners
v9.17 - improve README Quick Start install scripts
Summary
- replace the old Quick Start install block with cleaner Bash and PowerShell scripts
- remove centered presentation around the Quick Start install code
- keep the same active 36-rule runtime install set while making the scripts easier to reuse on Linux/macOS and Windows
Included files
- README.md
- TODO.md
- changelog/changelog.md
v9.16 - add AI-assisted install prompts
Summary
- add copy-ready README prompts for Claude Code, Codex CLI, and Gemini CLI
- keep install/adaptation prompts aligned to the active-vs-non-active rule boundary
- record the README install-prompt refinement in TODO and the master changelog
Included files
- README.md
- TODO.md
- changelog/changelog.md
v9.15 - refine task-phase linkage and phase explanations
Summary
- link live task-list behavior directly to the current active phase
- improve phase/progress explanations so they start with easy-to-picture plain-language framing
- add a standalone experimental high-signal-communication rule without merging it into the active owner graph
Included updates
- todo-standards, phase-implementation, artifact-initiation-control
- explanation-quality, accurate-communication, answer-presentation
- design/changelog/master-surface sync
Runtime install
Updated runtime copies were installed for the touched active rules and for the experimental high-signal-communication rule.
v9.8 - strengthen plain aligned table-style enforcement
Summary
- strengthen the ordinary answer-table default so it more explicitly enforces the selected light plain aligned no-frame style
- reduce fallback drift toward generic markdown pipe-table framing
- keep tables available when genuinely useful
- preserve list-first alternatives for sequence and simple status content
Included scope
- answer-presentation enforcement tightening
- explanation-quality alignment tightening
- runtime reinstall and live behavior retest
Runtime notes
- touched runtime rules were reinstalled and parity-checked against source
- live prompt test now outputs the selected plain aligned no-frame style instead of the earlier generic pipe-table form
v9.7 - memory governance, task tracking, and table style refinement
Summary
- add first-class memory governance and session-boundary rule chain
- make built-in task tracking explicit for non-trivial work while keeping TODO.md as the durable tracking artifact
- correct the default table style to the selected light plain aligned no-frame form
- narrow the remembered table preference so table style remains RULES-owned
Included waves
- Wave 026: memory governance and session boundary
- Wave 027: task-list-first execution tracking
- Wave 028: plain aligned no-frame table style refinement
Runtime notes
- touched runtime rules were reinstalled and parity-checked against source
- active runtime inventory remains 36 rules
Key touched runtime owners
- memory-governance-and-session-boundary
- todo-standards
- artifact-initiation-control
- project-documentation-standards
- answer-presentation
- explanation-quality
v9.4 - compact markdown table defaults
Summary
- standardize compact markdown tables as the default table form when a table is genuinely useful
- prefer numbered lists for sequence and bullets/grouped blocks for simple status pairs
- stop defaulting to full-frame boxed tables for ordinary answer formatting
Touched rule versions
- answer-presentation v1.16
- explanation-quality v2.11
Included governance artifacts
- patch/compact-markdown-table-default-and-minimal-table-usage.patch.md
- phase/phase-025-01-refine-compact-table-defaults.md
- phase/phase-025-02-sync-master-docs-and-runtime-install.md
v9.3 - purpose-first communication framing
Summary
- require purpose-first / main-point-first framing for diagnosis, test, recommendation, proposal, and implementation-update answers
- sync wording, explanation, presentation, and style owners plus bounded wave-024 governance artifacts
- resync installed runtime rule copies and reconcile postflight phase-summary drift found during audit
Touched rule versions
- accurate-communication v2.13
- explanation-quality v2.10
- answer-presentation v1.15
- natural-professional-communication v1.2
Included governance artifacts
- patch/purpose-first-communication-framing.patch.md
- phase/phase-024-01-refine-purpose-first-communication.md
- phase/phase-024-02-sync-master-docs-and-runtime-install.md
v9.2 - rules-first governance and portable support artifacts
Summary
This release tightens two governance areas in the RULES repository:
- direct human-readable wording over metaphor-heavy internal shorthand
- rules-first handling for user-declared governance issues, plus portable-by-default support/package source artifacts
Included rule updates
accurate-communication-> v2.12explanation-quality-> v2.9natural-professional-communication-> v1.1answer-presentation-> v1.14authority-and-scope-> v2.0portable-implementation-and-hardcoding-control-> v1.2project-documentation-standards-> v2.15document-consistency-> v1.6- master design / README / TODO / phase / changelog synchronized to
v9.2
Behavioral changes
Direct human-readable wording
The communication-owner set now prefers direct action/result wording over metaphor-heavy internal shorthand when a plain statement would make the practical meaning clearer immediately.
RULES-first over memory-first
When the user explicitly says an issue should be solved in RULES rather than memory, the assistant must keep the fix on the RULES path instead of treating a memory write as the substitute remedy for that same issue.
Portable support/package source artifacts
Reusable support/package source artifacts such as plugin-owned docs, scripts, skills, and agents are now explicitly portable-by-default and should not bake workstation-specific absolute paths into reusable source content.
New governed artifacts
patch/direct-human-readable-wording-over-metaphor-heavy-shorthand.patch.mdpatch/rules-first-over-memory-and-portable-support-artifacts.patch.mdphase/phase-022-01-refine-direct-human-readable-wording.mdphase/phase-022-02-sync-master-docs-and-runtime-install.mdphase/phase-023-01-rules-first-over-memory-boundary.mdphase/phase-023-02-sync-master-docs-and-runtime-install.md
Verification
- master changelog anchor integrity passed
- touched rule/design/changelog/master/phase/patch surfaces were synchronized
- touched runtime rule copies were re-synced into
~/.claude/rules/