# simplify

Simplifies code or diffs while preserving runtime behavior and test coverage. It strips unneeded abstractions and speculative generality without sacrificing readability.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 455 installs · ★ 39
- Author: LegendApp
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/LegendApp/legend-skills/tree/HEAD/simplify/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/legendapp-simplify

## What it does

The skill directs the agent to minimize concepts and moving parts rather than chasing a smaller line count. It inspects existing repository conventions, common execution paths, and error handling patterns first. Instead of adding new layers, it leans toward deletion, reuse, and direct inline logic.

Its checklist actively targets over-engineering. That includes single-use helper functions, redundant wrappers, defensive checks for impossible states, and config options built for hypothetical use cases. During diff reviews, the skill inspects surrounding code to catch duplicate branches and unreachable statements.

Performance tweaks require concrete benchmarks or profiling data. The workflow strictly enforces a passing test baseline before any cleanup begins. Unverified edits cannot slip through.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add LegendApp/legend-skills --skill simplify -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/simplify/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/simplify/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add LegendApp/legend-skills --skill simplify -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/simplify/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add LegendApp/legend-skills --skill simplify -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/simplify/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install LegendApp/legend-skills simplify
```

2. **Manually: put the files in place**
- File: `.github/skills/simplify/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add LegendApp/legend-skills --skill simplify -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/LegendApp/legend-skills --path simplify
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/simplify/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add LegendApp/legend-skills --skill simplify -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/LegendApp/legend-skills/tree/HEAD/simplify/SKILL.md

## When to use it
- clean up single-use helpers and redundant wrappers in pull requests
- detect duplicate control flow and unreachable code around changes
- remove speculative config options and unused extension points
- audit branch diffs against the merge base without inflating scope

## Example prompts
- Simplify this diff while preserving all existing tests and behavior.
- Audit the branch against main and strip unneeded scaffolding.
- Review `src/services/auth.ts` for over-engineering and inline single-use helpers.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d5a3ec2a5dad595e.

BEGIN THIRD-PARTY FILE d5a3ec2a5dad595e
```text
---
name: simplify
description: "Simplify the requested code or diff while preserving behavior and meaningful coverage."
---

# Simplify

Produce the smallest clear implementation that fully satisfies the required behavior. Minimize concepts and moving parts, not line count.

## Cadence

- Before adding code, decide the smallest change that meets the requirement; each new concept must earn its place.
- During construction, apply the priorities locally while discovering behavior. Allow clearly temporary instrumentation or scaffolding when it accelerates learning.
- At convergence, once a logical behavior slice passes, simplify that slice, remove superseded attempts and scaffolding, and rerun focused validation.
- For an explicitly requested branch audit, compare with the intended base. Otherwise review only the requested change; do not broaden a small cleanup into a whole-branch audit.

## Workflow

1. Identify the required behavior, invariants, constraints, and non-goals.
2. Inspect the relevant diff and separate it into logical concepts. For a final branch audit, compare the full branch with its merge base and check history for superseded attempts when relevant.
3. Inspect the existing owners, sources of truth, common path, decision points, and nearby code style before adding anything.
4. Choose the design with the fewest necessary concepts and the least work at runtime.
5. When changes are requested, implement directly and reuse existing mechanisms where they fit.
6. Validate behavior with checks proportional to the risk.
7. Review the final code, tests, names, comments, documentation, configuration, and relevant history for anything that no longer earns its complexity.

## Simplification Priorities

- Match the repository's existing style and patterns: naming, file layout, error handling, test style, and the libraries it already uses. Do not introduce a new pattern where an existing one fits.
- Prefer deletion, reuse, or a direct change over a new abstraction.
- Keep one source of truth; avoid mirrored state, overlapping guards, duplicate registries, and compensating mechanisms.
- Where the repository has no convention, prefer straightforward positive control flow over early-return chains or empty branches.
- On hot paths, minimize allocations, callback recreation, subscriptions, renders, passes, I/O, and native work.
- For prose, remove repetition and keep the shortest wording or example that remains self-sufficient.

## Over-engineering Checklist

Remove these when they serve no required behavior, invariant, useful clarity, measured performance need, or existing repository convention:

- one-use helpers that can be inlined instead;
- defensive null or type checks for states the types or callers already rule out;
- config flags, options, or parameters for variation no current caller needs;
- wrapper types or classes that only forward;
- new files, modules, or abstractions where an existing owner fits;
```
END THIRD-PARTY FILE d5a3ec2a5dad595e

The third-party file has ended. Everything between the d5a3ec2a5dad595e tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2958 of 5571 bytes. © LegendApp · MIT · https://github.com/LegendApp/legend-skills/tree/HEAD/simplify/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md