Loading...
Loading...
Found 73 Skills
Evaluates and prevents unnecessary abstractions by analyzing interfaces, layers, and patterns against concrete requirements. Use when evaluating new abstractions, reviewing architecture proposals, detecting over-engineering, or simplifying existing code. Triggers on "is this abstraction necessary", "too many layers", "simplify architecture", "reduce complexity", "over-engineered", "do we need this interface", or when reviewing design patterns.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Manually trigger the cdd-code-simplifier agent to review and simplify code
Keep code, tests, documentation, configuration, and other changes as tight, clear, performant, and minimal as possible without weakening behavior. Use during implementation to prevent unnecessary complexity, after behavior is proven to consolidate working changes, before handoff for a full branch audit, and when asked to simplify, tighten, clean up, reduce verbosity, remove complexity, or minimize existing work.
Use when working in a repository to find non-obvious simplification candidates — dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surface across code, docs, and skills — and turn the worthwhile ones into proposed Agent Notes or inline TODO/FIXME/XXX markers; also when asked to audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR or branch.
Anti-footgun protocol for AI-assisted coding. Always active during coding tasks to enforce simplicity-first thinking, surface assumptions, and prevent scope creep. Explicit checkpoints available via "cg pre", "cg post", "cg simplify". Triggers on: any coding task, code review requests, refactoring, or when user says "cg" or "check".
Post-implementation cleanup of correct code. Prunes comments aggressively: deletes what restates the code, files design rationale to the commit message and wider context to the PR or an issue, collapses one mechanism explained in three places, strips issue and PR references that make a file unreadable on its own, compacts genuine gotchas, renames unclear symbols so a comment is not needed, checks the code against the project's conventions, and simplifies what is more complicated than it needs to be. Tightens docs without gutting them. Auto-applies and reports.
Apply the K.I.S.S principle (Keep It Simple, Stupid) to reduce complexity, improve maintainability, and solve problems elegantly. Use when designing systems, writing code, planning solutions, creating documentation, architecting features, or making decisions where simplicity drives quality and efficiency.
Simplify and refine PHP/Laravel code for clarity and maintainability without changing behavior.
Review RTK Rust code for idiomatic simplification. Detects over-engineering, unnecessary allocations, verbose patterns. Applies Rust idioms without changing behavior.
Strip designs to their essence by removing unnecessary complexity. Great design is simple, powerful, and clean.
Remove LLM-generated code patterns that add noise without value. Use when reviewing diffs, PRs, or branches to clean up AI-generated code. Triggers include requests to "remove slop", "clean up AI code", "review for AI patterns", or checking diffs against main for unnecessary verbosity, redundant checks, or over-engineering introduced by LLMs. Language-agnostic.