prototype-prompt-generator
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePrototype Prompt Generator
原型提示词生成器
Overview
概述
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.
生成用于UI/UX原型创建的全面、可投入生产的提示词。将用户需求转化为包含设计系统、调色板、组件规格、布局结构和实现指南的详细技术规范。输出的提示词经过结构化处理,便于AI工具或开发人员构建HTML/CSS/React原型时使用。
Workflow
工作流程
Step 1: Gather Requirements
步骤1:收集需求
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?
- Brand colors or visual preferences?
- Any design references or inspiration?
Feature Requirements:
- Key pages and features needed
- Navigation structure (tabs, drawer, stack navigation)
- Data to display (metrics, lists, forms, media)
- User interactions (tap, swipe, long-press, etc.)
Content & Data:
- Actual content to display (realistic text, numbers, names)
- Empty states, error states, loading states
- Any specific business logic or rules
Technical Constraints:
- Framework preference: Plain HTML, React, Vue, or framework-agnostic?
- CSS approach: Tailwind CSS, CSS Modules, styled-components?
- 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.
首先从用户处收集关键信息。通过针对性问题了解以下内容:
应用类型与用途:
- 应用类型是什么?(例如:企业工具、电商平台、社交媒体、数据看板)
- 目标用户是谁?
- 主要使用场景和工作流是什么?
平台与使用环境:
- 目标平台:iOS、Android、网页、微信小程序还是跨平台?
- 设备类型:手机、平板、桌面端还是响应式设计?
- 已知的视口尺寸(例如:iPhone的375px,桌面端的1200px)
设计偏好:
- 设计风格:企业微信、iOS原生、Material Design、Ant Design Mobile还是自定义风格?
- 品牌色或视觉偏好?
- 是否有设计参考或灵感来源?
功能需求:
- 需要的核心页面和功能
- 导航结构(标签栏、抽屉式导航、栈式导航)
- 需展示的数据(指标、列表、表单、媒体内容)
- 用户交互方式(点击、滑动、长按等)
内容与数据:
- 实际展示内容(真实文本、数字、名称)
- 空状态、错误状态、加载状态
- 特定的业务逻辑或规则
技术约束:
- 框架偏好:纯HTML、React、Vue还是无框架?
- CSS方案:Tailwind CSS、CSS Modules、styled-components?
- 图片资源:真实图片、占位图还是特定来源?
- CDN依赖或版本要求?
逐步提问(每次2-3个),避免给用户造成负担。许多细节可通过上下文推断或使用合理默认值补充。
Step 2: Select Design System
步骤2:选择设计系统
Based on the gathered requirements, choose the appropriate design system from :
references/design-systems.mdWeChat 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 to ensure accurate color codes, component dimensions, and interaction patterns.
references/design-systems.md根据收集到的需求,从中选择合适的设计系统:
references/design-systems.md企业微信风格:
- 适用场景:中国企业应用、工作管理工具、B2B平台、内部业务系统
- 特点:简洁专业,科技蓝为主色调,清晰的信息层级
- 核心受众:中国商务用户、企业环境
iOS原生风格:
- 适用场景:iOS专属应用、苹果生态集成、面向iPhone/iPad用户的应用
- 特点:极简主义、宽松布局、San Francisco字体、系统原生色彩
- 核心受众:苹果用户、消费级应用、内容导向型应用
Material Design风格:
- 适用场景:安卓优先应用、谷歌生态集成、基于Material UI的跨平台应用
- 特点:醒目图形、层级阴影系统、涟漪效果、Roboto字体
- 核心受众:安卓用户、谷歌服务、开发者工具
Ant Design Mobile风格:
- 适用场景:包含复杂数据录入和表单的企业移动应用
- 特点:高效导向、组件一致性强,适合业务应用
- 核心受众:商务用户、企业移动应用、数据密集型界面
若用户未指定设计系统,可根据以下规则推荐:
- 地域:中国用户 → 企业微信,海外用户 → iOS/Material Design
- 平台:iOS → iOS原生,Android → Material Design
- 应用类型:企业B2B → 企业微信或Ant Design,消费级应用 → iOS或Material Design
从中加载完整的设计系统规范,确保颜色代码、组件尺寸和交互模式的准确性。
references/design-systems.mdStep 3: Structure the Prompt
步骤3:构建提示词结构
Using the template from , construct a comprehensive prompt with these sections:
references/prompt-structure.md1. Role Definition
Define expertise relevant to the prototype:
undefined使用中的模板,构建包含以下部分的全面提示词:
references/prompt-structure.md1. 角色定义
明确定义与原型相关的专业能力:
undefinedRole
角色
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:你是世界级的UI/UX工程师和前端开发人员,专注于[特定领域],精通[相关技术]。
**2. 任务描述**
清晰说明需要构建的内容和设计风格: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:
- File structure (single HTML, multi-page, component-based)
- Framework and version (e.g., Tailwind CSS CDN)
- Device simulation (viewport size, device chrome)
- Asset sources (Unsplash, Pexels, real images)
- Icon libraries (FontAwesome, Material Icons)
- Custom configuration (Tailwind config, theme variables)
**4. Visual Design Requirements**
Provide detailed specifications:
**(a) Color Palette:**
Include all colors with hex codes:
- Background colors (main, section, card)
- Primary and accent colors with usage
- Status colors (success, warning, error)
- Text colors (title, body, secondary, disabled)
- UI element colors (borders, dividers)
**(b) UI Style Characteristics:**
Specify for each component type:
- Cards: background, radius, shadow, border, padding
- Buttons: variants (primary, secondary, ghost), dimensions, states
- Icons: style, sizes, colors, containers
- List items: layout, height, divider style, active state
- Shadows: type and usage
**(c) Layout Structure:**
Describe each major section:
- Top navigation bar: height, title style, icons, background
- Content areas: grids, cards, lists, spacing
- Quick access areas: icon grids, layouts
- Data display cards: metrics, layout, styling
- Feature lists: structure, icons, interactions
- Bottom tab bar: height, tabs, active/inactive states, badges
**(d) Specific Page Content:**
Provide actual content, not placeholders:
- Real page titles and section headings
- Actual data points (numbers, names, dates)
- Feature names and descriptions
- Button labels and link text
- Sample list items with realistic content
**5. Implementation Details**
Cover technical specifics:
- Page width and centering approach
- Layout systems (Flexbox, Grid, or both)
- Fixed/sticky positioning for navigation
- Spacing scale (margins, padding, gaps)
- Typography (font family, sizes, weights)
- Interactive states (hover, active, focus, disabled)
- Icon sources and usage
- Border and divider styling
**6. Tailwind Configuration**
If using Tailwind CSS, provide custom config:
```javascript
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 38. Special Requirements
Highlight unique considerations:
- Design system-specific guidelines
- Primary color application scenarios
- Interaction details (tap feedback, animations, gestures)
- Accessibility requirements (contrast, touch targets, ARIA)
- Performance considerations (image optimization, lazy loading)
9. Output Format
Specify the exact deliverable:
undefined为[应用描述]创建一个[类型]原型。
设计风格必须严格遵循[设计系统],核心关键词:[3-5个核心属性]。
**3. 技术栈规范**
列出所有技术、框架和资源:
- 文件结构(单HTML、多页面、基于组件)
- 框架及版本(例如:Tailwind CSS CDN)
- 设备模拟(视口尺寸、设备边框)
- 资源来源(Unsplash、Pexels、真实图片)
- 图标库(FontAwesome、Material Icons)
- 自定义配置(Tailwind配置、主题变量)
**4. 视觉设计要求**
提供详细的规格说明:
**(a) 调色板:**
包含所有带十六进制代码的颜色:
- 背景色(主背景、区块背景、卡片背景)
- 主色调和强调色及使用场景
- 状态色(成功、警告、错误)
- 文本颜色(标题、正文、次要文本、禁用状态)
- UI元素颜色(边框、分隔线)
**(b) UI风格特征:**
为每种组件类型指定细节:
- 卡片:背景、圆角、阴影、边框、内边距
- 按钮:变体(主按钮、次要按钮、幽灵按钮)、尺寸、状态
- 图标:风格、尺寸、颜色、容器
- 列表项:布局、高度、分隔线样式、激活状态
- 阴影:类型及使用场景
**(c) 布局结构:**
描述每个主要区块:
- 顶部导航栏:高度、标题样式、图标、背景
- 内容区域:网格、卡片、列表、间距
- 快速访问区域:图标网格、布局
- 数据展示卡片:指标、布局、样式
- 功能列表:结构、图标、交互
- 底部标签栏:高度、标签、激活/未激活状态、徽章
**(d) 特定页面内容:**
提供真实内容,而非占位符:
- 真实页面标题和区块标题
- 实际数据(数字、名称、日期)
- 功能名称及描述
- 按钮标签和链接文本
- 包含真实内容的示例列表项
**5. 实现细节**
涵盖技术细节:
- 页面宽度和居中方式
- 布局系统(Flexbox、Grid或两者结合)
- 导航栏的固定/粘性定位
- 间距规范(外边距、内边距、间隙)
- 排版(字体家族、尺寸、字重)
- 交互状态(悬停、激活、聚焦、禁用)
- 图标来源及使用方式
- 边框和分隔线样式
**6. Tailwind配置**
若使用Tailwind CSS,提供自定义配置:
```javascript
tailwind.config = {
theme: {
extend: {
colors: {
'brand-primary': '#3478F6',
// ... 所有自定义颜色
}
}
}
}7. 内容结构与层级
以树形结构可视化页面结构:
页面名称
├─ 区块1
│ ├─ 元素1
│ └─ 元素2
├─ 区块2
│ ├─ 子区块A
│ │ ├─ 项目1
│ │ └─ 项目2
│ └─ 子区块B
└─ 区块38. 特殊要求
突出独特注意事项:
- 设计系统特定指南
- 主色调应用场景
- 交互细节(点击反馈、动画、手势)
- 无障碍要求(对比度、触摸目标、ARIA)
- 性能考虑(图片优化、懒加载)
9. 输出格式
明确指定交付物:
undefinedOutput Format
输出格式
Please output complete [file type] code, ensuring:
- [Requirement 1]
- [Requirement 2] ...
The output should be production-ready and viewable at [viewport] on [device].
undefined请输出完整的[文件类型]代码,确保:
- [要求1]
- [要求2] ...
输出内容需可投入生产,并能在[设备]的[视口尺寸]下正常显示。
undefinedStep 4: Populate with Specifics
步骤4:填充具体内容
Replace all template placeholders with concrete values:
Replace vague terms with precise specifications:
- ❌ "Use blue colors" → ✅ "Primary: #3478F6 (tech blue), Link: #576B95 (link blue)"
- ❌ "Make buttons rounded" → ✅ "Border radius: 4px (Tailwind: rounded)"
- ❌ "Add some spacing" → ✅ "Card spacing: 12px, page margins: 16px"
- ❌ "Display user info" → ✅ "Show username (15px bold), email (13px gray), avatar (48px circle)"
Use real content, not placeholders:
- ❌ "Lorem ipsum dolor sit amet" → ✅ "Customer Total: 14, Today's New Customers: 1, Today's Revenue: ¥0.00"
- ❌ "[Company Name]" → ✅ "Acme Insurance Co."
- ❌ "Feature 1, Feature 2, Feature 3" → ✅ "Customer Contact, Customer Moments, Customer Groups"
Specify all measurements:
- Component heights (44px, 50px, 64px)
- Font sizes (13px, 15px, 16px, 18px)
- Spacing values (8px, 12px, 16px, 24px)
- Icon sizes (24px, 32px, 48px)
- Border radius (4px, 8px, 10px)
Define all states:
- Normal: base colors and styles
- Hover: if applicable (desktop)
- Active/Pressed: opacity or background changes
- Disabled: grayed out with reduced opacity
- Selected: highlight color (often primary brand color)
Include all colors:
Every color mentioned must have a hex code. Reference the chosen design system from for accurate values.
references/design-systems.md将模板中的所有占位符替换为具体值:
用精确规范替代模糊表述:
- ❌ "使用蓝色" → ✅ "主色调:#3478F6(科技蓝),链接色:#576B95(链接蓝)"
- ❌ "按钮做圆角" → ✅ "圆角半径:4px(Tailwind类:rounded)"
- ❌ "添加一些间距" → ✅ "卡片间距:12px,页面外边距:16px"
- ❌ "展示用户信息" → ✅ "显示用户名(15px粗体)、邮箱(13px灰色)、头像(48px圆形)"
使用真实内容,而非占位符:
- ❌ "Lorem ipsum dolor sit amet" → ✅ "客户总数:14,今日新增客户:1,今日营收:¥0.00"
- ❌ "[公司名称]" → ✅ "Acme保险有限公司"
- ❌ "功能1、功能2、功能3" → ✅ "客户联系、客户动态、客户群组"
指定所有度量值:
- 组件高度(44px、50px、64px)
- 字体尺寸(13px、15px、16px、18px)
- 间距值(8px、12px、16px、24px)
- 图标尺寸(24px、32px、48px)
- 圆角半径(4px、8px、10px)
定义所有状态:
- 正常状态:基础颜色和样式
- 悬停状态(桌面端适用)
- 激活/按下状态:透明度或背景变化
- 禁用状态:灰度化并降低透明度
- 选中状态:高亮颜色(通常为品牌主色调)
包含所有颜色:
提及的每种颜色都必须带有十六进制代码。参考中选定的设计系统获取准确值。
references/design-systems.mdStep 5: Quality Assurance
步骤5:质量保证
Before presenting the final prompt, verify against the checklist in :
references/prompt-structure.mdCompleteness 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)
- Layout relationships clear (parent-child, spacing, alignment, z-index)
Specificity Check:
- Design system explicitly named (WeChat Work, iOS Native, Material Design, etc.)
- Viewport dimensions provided (e.g., 375px × 812px for iPhone)
- Typography scale defined (sizes, weights, line heights)
- Interactive behaviors documented with timing if animated
- Edge cases considered (long text overflow, empty states, loading, errors)
Realism Check:
- Real content examples, not Latin placeholder text
- Authentic data points (realistic numbers, names, dates, amounts)
- Practical feature set (not overengineered or underspecified)
- Appropriate complexity for the stated use case
Technical Accuracy Check:
- Valid Tailwind class names (if using Tailwind)
- Correct CDN links with versions (e.g., https://cdn.tailwindcss.com)
- 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.
在呈现最终提示词前,对照中的检查清单进行验证:
references/prompt-structure.md完整性检查:
- 角色明确定义并具备相关专业能力
- 任务清晰说明需构建的内容和设计风格
- 列出所有技术栈组件及版本/CDN链接
- 完整调色板,包含所有颜色的十六进制代码
- 所有UI组件都指定了精确尺寸和样式
- 页面布局描述完整且带有精确度量值
- 提供真实、符合实际的内容(无"Lorem Ipsum"或"[名称]"这类占位符)
- 实现细节涵盖所有技术要求
- 使用Tailwind CSS时包含完整配置
- 内容层级以树形结构可视化
- 记录特殊要求和交互细节
- 明确定义输出格式和所有交付物
清晰度检查:
- 无模糊术语或描述(例如:"一些内边距"、"好看的颜色")
- 所有度量值都带有单位(px、rem、%、vh等)
- 所有颜色都用十六进制代码定义(例如:#3478F6,而非仅"蓝色")
- 描述了组件状态(正常、悬停、激活、禁用、选中)
- 布局关系清晰(父子结构、间距、对齐方式、z-index)
精确性检查:
- 明确指定设计系统(企业微信、iOS原生、Material Design等)
- 提供视口尺寸(例如:iPhone的375px × 812px)
- 定义排版规范(尺寸、字重、行高)
- 记录交互行为,带动画时长(若有)
- 考虑边缘情况(长文本溢出、空状态、加载、错误)
真实性检查:
- 使用真实内容示例,而非拉丁文占位文本
- 数据真实合理(数字、名称、日期、金额符合实际)
- 功能集实用(不过度设计或规格不足)
- 复杂度与使用场景匹配
技术准确性检查:
- 有效的Tailwind类名(若使用Tailwind)
- 正确的CDN链接及版本(例如:https://cdn.tailwindcss.com)
- 合理的HTML结构(语义化元素、层级)
- 可行的布局方案(可实现的Flexbox/Grid模式)
- 无障碍标记考虑(触摸目标≥44px、颜色对比度)
若任何检查项未通过,需优化提示词后再继续。
Step 6: Present and Iterate
步骤6:呈现与迭代
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
向用户展示生成的提示词并附上简要说明:
- 选择的设计系统及原因
- 核心设计决策
- 任何假设或默认值
- 提示词的使用方式(复制后提供给其他AI工具、开发人员或设计工具)
提供优化选项:
- "是否需要调整颜色或间距?"
- "是否要添加更多页面或功能?"
- "是否需要更换设计系统?"
- "是否有需要重点强调的特定交互或动画?"
根据反馈迭代:
若用户要求修改:
- 更新提示词的相关部分
- 保持所有部分的一致性
- 再次对照质量检查清单验证
- 展示更新后的提示词
保存或导出:
提供将提示词保存为文件的选项:
- 用于文档的Markdown文件
- 便于复制的文本文件
- 以代码块形式展示,方便直接使用
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)
- Edge cases (empty states, error states, loading states)
- Exit points (logout, back navigation, completion states)
7. Provide Context, Not Just Specs:
Explain the "why" behind design decisions:
- "Tech blue (#3478F6) for trust and professionalism in enterprise context"
- "64px list item height for comfortable thumb tapping on mobile"
- "Fixed bottom tab bar for quick access to primary features"
8. Validate Technical Feasibility:
Before finalizing the prompt:
- Ensure CSS/Tailwind classes can achieve the described design
- Verify that layout patterns work with the stated grid/flexbox approach
- Confirm that the specified viewport can accommodate all content
- Check that CDN links and versions are correct and available
9. Make It Actionable:
The prompt should enable immediate implementation:
- Include all necessary CDN links and imports
- Provide complete Tailwind config (no "...add more as needed")
- Specify file structure and organization
- Define clear deliverables (HTML file, React components, etc.)
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)
1. 默认高质量输出:
即使用户提供的需求极少,也要生成全面的提示词。删除细节比补充细节更容易。需包含:
- 完整调色板(至少8-12种颜色)
- 所有常见UI组件(按钮、卡片、列表、输入框)
- 多种组件状态(正常、激活、禁用)
- 响应式设计考虑
- 基础无障碍要求(对比度、触摸目标)
2. 智能使用设计系统默认值:
当用户需求模糊时:
- 始终如一地应用完整设计系统
- 使用设计系统中的标准组件尺寸
- 遵循既定模式(例如:企业微信的64px列表项)
- 包含平台典型的交互模式
3. 优先清晰度而非简洁性:
冗长、详细的提示词比简短、模糊的提示词能生成更好的原型。需包含:
- 精确的十六进制代码而非颜色名称
- 精确度量值而非相对术语
- 特定组件布局而非通用描述
- 真实内容而非占位文本
4. 优先移动端设计:
针对移动应用,需始终考虑:
- 安全区域(iOS刘海、安卓手势栏)
- 触摸目标尺寸(最小44px × 44px)
- 拇指可达区域(底部导航优于顶部导航)
- 主要为竖屏方向(横屏为次要选项)
- 尽可能支持单手操作
5. 平衡灵活性与精确性:
- 核心设计元素(颜色、排版、关键组件)需精确指定
- 实现细节可保留灵活性(如动画时长、微小间距调整)
- 明确标记「必备项」,将「可选项」标记为可选
6. 考虑完整用户旅程:
包含以下场景的规格说明:
- 入口点(启动页、引导页,若适用)
- 主工作流(核心功能的顺畅路径)
- 边缘情况(空状态、错误状态、加载状态)
- 出口点(登出、返回导航、完成状态)
7. 提供上下文而非仅规格:
解释设计决策的「原因」:
- "科技蓝(#3478F6)用于企业场景,传递信任与专业感"
- "64px列表项高度便于移动端拇指舒适点击"
- "固定底部标签栏便于快速访问核心功能"
8. 验证技术可行性:
在最终确定提示词前:
- 确保CSS/Tailwind类可实现所描述的设计
- 验证布局模式与指定的网格/Flexbox方案兼容
- 确认指定视口可容纳所有内容
- 检查CDN链接和版本是否正确可用
9. 确保可执行性:
提示词应支持立即实现:
- 包含所有必要的CDN链接和导入
- 提供完整的Tailwind配置(无「按需添加更多」这类表述)
- 指定文件结构和组织方式
- 明确定义交付物(HTML文件、React组件等)
10. 预判问题:
在提示词中解决常见不确定性:
- 字体回退(例如:「sans-serif」系统字体栈)
- 图片尺寸和宽高比
- 图标使用场景(何时使用FontAwesome、SVG还是emoji)
- Z-index层级(哪个元素在上层)
- 溢出行为(滚动、截断、换行)
Common Patterns
常见模式
Pattern 1: Enterprise Work Dashboard (WeChat Work Style)
模式1:企业工作看板(企业微信风格)
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
典型结构:
- 顶部导航栏(44px,标题+搜索/菜单图标)
- 快速访问网格(4列图标网格)
- 数据汇总卡片(横向布局的关键指标)
- 功能列表(图标+文本行,每行高度64px)
- 底部标签栏(5个标签,高度50px)
核心元素:
- 科技蓝(#3478F6)用于主要操作和激活状态
- 浅灰色背景上的白色卡片,带细微阴影
- 48px图标,带rounded-lg容器
- 右侧箭头导航指示器
Pattern 2: iOS Consumer App (iOS Native Style)
模式2:iOS消费级应用(iOS原生风格)
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
典型结构:
- 大标题导航栏(展开时96px)
- 基于卡片的内容区块
- 系统标准列表(行高最小44px)
- 带SF Symbols图标的标签栏
核心元素:
- 系统蓝(#007AFF)用于交互元素
- 充足留白(20px外边距、16px内边距)
- 带左侧缩进的细微分隔线
- 导航栏的半透明模糊效果
Pattern 3: Android App (Material Design Style)
模式3:Android应用(Material Design风格)
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)
典型结构:
- 顶部应用栏(移动端56px,平板端64px)
- FAB(悬浮操作按钮)用于主要操作
- 带层级阴影的卡片式内容
- 底部导航或抽屉式导航
核心元素:
- 醒目主色调(#6200EE)带层级阴影
- 点击时的涟漪效果
- 16dp网格系统
- Material图标(24px)
Pattern 4: Enterprise Form App (Ant Design Mobile)
模式4:企业表单应用(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
典型结构:
- 简洁导航栏(45px)
- 带分组输入框的表单区块
- 包含详细信息的列表视图
- 固定底部操作栏,带主按钮
核心元素:
- 专业蓝(#108EE9)用于操作按钮
- 高密度信息布局
- 清晰的表单字段标签和验证
- 多步骤流程的面包屑或步骤指示器
Troubleshooting
故障排除
Issue: User requirements are too vague
Solution: 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 mixed
Solution: 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 requirements
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.
Issue: Too many features for one prompt
Solution: 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 knowledge
Solution: 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 results
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.
问题:用户需求过于模糊
解决方案: 提出针对性问题,提供同类应用示例,推荐可选设计系统,或生成默认提示词并提供迭代优化。
问题:用户希望混合多种设计风格
解决方案: 选择一个核心设计系统确保整体结构和一致性,然后将其他系统的特定元素作为强调特性融入其中。解释利弊。
问题:用户指定了不可能或冲突的需求
解决方案: 识别冲突点,解释问题所在(例如:"64px图标无法放入44px的导航栏"),提供替代方案,并寻求澄清。
问题:单个提示词包含过多功能
解决方案: 先聚焦核心页面/工作流,生成对应的提示词,再为附加功能创建单独的提示词。保持所有提示词的一致性。
问题:用户缺乏技术知识
解决方案: 避免使用术语,用通俗语言解释设计决策,提供视觉描述而非技术术语,并在提示词中添加帮助性注释。
问题:原型提示词未生成理想结果
解决方案: 对照质量检查清单审核,确保所有颜色都有十六进制代码,所有度量值都已指定,添加更具体的内容示例,检查是否存在模糊表述。
Resources
资源
This skill includes reference documentation to support prompt generation:
此Skill包含支持提示词生成的参考文档:
references/design-systems.md
references/design-systems.md
Comprehensive specifications for major design systems:
- WeChat Work Style: Chinese enterprise applications
- iOS Native Style: Apple ecosystem apps
- Material Design: Google/Android apps
- Ant Design Mobile: Enterprise mobile apps
Each design system includes:
- Complete color palettes with hex codes
- Component specifications (dimensions, spacing, states)
- Typography scales (sizes, weights, line heights)
- Interaction patterns (animations, gestures, feedback)
- Layout guidelines (grids, spacing, safe areas)
- Code examples (Tailwind classes, CSS snippets)
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.
主流设计系统的全面规范:
- 企业微信风格:中国企业应用
- iOS原生风格:苹果生态应用
- Material Design:谷歌/Android应用
- Ant Design Mobile:企业移动应用
每个设计系统包含:
- 带十六进制代码的完整调色板
- 组件规格(尺寸、间距、状态)
- 排版规范(尺寸、字重、行高)
- 交互模式(动画、手势、反馈)
- 布局指南(网格、间距、安全区域)
- 代码示例(Tailwind类、CSS片段)
参考时机: 生成提示词时始终加载此文件,确保设计系统规格的准确性。用于填充颜色值、组件尺寸和交互模式。
references/prompt-structure.md
references/prompt-structure.md
Detailed template and guidelines for prompt construction:
- Standard prompt structure (9 sections)
- Template syntax with placeholders
- Examples for each section
- Quality checklist (completeness, clarity, specificity)
- Workflow guidance (requirements → prompt → iteration)
- Tips for effective prompts
- Common pitfalls to avoid
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.
提示词构建的详细模板和指南:
- 标准提示词结构(9个部分)
- 带占位符的模板语法
- 各部分示例
- 质量检查清单(完整性、清晰度、精确性)
- 工作流指导(需求→提示词→迭代)
- 有效提示词技巧
- 需避免的常见陷阱
参考时机: 将其作为生成所有提示词的框架。确保所有提示词的一致性和完整性。
注意: 此Skill用于生成原型创建的提示词——不直接创建原型本身。输出是全面的文本提示词,可提供给其他AI工具、开发人员或设计工具,以生成实际的HTML/CSS/React代码。