design-first
/design-first
Share a design and wait for the user to confirm before making any change. Use whenever the user asks for work that would edit files (feature, fix, refactor, docs, config), before the first edit and before start-work, even when the request sounds clear.
- Author
- chrishunt ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Share a design and wait for the user to confirm before making any change. Use whenever the user asks for work that would edit files (feature, fix, refactor, docs, config), before the first edit and before start-work, even when the request sounds clear.
Original author description
Share a design and wait for the user to confirm before making any change. Use whenever the user asks for work that would edit files (feature, fix, refactor, docs, config), before the first edit and before start-work, even when the request sounds clear.
How it works
- 1. Look before proposing
- 2. Check what's current
- 3. Hold it to the principles
- 4. Share the design
- 5. Build only after a clear yes
SKILL.md preview
---
name: design-first
description: Share a design and wait for the user to confirm before making any change. Use whenever the user asks for work that would edit files (feature, fix, refactor, docs, config), before the first edit and before start-work, even when the request sounds clear.
---
# Design first, then build
The user wants to see the plan and say go before anything changes. Reading, searching, and running read-only commands are fine; editing files, creating branches or worktrees, and committing are not, until they confirm.
## 1. Look before proposing
Read enough of the code, docs, and notes to make the design concrete. Don't guess at things you can check.
## 2. Check what's current
Model knowledge lags, and feeling sure about a library or pattern is not evidence that it's still current. Whenever the design picks a library, framework, API, tool, or approach, search the web for its current version and what's recommended now, and compare that with what the repo already uses. Staying on the existing stack is often right, but say when it's behind. Scale the effort to the change: a one-line fix with nothing external needs no research; a new feature or dependency does.
## 3. Hold it to the principles
Load the `jig:build-principles` skill and check the design against it. Build in what applies rather than leaving it for review: offline behavior, data safety, tests, error handling, rendering screens before handing off. Any principle the design bends goes under **Decisions** with the reason.
## 4. Share the design
Keep it as short as the change allows: a few lines for a small fix, a page for a feature.
- **Goal:** what changes for the user, in one or two sentences.
- **Approach:** how it will work, and the files or pieces it touches.
- **Current practice:** what you checked, what you found, and source links; or one line saying why no research was needed.
- **Decisions:** any choice the user should make, each with your recommendation.
- **Not doing:** anything nearby you are deliberately leaving out.
End by asking whether they're ready for you to start. Then stop and wait.
## 5. Build only after a clear yes
- Feedback means revise and share again, not start.
- Approval covers that design. If the work turns out to need something materially different, stop and check back before going on.
- Once confirmed, continue with `jig:start-work`.
Skip this only when the user says to go ahead without a design ("just do it", "no need to check").
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · chrishunt/claude-plugins | 90 | MIT |
| rohitg00/skillkit | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version ec38e3eff8b5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100refactor-plan
Create a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes. - 100work-pipeline
Triggers the WORK-PIPELINE when a user request starts with a [] tag (e.g., [new-feature], [bugfix], [WORK start]). Use this skill whenever you detect a [] tag at the beginning of a user message. - 100requirements-and-design
Use before building anything new or changing behavior — a feature, component, app, API, refactor with visible effects, or any "build/add/make X" request — to understand what the user actually needs, compare approaches, and get an approved design before code is written. Covers… - 86plan
Design an implementation plan before writing code — where the change lands, what it will touch, what could break, and the steps in order. Use when asked to plan a feature, scope a change, or figure out how to approach an edit before making it. To assess a change that already… - 100ticket-work
Seven steps that carry one ticket from clarifying the request to a merged pull request. Use at the start of a request to implement a component, page, or route, add or change a feature, fix a bug that needs more than a one-line change, or refactor a module, including when the… - 90plan
Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.