anchor
FreeRewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.
The English summary is being prepared. Showing the original description.
Use in a repo that has sound taste rules installed (a `.claude/sound/` directory), before writing or editing code — at the start of a coding task, and again when the work reaches a surface it was not planned to touch.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
If the repo has no .claude/sound/ directory, it carries no sound taste rules — do nothing.
Otherwise: the project's taste rules live under .claude/sound/, grouped into topic folders (<topic>/<rule-name>.md). Before you write, browse the tree to see which topics bear on the surfaces you'll touch. Read a rule's file when its situation comes up, and make sure your code meets every rule that governs a surface you change. If the work reaches a surface you had not planned to touch, browse the tree again for that surface before writing it.
When two rules pull opposite ways on one surface, check each rule's Not-when and Cross-ref first — most conflicts are already carved there. Where none applies, the rule protecting correctness or debuggability outranks the one protecting style.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Rewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.
The English summary is being prepared. Showing the original description.
Turn words with two readings into one confirmed ask. Use when the user's words admit two readings that would build different things.
The English summary is being prepared. Showing the original description.
Plan the skills an ask needs, invoke each as its condition arrives. Use when the ask has multiple aspects that different skills carry, or the user named multiple skills.
The English summary is being prepared. Showing the original description.
Bring how named experts would think about the question. Use when the user wants expert thinking on a tradeoff, choice, or stuck problem — not a verdict.
The English summary is being prepared. Showing the original description.
Hold an ask to the bar a top professional in its field would set — a deeper ask, never a bigger one. Use when an ask is clear but nothing yet names the sources, methods, target, or outside check the work will meet.
The English summary is being prepared. Showing the original description.
Build the thing the user can't specify, choices surfaced. Use when the user needs something to react to before they can choose.
The English summary is being prepared. Showing the original description.