reducing-entropy
Reducing Entropy
More code begets more code. Entropy accumulates. This skill biases toward the smallest possible codebase.
Core question: "What does the codebase look like after?"
Before You Begin
Load at least one mindset from references/
- List the files in the reference directory
- Read frontmatter descriptions to pick which applies
- Load at least one
- State which you loaded and its core principle
Do not proceed until you've done this.
The Goal
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.
9simplify
Use when code has been recently written or modified and needs refinement for clarity, consistency, and maintainability before committing
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