Simplify
Polish code you just wrote so it matches project conventions and reads clearly without changing behavior.
Overview
Simplify is an agent skill most often used in Ship (also Build frontend and Build backend) that refines recently changed code for clarity and project consistency without altering what it does.
Install
npx skills add https://github.com/brianlovin/agent-config --skill simplifyWhat is this skill?
- Hard rule: preserve all functionality, outputs, and behavior while only changing structure and style
- Applies project standards from CLAUDE.md: ES modules, import sorting, function over arrow, explicit return types, React
- Simplifies nesting, removes redundant abstractions, and favors readable explicit code over compact cleverness
- Avoids unnecessary try/catch per stated error-handling preferences
- Targets recently modified code rather than whole-repo rewrites
- Three core refinement pillars: preserve functionality, apply project standards, enhance clarity
- Explicitly prioritizes readable code over overly compact solutions
Adoption & trust: 528 installs on skills.sh; 349 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You shipped working code from an agent session, but it is verbose, inconsistent with CLAUDE.md, or harder to review than the rest of your codebase.
Who is it for?
Solo builders who already have CLAUDE.md or similar standards and want a dedicated pass on diffs the agent just wrote.
Skip if: Greenfield repos with no style guide yet, or when you need bug fixes or feature changes rather than readability-only edits.
When should I use this skill?
Use after writing code to improve readability without changing functionality.
What do I get? / Deliverables
Recently modified files read cleaner, follow your documented conventions, and stay functionally identical—ready for commit or code review.
- Refined source edits with unchanged behavior
- Imports and components aligned to documented conventions
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship → review because the skill is explicitly for post-implementation refinement before merge or release, even though you invoke it right after coding in Build. Review subphase fits clarity-and-consistency passes that preserve outputs while aligning with team standards (e.g. CLAUDE.md).
Where it fits
After the agent adds a React screen, run simplify so new components use explicit Props types and function declarations like the rest of the app.
Tighten a freshly written API handler by flattening nesting and aligning error handling before you wire integrations.
Pre-PR pass on the diff only so reviewers see consistent ES module imports and less redundant abstraction.
How it compares
Use after implementation for style and structure; use a dedicated code-review skill when you need defect hunting and severity-ranked findings.
Common Questions / FAQ
Who is simplify for?
Simplify is for solo and indie developers using Claude Code, Cursor, or Codex who want post-coding polish aligned with CLAUDE.md-style rules without changing program behavior.
When should I use simplify?
Use it after writing or generating code in Build (frontend or backend integrations), before opening a PR in Ship review, or when agent output works but violates your import, React, or naming conventions.
Is simplify safe to install?
It focuses on local code edits; review the Security Audits panel on this Prism page and skim proposed diffs before merging since any refactor can introduce accidental edits.
SKILL.md
READMESKILL.md - Simplify
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions. This is a balance that you have mastered as a result your years as an expert software engineer. You will analyze recently modified code and apply refinements that: 1. **Preserve Functionality**: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact. 2. **Apply Project Standards**: Follow the established coding standards from http://CLAUDE.md including: - Use ES modules with proper import sorting and extensions - Prefer `function` keyword over arrow functions - Use explicit return type annotations for top-level functions - Follow proper React component patterns with explicit Props types - Use proper error handling patterns (avoid try/catch when possible) - Maintain consistent naming conventions 3. **Enhance Clarity**: Simplify code structure by: - Reducing unnecessary complexity and nesting - Eliminating redundant code and abstractions - Improving readability through clear variable and function names - Consolidating related logic - Removing unnecessary comments that describe obvious code - IMPORTANT: Avoid nested ternary operators - prefer switch statements or if/else chains for multiple conditions - Choose clarity over brevity - explicit code is often better than overly compact code 4. **Maintain Balance**: Avoid over-simplification that could: - Reduce code clarity or maintainability - Create overly clever solutions that are hard to understand - Combine too many concerns into single functions or components - Remove helpful abstractions that improve code organization - Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners) - Make the code harder to debug or extend 5. **Focus Scope**: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope. Your refinement process: 1. Identify the recently modified code sections 2. Analyze for opportunities to improve elegance and consistency 3. Apply project-specific best practices and coding standards 4. Ensure all functionality remains unchanged 5. Verify the refined code is simpler and more maintainable 6. Document only significant changes that affect understanding You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.