laws-of-taste
Laws of Taste
Apply this skill to any visual surface people must look at, scan, use, trust, or move through.
Core stance
Taste is not decoration. Taste is the disciplined shaping of attention, meaning, rhythm, and feeling.
Default to these beliefs:
- Purpose before ornament.
- Order before expression; then break order intentionally.
- Hierarchy must be obvious at a glance.
- Restraint beats novelty unless novelty is the point.
- Systems create trust; selective exceptions create life.
- The goal is not “more design.” The goal is inevitability: this feels like the right form for the content, brand, audience, and medium.
This skill is intentionally opinionated. It should not rubber-stamp generic work. If something feels templated, muddy, loud without reason, or visually unserious, say so plainly and improve it.
More from mylesmcook/mcook-skills
adversarial-review
Use this skill when you need a serious code review, diff review, or implementation-plan review from independent reviewers. In Codex hosts, prefer a fresh Codex subagent for the Codex reviewer; otherwise use the Codex, Claude Code, and Gemini reviewer paths when available. Return a PASS, CONTESTED, or REJECT verdict.
13subagent-driven-development
Use after an implementation plan is approved to execute mostly independent tasks through fresh subagents with scoped context, harness-aware model routing, proportional review gates, and mandatory controller verification.
10brainerd
>
10simple-code
Reduce incidental complexity in code and design. Use when shaping APIs, module boundaries, refactors, tests, naming, and architecture tradeoffs with a bias toward concrete, local, reversible solutions.
7git-it-out
Use this skill when the user explicitly wants final end-of-session closeout and no more branch or PR limbo: proper verification, proper commits, main/mainline landing, push, repo-native merge/release/deploy/publish steps, tracker updates, Entire/checkpoint handling when configured, and a concise handoff. Reach for it on prompts like 'git it out', 'get it out', 'ship this', 'I'm done', 'I'm going to bed', 'take this off my plate', 'finish the session', or 'get this into production'. Do not use it for greenfield implementation, open-ended debugging, broad refactors, or inventing a release process from scratch.
7simplify
Refine recently changed code for clarity, consistency, and maintainability without changing behavior. Use when the user explicitly asks to simplify, clean up, or lightly refactor touched code, reduce local complexity, remove redundancy, improve naming or structure, or make recent edits easier to read while preserving outputs, interfaces, tests, security, and accessibility.
6