This skill should be used when users need to generate detailed, structured prompts for creating UI/UX prototypes. Trigger when users request help with "create a prototype prompt", "design a mobile app", "generate UI specifications", or need comprehensive design documentation for web/mobile applications. Works with multiple design systems including WeChat Work, iOS Native, Material Design, and Ant Design Mobile.
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.
Workflow
Step 1: Gather Requirements
Begin by collecting essential information from the user. Ask targeted questions to understand:
Application Type & Purpose:
What kind of application? (e.g., enterprise tool, e-commerce, social media, dashboard)
Who are the target users?
What are the primary use cases and workflows?
Platform & Context:
Target platform: iOS, Android, Web, WeChat Mini Program, or cross-platform?
Device: Mobile phone, tablet, desktop, or responsive?
Viewport dimensions if known (e.g., 375px for iPhone, 1200px for desktop)
Design Preferences:
Design style: WeChat Work, iOS Native, Material Design, Ant Design Mobile, or custom?
Image assets: Real images, placeholders, or specific sources?
CDN dependencies or version requirements?
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.
Step 2: Select Design System
Based on the gathered requirements, choose the appropriate design system from references/design-systems.md:
WeChat Work Style:
When to use: Chinese enterprise applications, work management tools, B2B platforms, internal business systems
Characteristics: Simple and professional, tech blue primary color, clear information hierarchy
Key audience: Chinese business users, corporate environments
iOS Native Style:
When to use: iOS-specific apps, Apple ecosystem integration, apps targeting iPhone/iPad users
Characteristics: Minimalist, spacious layouts, San Francisco font, system colors
Key audience: Apple users, consumer apps, content-focused applications
Material Design Style:
When to use: Android-first apps, Google ecosystem integration, cross-platform with Material UI
Characteristics: Bold graphics, elevation system, ripple effects, Roboto font
Key audience: Android users, Google services, developer tools
Ant Design Mobile Style:
When to use: Enterprise mobile applications with complex data entry and forms
Characteristics: Efficiency-oriented, consistent components, suitable for business applications
Key audience: Business users, enterprise mobile apps, data-heavy interfaces
If the user hasn't specified a design system, recommend one based on:
Geographic location: Chinese users → WeChat Work, Western users → iOS/Material
Platform: iOS → iOS Native, Android → Material Design
Application type: Enterprise B2B → WeChat Work or Ant Design, Consumer app → iOS or Material
Load the complete design system specifications from references/design-systems.md to ensure accurate color codes, component dimensions, and interaction patterns.
Step 3: Structure the Prompt
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:
# 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].
Step 4: Populate with Specifics
Replace all template placeholders with concrete values:
Selected: highlight color (often primary brand color)
Include all colors:
Every color mentioned must have a hex code. Reference the chosen design system from references/design-systems.md for accurate values.
Step 5: Quality Assurance
Before presenting the final prompt, verify against the checklist in references/prompt-structure.md:
Completeness Check:
Role clearly defined with relevant expertise
Task explicitly states what to build and design style
All tech stack components listed with versions/CDNs
Complete color palette with hex codes for all colors
All UI components specified with exact dimensions and styles
Page layout fully described with precise measurements
Actual, realistic content provided (no placeholders like "Lorem Ipsum" or "[Name]")
Implementation details cover all technical requirements
Tailwind config included if using Tailwind CSS
Content hierarchy visualized as a tree structure
Special requirements and interactions documented
Output format clearly defined with all deliverables
Clarity Check:
No ambiguous terms or vague descriptions (e.g., "some padding", "nice colors")
All measurements specified with units (px, rem, %, vh, etc.)
All colors defined with hex codes (e.g., #3478F6, not just "blue")
Component states described (normal, hover, active, disabled, selected)
Proper HTML structure implied (semantic elements, hierarchy)
Feasible layout techniques (Flexbox/Grid patterns that work)
Accessible markup considerations (touch targets ≥44px, color contrast)
If any checks fail, refine the prompt before proceeding.
Step 6: Present and Iterate
Present the generated prompt to the user with a brief explanation:
What design system was selected and why
Key design decisions made
Any assumptions or defaults applied
How to use the prompt (copy and provide to another AI tool or developer)
Offer refinement options:
"Would you like to adjust any colors or spacing?"
"Should we add more pages or features?"
"Do you want to change the design system?"
"Any specific interactions or animations to emphasize?"
Iterate based on feedback:
If the user requests changes:
Update the relevant sections of the prompt
Maintain consistency across all sections
Re-verify against the quality checklist
Present the updated prompt
Save or Export:
Offer to save the prompt to a file:
Markdown file for documentation
Text file for easy copying
Include as a code block for immediate use
Best Practices
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:
Complete color palettes (8-12 colors minimum)
All common UI components (buttons, cards, lists, inputs)
Multiple component states (normal, active, disabled)
Responsive considerations
Accessibility basics (contrast, touch targets)
2. Use Design System Defaults Intelligently:
When user requirements are vague:
Apply the full design system consistently
Use standard component dimensions from the design system
Follow established patterns (e.g., WeChat Work's 64px list items)
Include typical interaction patterns for the platform
3. Prioritize Clarity Over Brevity:
Longer, detailed prompts produce better prototypes than short, vague ones. Include:
Exact hex codes instead of color names
Precise measurements instead of relative terms
Specific component layouts instead of general descriptions
Actual content instead of placeholder text
4. Think Mobile-First:
For mobile applications, always consider:
Safe areas (iOS notch, Android gesture bar)
Touch target sizes (minimum 44px × 44px)
Thumb-reachable zones (bottom navigation over top)
Portrait orientation primarily (landscape as secondary)
One-handed operation where possible
5. Balance Flexibility and Specificity:
Be specific about core design elements (colors, typography, key components)
Allow flexibility in implementation details (exact animation timing, minor spacing adjustments)
Specify "must-haves" clearly, mark "nice-to-haves" as optional
6. Consider the Full User Journey:
Include specifications for:
Entry points (splash screen, onboarding if applicable)
Primary workflows (happy path through key features)
10. Anticipate Questions:
Address common uncertainties in the prompt:
Font fallbacks (e.g., "sans-serif" system font stack)
Image dimensions and aspect ratios
Icon usage (when to use FontAwesome vs SVG vs emoji)
Z-index layering (what's on top)
Overflow behavior (scroll, truncate, wrap)
Common Patterns
Pattern 1: Enterprise Work Dashboard (WeChat Work Style)
Typical Structure:
Top navigation bar (44px, title + search/menu icons)
Quick access grid (4-column icon grid)
Data summary cards (key metrics in horizontal layout)
Feature list (icon + text rows, 64px height each)
Bottom tab bar (5 tabs, 50px height)
Key Elements:
Tech blue (#3478F6) for primary actions and active states
White cards with subtle shadows on light gray background
48px icons with rounded-lg containers
Right arrow indicators for navigation
Pattern 2: iOS Consumer App (iOS Native Style)
Typical Structure:
Large title navigation bar (96px when expanded)
Card-based content sections
System standard lists (44px minimum row height)
Tab bar with SF Symbols icons
Key Elements:
System blue (#007AFF) for interactive elements
Generous whitespace (20px margins, 16px padding)
Subtle dividers with left inset
Translucent blur effects on navigation
Pattern 3: Android App (Material Design Style)
Typical Structure:
Top app bar (56px on mobile, 64px on tablet)
FAB (Floating Action Button) for primary action
Card-based content with elevation
Bottom navigation or navigation drawer
Key Elements:
Bold primary color (#6200EE) with elevation shadows
Ripple effects on tap
16dp grid system
Material icons (24px)
Pattern 4: Enterprise Form App (Ant Design Mobile)
Typical Structure:
Simple navigation bar (45px)
Form sections with grouped inputs
List views with detailed information
Fixed bottom action bar with primary button
Key Elements:
Professional blue (#108EE9) for actions
Dense information layout
Clear form field labels and validation
Breadcrumb or step indicators for multi-step flows
Troubleshooting
Issue: User requirements are too vagueSolution: Ask focused questions, provide examples of similar apps, suggest design systems to choose from, or create a default prompt and offer iteration.
Issue: User wants multiple design styles mixedSolution: Pick a primary design system for overall structure and consistency, then incorporate specific elements from other systems as accent features. Explain trade-offs.
Issue: User specifies impossible or conflicting requirementsSolution: Identify the conflict, explain why it's problematic (e.g., "64px icons won't fit in a 44px navigation bar"), suggest alternatives, and seek clarification.
Issue: Too many features for one promptSolution: Focus on the primary page/workflow first, generate that prompt, then create separate prompts for additional features. Maintain consistency across prompts.
Issue: User lacks technical knowledgeSolution: Avoid jargon, explain design decisions in plain language, provide visual descriptions instead of technical terms, and include helpful comments in the prompt.
Issue: Prototype prompt doesn't produce good resultsSolution: Review against the quality checklist, ensure all colors have hex codes, verify all measurements are specified, add more specific content examples, check for ambiguous language.
Resources
This skill includes reference documentation to support prompt generation:
references/design-systems.md
Comprehensive specifications for major design systems:
WeChat Work Style: Chinese enterprise applications
When to reference: Always load this file when generating a prompt to ensure accurate design system specifications. Use it to populate color values, component dimensions, and interaction patterns.
references/prompt-structure.md
Detailed template and guidelines for prompt construction:
When to reference: Use this as the skeleton for every generated prompt. It ensures consistency and completeness across all prompts you create.
Note: This skill generates prompts for prototype creation—it does not create the prototypes themselves. The output is a comprehensive text prompt that can be provided to another AI tool, developer, or design tool to generate the actual HTML/CSS/React code.
1---
2name: prototype-prompt-generator
3description: This skill should be used when users need to generate detailed, structured prompts for creating UI/UX prototypes. Trigger when users request help with "create a prototype prompt", "design a mobile app", "generate UI specifications", or need comprehensive design documentation for web/mobile applications. Works with multiple design systems including WeChat Work, iOS Native, Material Design, and Ant Design Mobile.
4metadata:
5 source: https://skillmd.com/skills/ahang1598/prototype-prompt-generator
6---
78# Prototype Prompt Generator
910## Overview
1112Generate 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.
1314## Workflow
1516### Step 1: Gather Requirements
1718Begin by collecting essential information from the user. Ask targeted questions to understand:
1920**Application Type & Purpose:**
21- What kind of application? (e.g., enterprise tool, e-commerce, social media, dashboard)
22- Who are the target users?
23- What are the primary use cases and workflows?
2425**Platform & Context:**
26- Target platform: iOS, Android, Web, WeChat Mini Program, or cross-platform?
27- Device: Mobile phone, tablet, desktop, or responsive?
28- Viewport dimensions if known (e.g., 375px for iPhone, 1200px for desktop)
2930**Design Preferences:**
31- Design style: WeChat Work, iOS Native, Material Design, Ant Design Mobile, or custom?
32- Brand colors or visual preferences?
33- Any design references or inspiration?
3435**Feature Requirements:**
36- Key pages and features needed
37- Navigation structure (tabs, drawer, stack navigation)
38- Data to display (metrics, lists, forms, media)
39- User interactions (tap, swipe, long-press, etc.)
4041**Content & Data:**
42- Actual content to display (realistic text, numbers, names)
43- Empty states, error states, loading states
44- Any specific business logic or rules
4546**Technical Constraints:**
47- Framework preference: Plain HTML, React, Vue, or framework-agnostic?
48- CSS approach: Tailwind CSS, CSS Modules, styled-components?
49- Image assets: Real images, placeholders, or specific sources?
50- CDN dependencies or version requirements?
5152**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.
5354### Step 2: Select Design System
5556Based on the gathered requirements, choose the appropriate design system from `references/design-systems.md`:
5758**WeChat Work Style:**
59- **When to use**: Chinese enterprise applications, work management tools, B2B platforms, internal business systems
60- **Characteristics**: Simple and professional, tech blue primary color, clear information hierarchy
61- **Key audience**: Chinese business users, corporate environments
6263**iOS Native Style:**
64- **When to use**: iOS-specific apps, Apple ecosystem integration, apps targeting iPhone/iPad users
65- **Characteristics**: Minimalist, spacious layouts, San Francisco font, system colors
66- **Key audience**: Apple users, consumer apps, content-focused applications
6768**Material Design Style:**
69- **When to use**: Android-first apps, Google ecosystem integration, cross-platform with Material UI
70- **Characteristics**: Bold graphics, elevation system, ripple effects, Roboto font
71- **Key audience**: Android users, Google services, developer tools
7273**Ant Design Mobile Style:**
74- **When to use**: Enterprise mobile applications with complex data entry and forms
75- **Characteristics**: Efficiency-oriented, consistent components, suitable for business applications
76- **Key audience**: Business users, enterprise mobile apps, data-heavy interfaces
7778**If the user hasn't specified a design system**, recommend one based on:
79- Geographic location: Chinese users → WeChat Work, Western users → iOS/Material
80- Platform: iOS → iOS Native, Android → Material Design
81- Application type: Enterprise B2B → WeChat Work or Ant Design, Consumer app → iOS or Material
8283Load the complete design system specifications from `references/design-systems.md` to ensure accurate color codes, component dimensions, and interaction patterns.
8485### Step 3: Structure the Prompt
8687Using the template from `references/prompt-structure.md`, construct a comprehensive prompt with these sections:
8889**1. Role Definition**
90Define expertise relevant to the prototype:
91```
92# Role
93You are a world-class UI/UX engineer and frontend developer, specializing in [specific domain] using [technologies].
94```
9596**2. Task Description**
97State clearly what to build and the design style:
98```
99# Task
100Create a [type] prototype for [application description].
101Design style must strictly follow [design system], with core keywords: [3-5 key attributes].
102```
103104**3. Tech Stack Specifications**
105List all technologies, frameworks, and resources:
106- File structure (single HTML, multi-page, component-based)
107- Framework and version (e.g., Tailwind CSS CDN)
108- Device simulation (viewport size, device chrome)
109- Asset sources (Unsplash, Pexels, real images)
110- Icon libraries (FontAwesome, Material Icons)
111- Custom configuration (Tailwind config, theme variables)
112113**4. Visual Design Requirements**
114Provide detailed specifications:
115116**(a) Color Palette:**
117Include all colors with hex codes:
118- Background colors (main, section, card)
119- Primary and accent colors with usage
120- Status colors (success, warning, error)
121- Text colors (title, body, secondary, disabled)
122- UI element colors (borders, dividers)
123124**(b) UI Style Characteristics:**
125Specify for each component type:
126- Cards: background, radius, shadow, border, padding
127- Buttons: variants (primary, secondary, ghost), dimensions, states
128- Icons: style, sizes, colors, containers
129- List items: layout, height, divider style, active state
130- Shadows: type and usage
131132**(c) Layout Structure:**
133Describe each major section:
134- Top navigation bar: height, title style, icons, background
135- Content areas: grids, cards, lists, spacing
136- Quick access areas: icon grids, layouts
137- Data display cards: metrics, layout, styling
138- Feature lists: structure, icons, interactions
139- Bottom tab bar: height, tabs, active/inactive states, badges
140141**(d) Specific Page Content:**
142Provide actual content, not placeholders:
143- Real page titles and section headings
144- Actual data points (numbers, names, dates)
145- Feature names and descriptions
146- Button labels and link text
147- Sample list items with realistic content
148149**5. Implementation Details**
150Cover technical specifics:
151- Page width and centering approach
152- Layout systems (Flexbox, Grid, or both)
153- Fixed/sticky positioning for navigation
154- Spacing scale (margins, padding, gaps)
155- Typography (font family, sizes, weights)
156- Interactive states (hover, active, focus, disabled)
157- Icon sources and usage
158- Border and divider styling
159160**6. Tailwind Configuration**
161If using Tailwind CSS, provide custom config:
162```javascript
163tailwind.config = {
164 theme: {
165 extend: {
166 colors: {
167 'brand-primary': '#3478F6',
168 // ... all custom colors
169 }
170 }
171 }
172}
173```
174175**7. Content Structure & Hierarchy**
176Visualize the page structure as a tree:
177```
178Page Name
179├─ Section 1
180│ ├─ Element 1
181│ └─ Element 2
182├─ Section 2
183│ ├─ Subsection A
184│ │ ├─ Item 1
185│ │ └─ Item 2
186│ └─ Subsection B
187└─ Section 3
188```
189190**8. Special Requirements**
191Highlight unique considerations:
192- Design system-specific guidelines
193- Primary color application scenarios
194- Interaction details (tap feedback, animations, gestures)
195- Accessibility requirements (contrast, touch targets, ARIA)
196- Performance considerations (image optimization, lazy loading)
197198**9. Output Format**
199Specify the exact deliverable:
200```
201# Output Format
202203Please output complete [file type] code, ensuring:
2041. [Requirement 1]
2052. [Requirement 2]
206...
207208The output should be production-ready and viewable at [viewport] on [device].
209```
210211### Step 4: Populate with Specifics
212213Replace all template placeholders with concrete values:
214215**Replace vague terms with precise specifications:**
216- ❌ "Use blue colors" → ✅ "Primary: #3478F6 (tech blue), Link: #576B95 (link blue)"
217- ❌ "Make buttons rounded" → ✅ "Border radius: 4px (Tailwind: rounded)"
218- ❌ "Add some spacing" → ✅ "Card spacing: 12px, page margins: 16px"
219- ❌ "Display user info" → ✅ "Show username (15px bold), email (13px gray), avatar (48px circle)"
220221**Use real content, not placeholders:**
222- ❌ "Lorem ipsum dolor sit amet" → ✅ "Customer Total: 14, Today's New Customers: 1, Today's Revenue: ¥0.00"
223- ❌ "[Company Name]" → ✅ "Acme Insurance Co."
224- ❌ "Feature 1, Feature 2, Feature 3" → ✅ "Customer Contact, Customer Moments, Customer Groups"
225226**Specify all measurements:**
227- Component heights (44px, 50px, 64px)
228- Font sizes (13px, 15px, 16px, 18px)
229- Spacing values (8px, 12px, 16px, 24px)
230- Icon sizes (24px, 32px, 48px)
231- Border radius (4px, 8px, 10px)
232233**Define all states:**
234- Normal: base colors and styles
235- Hover: if applicable (desktop)
236- Active/Pressed: opacity or background changes
237- Disabled: grayed out with reduced opacity
238- Selected: highlight color (often primary brand color)
239240**Include all colors:**
241Every color mentioned must have a hex code. Reference the chosen design system from `references/design-systems.md` for accurate values.
242243### Step 5: Quality Assurance
244245Before presenting the final prompt, verify against the checklist in `references/prompt-structure.md`:
246247**Completeness Check:**
248- [ ] Role clearly defined with relevant expertise
249- [ ] Task explicitly states what to build and design style
250- [ ] All tech stack components listed with versions/CDNs
251- [ ] Complete color palette with hex codes for all colors
252- [ ] All UI components specified with exact dimensions and styles
253- [ ] Page layout fully described with precise measurements
254- [ ] Actual, realistic content provided (no placeholders like "Lorem Ipsum" or "[Name]")
255- [ ] Implementation details cover all technical requirements
256- [ ] Tailwind config included if using Tailwind CSS
257- [ ] Content hierarchy visualized as a tree structure
258- [ ] Special requirements and interactions documented
259- [ ] Output format clearly defined with all deliverables
260261**Clarity Check:**
262- [ ] No ambiguous terms or vague descriptions (e.g., "some padding", "nice colors")
263- [ ] All measurements specified with units (px, rem, %, vh, etc.)
264- [ ] All colors defined with hex codes (e.g., #3478F6, not just "blue")
265- [ ] Component states described (normal, hover, active, disabled, selected)
266- [ ] Layout relationships clear (parent-child, spacing, alignment, z-index)
267268**Specificity Check:**
269- [ ] Design system explicitly named (WeChat Work, iOS Native, Material Design, etc.)
270- [ ] Viewport dimensions provided (e.g., 375px × 812px for iPhone)
271- [ ] Typography scale defined (sizes, weights, line heights)
272- [ ] Interactive behaviors documented with timing if animated
273- [ ] Edge cases considered (long text overflow, empty states, loading, errors)
274275**Realism Check:**
276- [ ] Real content examples, not Latin placeholder text
277- [ ] Authentic data points (realistic numbers, names, dates, amounts)
278- [ ] Practical feature set (not overengineered or underspecified)
279- [ ] Appropriate complexity for the stated use case
280281**Technical Accuracy Check:**
282- [ ] Valid Tailwind class names (if using Tailwind)
283- [ ] Correct CDN links with versions (e.g., https://cdn.tailwindcss.com)
284- [ ] Proper HTML structure implied (semantic elements, hierarchy)
285- [ ] Feasible layout techniques (Flexbox/Grid patterns that work)
286- [ ] Accessible markup considerations (touch targets ≥44px, color contrast)
287288If any checks fail, refine the prompt before proceeding.
289290### Step 6: Present and Iterate
291292**Present the generated prompt to the user** with a brief explanation:
293- What design system was selected and why
294- Key design decisions made
295- Any assumptions or defaults applied
296- How to use the prompt (copy and provide to another AI tool or developer)
297298**Offer refinement options:**
299- "Would you like to adjust any colors or spacing?"
300- "Should we add more pages or features?"
301- "Do you want to change the design system?"
302- "Any specific interactions or animations to emphasize?"
303304**Iterate based on feedback:**
305If the user requests changes:
3061. Update the relevant sections of the prompt
3072. Maintain consistency across all sections
3083. Re-verify against the quality checklist
3094. Present the updated prompt
310311**Save or Export:**
312Offer to save the prompt to a file:
313- Markdown file for documentation
314- Text file for easy copying
315- Include as a code block for immediate use
316317## Best Practices
318319**1. Default to High Quality:**
320Even if the user provides minimal requirements, generate a comprehensive prompt. It's easier to remove details than to add them later. Include:
321- Complete color palettes (8-12 colors minimum)
322- All common UI components (buttons, cards, lists, inputs)
323- Multiple component states (normal, active, disabled)
324- Responsive considerations
325- Accessibility basics (contrast, touch targets)
326327**2. Use Design System Defaults Intelligently:**
328When user requirements are vague:
329- Apply the full design system consistently
330- Use standard component dimensions from the design system
331- Follow established patterns (e.g., WeChat Work's 64px list items)
332- Include typical interaction patterns for the platform
333334**3. Prioritize Clarity Over Brevity:**
335Longer, detailed prompts produce better prototypes than short, vague ones. Include:
336- Exact hex codes instead of color names
337- Precise measurements instead of relative terms
338- Specific component layouts instead of general descriptions
339- Actual content instead of placeholder text
340341**4. Think Mobile-First:**
342For mobile applications, always consider:
343- Safe areas (iOS notch, Android gesture bar)
344- Touch target sizes (minimum 44px × 44px)
345- Thumb-reachable zones (bottom navigation over top)
346- Portrait orientation primarily (landscape as secondary)
347- One-handed operation where possible
348349**5. Balance Flexibility and Specificity:**
350- Be specific about core design elements (colors, typography, key components)
351- Allow flexibility in implementation details (exact animation timing, minor spacing adjustments)
352- Specify "must-haves" clearly, mark "nice-to-haves" as optional
353354**6. Consider the Full User Journey:**
355Include specifications for:
356- Entry points (splash screen, onboarding if applicable)
357- Primary workflows (happy path through key features)
358- Edge cases (empty states, error states, loading states)
359- Exit points (logout, back navigation, completion states)
360361**7. Provide Context, Not Just Specs:**
362Explain the "why" behind design decisions:
363- "Tech blue (#3478F6) for trust and professionalism in enterprise context"
364- "64px list item height for comfortable thumb tapping on mobile"
365- "Fixed bottom tab bar for quick access to primary features"
366367**8. Validate Technical Feasibility:**
368Before finalizing the prompt:
369- Ensure CSS/Tailwind classes can achieve the described design
370- Verify that layout patterns work with the stated grid/flexbox approach
371- Confirm that the specified viewport can accommodate all content
372- Check that CDN links and versions are correct and available
373374**9. Make It Actionable:**
375The prompt should enable immediate implementation:
376- Include all necessary CDN links and imports
377- Provide complete Tailwind config (no "...add more as needed")
378- Specify file structure and organization
379- Define clear deliverables (HTML file, React components, etc.)
380381**10. Anticipate Questions:**
382Address common uncertainties in the prompt:
383- Font fallbacks (e.g., "sans-serif" system font stack)
384- Image dimensions and aspect ratios
385- Icon usage (when to use FontAwesome vs SVG vs emoji)
386- Z-index layering (what's on top)
387- Overflow behavior (scroll, truncate, wrap)
388389## Common Patterns
390391### Pattern 1: Enterprise Work Dashboard (WeChat Work Style)
392**Typical Structure:**
393- Top navigation bar (44px, title + search/menu icons)
394- Quick access grid (4-column icon grid)
395- Data summary cards (key metrics in horizontal layout)
396- Feature list (icon + text rows, 64px height each)
397- Bottom tab bar (5 tabs, 50px height)
398399**Key Elements:**
400- Tech blue (#3478F6) for primary actions and active states
401- White cards with subtle shadows on light gray background
402- 48px icons with rounded-lg containers
403- Right arrow indicators for navigation
404405### Pattern 2: iOS Consumer App (iOS Native Style)
406**Typical Structure:**
407- Large title navigation bar (96px when expanded)
408- Card-based content sections
409- System standard lists (44px minimum row height)
410- Tab bar with SF Symbols icons
411412**Key Elements:**
413- System blue (#007AFF) for interactive elements
414- Generous whitespace (20px margins, 16px padding)
415- Subtle dividers with left inset
416- Translucent blur effects on navigation
417418### Pattern 3: Android App (Material Design Style)
419**Typical Structure:**
420- Top app bar (56px on mobile, 64px on tablet)
421- FAB (Floating Action Button) for primary action
422- Card-based content with elevation
423- Bottom navigation or navigation drawer
424425**Key Elements:**
426- Bold primary color (#6200EE) with elevation shadows
427- Ripple effects on tap
428- 16dp grid system
429- Material icons (24px)
430431### Pattern 4: Enterprise Form App (Ant Design Mobile)
432**Typical Structure:**
433- Simple navigation bar (45px)
434- Form sections with grouped inputs
435- List views with detailed information
436- Fixed bottom action bar with primary button
437438**Key Elements:**
439- Professional blue (#108EE9) for actions
440- Dense information layout
441- Clear form field labels and validation
442- Breadcrumb or step indicators for multi-step flows
443444## Troubleshooting
445446**Issue: User requirements are too vague**
447**Solution:** Ask focused questions, provide examples of similar apps, suggest design systems to choose from, or create a default prompt and offer iteration.
448449**Issue: User wants multiple design styles mixed**
450**Solution:** Pick a primary design system for overall structure and consistency, then incorporate specific elements from other systems as accent features. Explain trade-offs.
451452**Issue: User specifies impossible or conflicting requirements**
453**Solution:** Identify the conflict, explain why it's problematic (e.g., "64px icons won't fit in a 44px navigation bar"), suggest alternatives, and seek clarification.
454455**Issue: Too many features for one prompt**
456**Solution:** Focus on the primary page/workflow first, generate that prompt, then create separate prompts for additional features. Maintain consistency across prompts.
457458**Issue: User lacks technical knowledge**
459**Solution:** Avoid jargon, explain design decisions in plain language, provide visual descriptions instead of technical terms, and include helpful comments in the prompt.
460461**Issue: Prototype prompt doesn't produce good results**
462**Solution:** Review against the quality checklist, ensure all colors have hex codes, verify all measurements are specified, add more specific content examples, check for ambiguous language.
463464## Resources
465466This skill includes reference documentation to support prompt generation:
467468### references/design-systems.md
469Comprehensive specifications for major design systems:
470- **WeChat Work Style**: Chinese enterprise applications
471- **iOS Native Style**: Apple ecosystem apps
472- **Material Design**: Google/Android apps
473- **Ant Design Mobile**: Enterprise mobile apps
474475Each design system includes:
476- Complete color palettes with hex codes
477- Component specifications (dimensions, spacing, states)
478- Typography scales (sizes, weights, line heights)
479- Interaction patterns (animations, gestures, feedback)
480- Layout guidelines (grids, spacing, safe areas)
481- Code examples (Tailwind classes, CSS snippets)
482483**When to reference:** Always load this file when generating a prompt to ensure accurate design system specifications. Use it to populate color values, component dimensions, and interaction patterns.
484485### references/prompt-structure.md
486Detailed template and guidelines for prompt construction:
487- Standard prompt structure (9 sections)
488- Template syntax with placeholders
489- Examples for each section
490- Quality checklist (completeness, clarity, specificity)
491- Workflow guidance (requirements → prompt → iteration)
492- Tips for effective prompts
493- Common pitfalls to avoid
494495**When to reference:** Use this as the skeleton for every generated prompt. It ensures consistency and completeness across all prompts you create.
496497---
498499**Note:** This skill generates prompts for prototype creation—it does not create the prototypes themselves. The output is a comprehensive text prompt that can be provided to another AI tool, developer, or design tool to generate the actual HTML/CSS/React code.
Run npx get-skill add ahang1598/prototype-prompt-generator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
This skill should be used when users need to generate detailed, structured prompts for creating UI/UX prototypes. Trigger when users request help with "create a prototype prompt", "design a mobile app", "generate UI specifications", or need comprehensive design documentation for web/mobile applications. Works with multiple design systems including WeChat Work, iOS Native, Material Design, and Ant Design Mobile. It is listed under AI & ML on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
ahang1598 (@ahang1598) published this skill. Their other Agent Skills are listed on their SkillMD profile.