simplify
Simplify
Overview
Refine recently modified code for clarity, consistency, and maintainability while preserving exact functionality. Prefer readable, explicit code over compact solutions.
When to Use
- After writing or modifying code, before committing
- When code works but feels overly complex or unclear
- When you notice inconsistency with project patterns
- After a feature is complete and needs a cleanup pass
Not for: Rewriting code that wasn't recently touched (unless explicitly asked).
Core Principles
More from jssee/agents
slicing
Use when a chosen approach or clear build target needs to become ordered, demo-able slices. Natural follow-up to `shaping`, but also works from any clear description of what to build. Trigger on "break this down", "what's V1", "plan the rollout", "MVP then iterate", "ship incrementally", or work with multiple pieces that need sequencing.
10shaping
Use when working through a fuzzy idea before implementation. Always asks clarification questions first, then produces a requirements table, one or more viable shapes, a fit-check matrix, and a recommendation. Trigger on "not sure which approach", "should we build X or Y", "what's the scope", "tradeoffs", "before we start", or any request where multiple directions are possible.
10commit
Use when committing local changes while preserving clean, reviewable git history.
9reducing-entropy
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
3write-skill
Create or revise SKILL.md instruction files that agents can follow reliably under context pressure.
3diagnose
Use when a bug, failure, exception, flake, or performance regression needs disciplined root-cause work. Triggers on "diagnose this", "debug this", "why is this broken/slow/throwing/failing", or any report of incorrect runtime behavior.
2