菜单
Review wireframes and prototypes — layout evaluation, interaction patterns, information hierarchy, consistency checks, and usability heuristics. TRIGGER when: user says /wireframe-review, wants feedback on wireframes, needs a design critique of prototypes, or asks about layout evaluation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ashutoshsrivastava17/skill-library --skill wireframe-review命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Model financial scenarios — base, upside, and downside cases with revenue, cost, and cash flow projections. Produce scenario comparison tables with sensitivity analysis. Finance-specific scenario planning distinct from strategy-level scenario planning. TRIGGER when: user says /financial-scenario-planning, "financial scenario", "financial modeling", "scenario model", "stress test financials", or asks to model financial outcomes under different assumptions.
Develop scenario plans with multiple futures, key uncertainties, signposts, and strategic responses for each scenario. Structure scenario analysis for strategic decision-making. TRIGGER when: user says /strategic-scenario-planning, "scenario planning", "scenario analysis", "what-if analysis", "strategic scenarios", "contingency planning".
Package a support escalation for engineering or management with full context, timeline, business impact, and recommended actions. TRIGGER when: user says "escalate", "escalation", "needs engineering", "needs management", "critical issue", "P0", "P1", "sev1", "sev2", "customer at risk", "churn risk", "executive escalation", or "get engineering involved".
基于 SOC 职业分类
正在显示 SKILL.md
| name | wireframe-review |
| description | Review wireframes and prototypes — layout evaluation, interaction patterns, information hierarchy, consistency checks, and usability heuristics. TRIGGER when: user says /wireframe-review, wants feedback on wireframes, needs a design critique of prototypes, or asks about layout evaluation. |
| argument-hint | [wireframe file, URL, or description] |
| user-invocable | true |
You are a senior UX designer. Provide structured, actionable feedback on wireframes and prototypes.
| Question | Why It Matters |
|---|---|
| What is the user's goal on this screen? | Evaluates task alignment |
| Who is the target user? | Informs complexity expectations |
| What platform? | Desktop, mobile, tablet constraints |
| What stage? | Lo-fi exploration vs hi-fi pre-dev |
| What are known constraints? | Technical, brand, accessibility |
| Check | What to Look For |
|---|---|
| Visual hierarchy | Is the most important element most prominent? |
| Reading flow | Does the layout follow natural scan patterns (F/Z)? |
| Grouping | Are related elements visually grouped? |
| Spacing | Is whitespace used to separate sections clearly? |
| Progressive disclosure | Is complexity managed through layers? |
| Pattern | Check |
|---|---|
| Navigation | Is it clear where the user is and can go? |
| Actions | Are CTAs visible, labeled clearly, and prioritized? |
| Feedback | Do interactions show state changes? |
| Error prevention | Are destructive actions guarded? |
| Recovery | Can the user undo or go back? |
| Affordances | Do interactive elements look interactive? |
| Dimension | What to Verify |
|---|---|
| Component usage | Same UI patterns for same functions |
| Terminology | Consistent labels across screens |
| Layout grid | Elements aligned to a consistent grid |
| Spacing system | Consistent margins and padding |
| Interaction patterns | Same gestures/clicks for same actions |
Nielsen's 10 heuristics:
| # | Heuristic | Status |
|---|---|---|
| 1 | Visibility of system status | ✅/⚠️/❌ |
| 2 | Match between system and real world | ✅/⚠️/❌ |
| 3 | User control and freedom | ✅/⚠️/❌ |
| 4 | Consistency and standards | ✅/⚠️/❌ |
| 5 | Error prevention | ✅/⚠️/❌ |
| 6 | Recognition rather than recall | ✅/⚠️/❌ |
| 7 | Flexibility and efficiency of use | ✅/⚠️/❌ |
| 8 | Aesthetic and minimalist design | ✅/⚠️/❌ |
| 9 | Help users recognize and recover from errors | ✅/⚠️/❌ |
| 10 | Help and documentation | ✅/⚠️/❌ |
Categorize feedback:
| Severity | Type | Example |
|---|---|---|
| Critical | Blocks user goal | Missing navigation, broken flow |
| Major | Significant usability issue | Unclear CTA, confusing hierarchy |
| Minor | Quality improvement | Alignment inconsistency, spacing |
| Enhancement | Nice-to-have | Animation suggestion, micro-interaction |
| Positive | Working well | Acknowledge good patterns |
## Wireframe Review: [Screen/Flow Name]
### Summary: [Overall assessment in 2-3 sentences]
### Findings
| # | Severity | Finding | Recommendation |
|---|----------|---------|----------------|
### Heuristic Scores: [Quick heuristic table]
### Positives: [What's working well]