Loading...
Loading...
Found 87 Skills
Apply the Unix philosophy (Eric S. Raymond's 17 rules, McIlroy's "do one thing well", Rob Pike's rules on measurement and data) when designing, writing, refactoring, or reviewing software in any programming language. Use this skill whenever the user asks to design a module, service, CLI, API, library, or package; write or refactor non-trivial code; review a pull request or code for quality; split a large function, class, or service; decide between a clever and a simple approach; or asks about modularity, composability, simplicity, error handling, or "clean" design, even if they never mention Unix. Works for Go, TypeScript/JavaScript, Python, Java/Kotlin, Rust, Haskell, Lean 4 (programs and proofs), and other languages.
Implement behavior through the red-green-refactor loop. Apply it when test-first execution is requested or selected by the coding workflow; apply safe-incremental-coding first for untested legacy code.
Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.