simple-code
Simple Code
Use this skill when simplicity and maintainability are the main design pressure.
Workflow
- Identify the real requirement, dominant risks, and which concern should lead the decision.
- Recommend the simplest design that satisfies the requirement now.
- Prefer local, concrete, reversible changes over speculative abstractions.
- Pull unavoidable complexity behind the simplest stable boundary you can.
- Test at stable boundaries rather than mirroring internals.
References
references/api-design.mdreferences/architecture.mdreferences/refactoring.mdreferences/provenance.md
Guardrails
- Do not simplify away correctness, security, accessibility, or explicit product requirements.
- Treat added abstraction as a cost that must justify itself.
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
>
10git-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.
7laws-of-taste
>-
6simplify
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