design-auto
Skill1 starsChanged 4 months agoMITView on GitHub
Designs, builds, audits, polishes, prototypes, and reviews frontend interfaces through one integrated workflow. Use for UI/UX work, visual design, accessibility, responsive behavior, design systems, animation, motion audits, gesture-driven interfaces, and final product polish. Add --deep only for exhaustive phase-gated work.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- VladTheProgrammer/claude-asimovtheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- VladTheProgrammer/claude-asimov★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Before judging or changing an existing interface:
- Distinctive: line 46
Read the target and at least one representative neighboring component.
- Distinctive: line 47
Read the project's tokens, theme, global styles, and shared primitives.
- Very specific: line 50
If .superdesign/init/ exists and the mode is prototype, read all of it.
- Distinctive: line 52
Do not block ordinary work merely because PRODUCT.md, DESIGN.md, or a specific design tool is absent.
- Distinctive: line 58
Ask only when the missing answer materially changes the design or causes destructive work.
- Distinctive: line 59
Use real content when available.
- Distinctive: line 62
Never commit, publish, or deploy without explicit permission.
- Distinctive: line 63
Verify in proportion to risk: static inspection, tests, responsive checks, keyboard flow, and browser interaction where available.
- Distinctive: line 67
Start with a phase plan containing:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Integrated Design Workflow
Handle the request directly. Do not invoke a chain of overlapping design skills. Select the smallest mode below, read only its reference file, and continue to the mode's natural stopping point.
Modes
| Goal | Mode | Required reference |
| New page, feature, component, or redesign | build | BUILD.md |
| UX, accessibility, visual, or technical review | audit | AUDIT.md |
| Nearly finished UI needs refinement | polish | POLISH.md |
| Explore visual directions before implementation | prototype | PROTOTYPE.md |
| Add, review, audit, name, or improve motion | motion | MOTION.md |
Combine references only when the outcome truly crosses modes:
- Build with important motion:
BUILD.md+MOTION.md. - Full release review:
AUDIT.md+MOTION.md. - Motion-only review or codebase audit:
MOTION.mdalone. - Prototype then implement only when the user has asked for both.
Invocation variants
--shape: clarify users, hierarchy, flows, and acceptance criteria before code.--craft: implement from a clear or confirmed brief.--component: constrain work to one component and direct dependencies.--visual,--tech,--a11y,--full: select audit depth.--bolder,--quieter,--typeset,--layout,--clarify,--harden: select polish focus.--animate: add purposeful motion usingMOTION.md.--motion-review: review motion in a diff and return Block/Approve.--motion-audit [quick|standard|deep]: survey the codebase and produce prioritized findings; write implementation plans only after selection.--gesture: design drag, swipe, sheet, spring, or momentum interactions.--vocabulary: identify the precise name for a described animation effect.--deep: exhaustive, phase-gated design work. Use only when explicitly requested.
Required context
Before judging or changing an existing interface:
- Read the target and at least one representative neighboring component.
- Read the project's tokens, theme, global styles, and shared primitives.
- Infer the product register: task-focused product UI or expressive brand/marketing.
- Preserve established conventions unless a concrete UX gain justifies changing them.
- If
.superdesign/init/exists and the mode isprototype, read all of it.
Do not block ordinary work merely because PRODUCT.md, DESIGN.md, or a specific design tool is absent. Existing code and the user's brief are valid context.
Operating rules
- With a target but an unclear goal, perform lightweight triage and choose the safest mode.
- With neither a target nor an actionable outcome, ask one concise blocking question.
- Ask only when the missing answer materially changes the design or causes destructive work.
- Use real content when available. Do not ship placeholder-only UI unless asked for a wireframe.
- Extend existing primitives before creating new abstractions.
- Implementation requests authorize relevant code edits; reviews and audits remain read-only unless fixes are requested.
- Never commit, publish, or deploy without explicit permission.
- Verify in proportion to risk: static inspection, tests, responsive checks, keyboard flow, and browser interaction where available.
--deep
Start with a phase plan containing:
- Context and current-system discovery
- Shape or prototype
- Build
- Audit
- Polish
State the aesthetic direction, measurable success criteria, and stop condition before implementation. Do not use --deep for ordinary broad requests.
Output
Lead with the outcome. End with a compact execution summary:
- completed work
- design decisions
- verification performed
- blockers or assumptions
- artifacts or files produced
- next safe action, only if one remains
For audits, prioritize evidence and concrete fixes over generic advice. For implementations, report files changed rather than repeating the code.
Sources
This integrated workflow incorporates and adapts guidance from Emil Kowalski's skills repository, Apple's fluid-interface principles, Vercel's Web Interface Guidelines, and the previously installed local design workflows. Emil-derived material is used under the MIT license; see LICENSE-EMIL-KOWALSKI.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

