ux-to-prompts
Skill4 starsChanged 4 months agoMITView on GitHub
Turn a UX spec into build-order prompts for UI tools like v0 or Bolt.
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- actionableSkill
- astro-bootstrapSkill
- astro-patternsSkill
- autopilotSkill
- axon-code-intelSkill
- brainstormingSkill
- commit-conventionsSkill
- cross-repo-contextSkill
- django-bootstrapSkill
- django-patternsSkill
- executeSkill
- find-sessionSkill
- flutter-bootstrapSkill
- flutter-patternsSkill
- full-featureSkill
- intelSkill
- nextjs-bootstrapSkill
- nextjs-fullstack-bootstrapSkill
- nextjs-fullstack-patternsSkill
- nextjs-mui-bootstrapSkill
- nextjs-patternsSkill
- nextjs-shadcn-bootstrapSkill
- orchestratorSkill
- phase-breakdownSkill
- plan-and-scopeSkill
- prdSkill
- reactSkill
- recallSkill
- reflectSkill
- relaySkill
- rememberSkill
- scaffoldSkill
- scratchSkill
- tailwindSkill
- ux-specSkill
- verify-astroSkill
- verify-djangoSkill
- verify-flutterSkill
- verify-nextjs-fullstackSkill
- verify-nextjs-muiSkill
- verify-nextjs-shadcnSkill
- verify-nextjsSkill
- verifySkill
- visual-feedbackSkill
- work-disciplineSkill
- worktreesSkill
- wrapSkill
- write-as-friendSkill
- write-as-humanSkill
- writing-clearlySkill
- writing-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 11 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
After /ux-spec, when you want to feed specs into external UI generation tools
- Distinctive: line 18
When a UX spec is too large for a single prompt
- Distinctive: line 19
When you need build-order sequencing (foundations → features → polish)
- Distinctive: line 40
Read the UX spec and list discrete buildable features:
- Distinctive: line 97
All visual specs (colors, spacing, dimensions) relevant to that feature
- Distinctive: line 98
All states that feature can be in
- Distinctive: line 99
All interactions for that feature
- Distinctive: line 104
Leave specs vague ("appropriate styling")
- Very specific: line 108
Write to docs/plans/Build-Order-Prompts-{topic}.md with this structure:
- Distinctive: line 135
Every measurement from spec is captured in a prompt
- Distinctive: line 136
Every state from spec is captured in a prompt
- Distinctive: line 137
Every interaction from spec is captured in a prompt
- Distinctive: line 138
No prompt references another prompt
≈ “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
Skill: UX Spec to Build-Order Prompts
Adapted from UX-spec-to-prompts skill
Overview
Transform a UX specification into a sequence of self-contained prompts optimized for UI generation tools (v0, Bolt, Claude, Stitch, etc.). Each prompt builds one discrete feature/view with full context included.
When to Use
- After
/ux-spec, when you want to feed specs into external UI generation tools - When a UX spec is too large for a single prompt
- When you need build-order sequencing (foundations → features → polish)
Not for: Quick component requests, features that fit in one prompt, or projects where you're building with code directly (use /execute instead).
Build Order
Generate prompts in this sequence:
| Phase | What to Include | Why First |
| Foundation | Design tokens, shared types, base styles | Everything depends on these |
| Layout Shell | Page structure, navigation, panels | Container for all features |
| Core Components | Primary UI elements (nodes, cards, inputs) | Building blocks for features |
| Interactions | Drag-drop, connections, pickers | Depend on components existing |
| States & Feedback | Empty, loading, error, success states | Refinement of existing elements |
| Polish | Animations, responsive, edge cases | Final layer |
Extraction Process
Step 1: Identify Atomic Units
Read the UX spec and list discrete buildable features:
- Each screen/view
- Each reusable component
- Each interaction pattern
- Each state variation
Step 2: Map Dependencies
For each unit, note what it requires:
- "Node card requires design tokens"
- "Connection lines require nodes to exist"
- "Lens picker requires prompt field"
Step 3: Sequence by Dependency Graph
Order units so dependencies come first. Group tightly coupled items into single prompts.
Step 4: Write Self-Contained Prompts
For each prompt:
- Re-state relevant context — don't assume reader saw previous prompts
- Include specific measurements from the spec
- Include all states from state design (Pass 5)
- Include interaction details from affordances (Pass 3)
- Set boundaries — what this prompt does NOT include
Prompt Structure
Each generated prompt follows this template:
## [Feature Name]
### Context
[What this feature is and where it fits in the app]
### Requirements
- [Specific behavior/appearance requirement]
- [Include relevant specs: dimensions, colors, states]
### States
- Default: [description]
- [Other states from spec]
### Interactions
- [How user interacts]
- [Keyboard support if applicable]
### Constraints
- [Technical or design constraints]
- [What NOT to include]Self-Containment Rules
Each prompt MUST include:
- Enough context to understand the feature in isolation
- All visual specs (colors, spacing, dimensions) relevant to that feature
- All states that feature can be in
- All interactions for that feature
Each prompt MUST NOT:
- Reference "see previous prompt" or "as described earlier"
- Assume knowledge from other prompts
- Leave specs vague ("appropriate styling")
Output
Write to docs/plans/Build-Order-Prompts-{topic}.md with this structure:
# Build-Order Prompts: [Project Name]
## Overview
[1-2 sentence summary]
## Build Sequence
1. [Prompt name] - [brief description]
2. [Prompt name] - [brief description]
...
---
## Prompt 1: [Feature Name]
[Full self-contained prompt]
---
## Prompt 2: [Feature Name]
[Full self-contained prompt]Quality Checklist
Before finalizing:
- Every measurement from spec is captured in a prompt
- Every state from spec is captured in a prompt
- Every interaction from spec is captured in a prompt
- No prompt references another prompt
- Build order respects dependencies
- Each prompt could be given to someone with no context
Common Mistakes
| Mistake | Fix |
| Prompts too large (whole spec in one) | Break into atomic features |
| Prompts reference each other | Re-state needed context inline |
| Missing states | Cross-reference UX spec's state design (Pass 5) |
| Vague measurements ("good spacing") | Use exact values from spec |
| Wrong build order | Check dependency graph |
| Duplicated component definitions | Each component defined once, in first prompt that needs it |
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.

