/improve
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions.
$ npx -y skills add owainlewis/blueprint --skill improve --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/improve
Context preview
The summary Claude sees to decide when to auto-load this skill.
Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions.
SKILL.md
improve.SKILL.mdname: improve description: "Makes existing code easier to understand without changing behavior. Use to simplify structure, remove duplication or dead code, improve names, or remove unnecessary abstractions." user-invocable: true argument-hint: "[code, files, diff, branch, or improvement focus]"
Improve
Workflow
1. Identify the target from the request, current diff, or recently changed code. 2. Read the target, its tests, and relevant surrounding code. State the behavior that must not change. 3. If that behavior lacks tests, add focused coverage before refactoring. If automated tests cannot exercise it, explain why and give other evidence. 4. Find unnecessary complexity, duplication, dead code, weak names, awkward boundaries, and abstractions that cost more than they help. 5. Make focused improvements by deleting, deduplicating, renaming, simplifying, extracting, or inlining. 6. Preserve public interfaces, data shapes, errors, and user-visible behavior unless the user explicitly asks to change them. 7. Run tests and checks that cover behavior the refactor can affect. Report what improved, what behavior was preserved, and the evidence.
Boundaries
- Do not add product scope or absorb unrelated cleanup.
- Prefer a few clear edits over a broad rewrite.
- Preserve behavior even when a redesign would be easier.
A small set of instructions for AI coding. Blueprint helps agents decide what to build, make focused changes, test them, get an independent review, and open pull requests.
Other skills on blueprint.
- /architecture-review
Reviews a technical proposal before implementation. Use for specs, designs, RFCs, ADRs, architecture proposals, and issues that specify how a system change should work. Finds material ambiguity and flaws in correctness, scalability, performance, security, operations, and proof.
Open skill - /architecture
Explains how an existing system works today. Use for architecture maps, audits, or ARCHITECTURE.md. Return a chat report unless the user asks for a file. Use design for proposed changes.
Open skill - /design
Writes a clear spec for a proposed feature or system change. Use when important product or technical choices must be settled before coding. Covers behavior, interfaces, failures, risks, acceptance criteria, and tests. Use architecture to explain the current system.
Open skill - /plan
Turns an approved design or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
Open skill - /review
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
Open skill - /task-to-pr
Completes one or more tasks. Creates one tested and reviewed pull request for each task. Use to implement, build, fix, or deliver tasks, tickets, pull requests, or a milestone.
Open skill