This skill helps you shrink a codebase by focusing on the final amount of code. The main idea is to bias toward deletion and aim for less total code in the end. Every change should make the codebase smaller, not bigger.
Success is measured by how many lines remain, not by how much work you put in. Writing 50 lines to delete 200 is a win. Keeping 14 functions to avoid writing 2 is a loss. The goal is the smallest possible codebase that still solves the problem.
Before you start, you must load a mindset from the reference files. Then ask three questions: What is the smallest codebase that works? Does the change make total code smaller? What can you delete? Always measure the end state, not the effort.
Global
mkdir -p ~/.claude/skills/reducing-entropyProject
mkdir -p .claude/skills/reducing-entropySource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues