laws-of-software-los
Laws of Software (LOS)
Apply this skill when software work needs principal-level judgment, explicit tradeoffs, and a credible validation path.
This skill is original synthesis inspired by the public law list at https://lawsofsoftwareengineering.com/. Use the source site for canonical law descriptions and updates.
Use when
- choosing or reviewing architecture, system design, APIs, service boundaries, or infrastructure direction
- reviewing an RFC, ADR, migration plan, incident, codebase structure, or technical strategy
- making code changes where data safety, compatibility, reliability, security, or operability matter
- answering questions about distributed systems, scalability, performance, technical debt, testing, rollout, rollback, or team ownership
Do not use for:
- tiny syntax fixes or rote formatting
- purely mechanical conversions or summaries
- non-software domain work
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.
7laws-of-taste
>-
6