From sound
Use at the very start of any coding task in a repo that has sound taste rules installed (a `.claude/sound/` directory), before writing or editing code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sound:primeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
If the repo has no `.claude/sound/` directory, it carries no sound taste rules — do nothing.
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.
npx claudepluginhub saadshahd/moo.md --plugin soundUse when installing or refreshing sound taste rules in a project. Triggers on "sound setup", "install taste rules", "scaffold .claude/sound", "set up sound here", starting work in a repo with no .claude/sound/, or a taste-not-defined nudge. Also use to re-run after a stack change (new framework, new package in a monorepo).
Guides creation of .claude/rules/ files for path-scoped project conventions using TDD workflow: RED (test gaps), GREEN (write rule), REFACTOR (optimize). Triggers on 'add rule', 'create convention', 'scope guideline'.
Facilitates structured conversation to define clean code principles for a repository, producing clean-code.md override for clean-code atom. Use for coding standards or quality rules.