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.
Scanned 8/31/2026
Install via CLI
Skills Directoryopenskills install saadshahd/moo.md---
name: prime
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.
---
# sound:prime
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 comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
