Generate comprehensive, production-ready prompts for UI/UX prototype creation. Transform user requirements into detailed technical specifications that include design systems, color palettes, component specifications, layout structures, and implementation guidelines. Output prompts are structured for optimal consumption by AI tools or human developers building HTML/CSS/React prototypes.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionprototype-prompt-generatorExecute the skills CLI command in your project's root directory to begin installation:
Fetches prototype-prompt-generator from cexll/myclaude and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate prototype-prompt-generator. Access via /prototype-prompt-generator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
2.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
2.6K
stars
Generate comprehensive, production-ready prompts for UI/UX prototype creation. Transform user requirements into detailed technical specifications that include design systems, color palettes, component specifications, layout structures, and implementation guidelines. Output prompts are structured for optimal consumption by AI tools or human developers building HTML/CSS/React prototypes.
Begin by collecting essential information from the user. Ask targeted questions to understand:
Application Type & Purpose:
Platform & Context:
Design Preferences:
Feature Requirements:
Content & Data:
Technical Constraints:
Ask questions incrementally (2-3 at a time) to avoid overwhelming the user. Many details can be inferred from context or filled with sensible defaults.
Based on the gathered requirements, choose the appropriate design system from references/design-systems.md:
WeChat Work Style:
iOS Native Style:
Material Design Style:
Ant Design Mobile Style:
If the user hasn't specified a design system, recommend one based on:
Load the complete design system specifications from references/design-systems.md to ensure accurate color codes, component dimensions, and interaction patterns.
Using the template from references/prompt-structure.md, construct a comprehensive prompt with these sections:
1. Role Definition Define expertise relevant to the prototype:
# Role
You are a world-class UI/UX engineer and frontend developer, specializing in [specific domain] using [technologies].
2. Task Description State clearly what to build and the design style:
# Task
Create a [type] prototype for [application description].
Design style must strictly follow [design system], with core keywords: [3-5 key attributes].
3. Tech Stack Specifications List all technologies, frameworks, and resources:
4. Visual Design Requirements Provide detailed specifications:
(a) Color Palette: Include all colors with hex codes:
(b) UI Style Characteristics: Specify for each component type:
(c) Layout Structure: Describe each major section:
(d) Specific Page Content: Provide actual content, not placeholders:
5. Implementation Details Cover technical specifics:
6. Tailwind Configuration If using Tailwind CSS, provide custom config:
tailwind.config = {
theme: {
extend: {
colors: {
'brand-primary': '#3478F6',
// ... all custom colors
}
}
}
}
7. Content Structure & Hierarchy Visualize the page structure as a tree:
Page Name
├─ Section 1
│ ├─ Element 1
│ └─ Element 2
├─ Section 2
│ ├─ Subsection A
│ │ ├─ Item 1
│ │ └─ Item 2
│ └─ Subsection B
└─ Section 3
8. Special Requirements Highlight unique considerations:
9. Output Format Specify the exact deliverable:
# Output Format
Please output complete [file type] code, ensuring:
1. [Requirement 1]
2. [Requirement 2]
...
The output should be production-ready and viewable at [viewport] on [device].
Replace all template placeholders with concrete values:
Replace vague terms with precise specifications:
Use real content, not placeholders:
Specify all measurements:
Define all states:
Include all colors:
Every color mentioned must have a hex code. Reference the chosen design system from references/design-systems.md for accurate values.
Before presenting the final prompt, verify against the checklist in references/prompt-structure.md:
Completeness Check:
Clarity Check:
Specificity Check:
Realism Check:
Technical Accuracy Check:
If any checks fail, refine the prompt before proceeding.
Present the generated prompt to the user with a brief explanation:
Offer refinement options:
Iterate based on feedback: If the user requests changes:
Save or Export: Offer to save the prompt to a file:
1. Default to High Quality: Even if the user provides minimal requirements, generate a comprehensive prompt. It's easier to remove details than to add them later. Include:
2. Use Design System Defaults Intelligently: When user requirements are vague:
3. Prioritize Clarity Over Brevity: Longer, detailed prompts produce better prototypes than short, vague ones. Include:
4. Think Mobile-First: For mobile applications, always consider:
5. Balance Flexibility and Specificity:
6. Consider the Full User Journey: Include specifications for:
7. Provide Context, Not Just Specs: Explain the "why" behind design decisions:
8. Validate Technical Feasibility: Before finalizing the prompt:
9. Make It Actionable: The prompt should enable immediate implementation:
10. Anticipate Questions: Address common uncertainties in the prompt:
Typical Structure:
Key Elements:
Typical Structure:
Key Elements:
Typical Structure:
Key Elements:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
prototype-prompt-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend prototype-prompt-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
prototype-prompt-generator reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added prototype-prompt-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend prototype-prompt-generator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added prototype-prompt-generator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: prototype-prompt-generator is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in prototype-prompt-generator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
prototype-prompt-generator has been reliable in day-to-day use. Documentation quality is above average for community skills.
prototype-prompt-generator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 52