shape
在编码前规划UX/UI设计
大多数AI生成的UI失败是因为跳过了设计思维。这个技能会运行结构化的发现访谈，了解用户需求、约束条件和目标，然后生成一份综合设计简报来指导实施。
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“shape”。 Shape the UX for a user onboarding flow that helps new users set up their workspace.
预期结果:
Feature Summary: First-time workspace setup for users who just signed up. Primary goal is getting users to 'aha moment' within 5 minutes while reducing anxiety about configuration complexity. Primary User Action: Complete workspace configuration with confidence. Design Direction: Calm, reassuring, progressive disclosure. Layout Strategy: Single-column vertical flow with clear progress indicators. Key States: First visit (welcome), In-progress (step indicators), Completed (success celebration), Error (validation with guidance). Interaction Model: Guided wizard with skip optional steps, auto-save after each section. Content Requirements: Welcome message, step headers, inline help text, validation messages. Recommended References: interaction-design.md, form-design.md. Open Questions: Should we allow skipping profile setup?
正在使用“shape”。 I need to design a dashboard for monitoring API health.
预期结果:
Feature Summary: Real-time API monitoring dashboard for DevOps engineers. Primary goal is rapid issue identification and root cause analysis. Primary User Action: Spot and diagnose API anomalies quickly. Design Direction: Information-dense, high contrast, fast-scanning. Layout Strategy: Grid-based with status overview top, detailed metrics bottom, left-to-right severity gradient. Key States: All systems healthy, partial degradation (warning), critical failure, loading (initial data fetch), no data. Interaction Model: Hover for details, click to drill down, auto-refresh every 30s, manual refresh available. Content Requirements: Service names, status indicators, latency numbers, error counts, timestamps, error messages. Recommended References: data-visualization.md, dashboard-design.md. Open Questions: Alert threshold preferences?
安全审计
安全Static analysis detected 22 potential issues (21 'weak cryptographic algorithm' patterns, 1 'external commands' pattern). All findings are false positives caused by pattern matching on markdown formatting (backticks around `.impeccable.md`) and common English words ('block', 'key', 'cipher'). This is a pure documentation/planning skill with no executable code, no network operations, no file system access, and no security risks. The skill runs a structured interview process and generates design documentation.
低风险问题 (1)
质量评分
你能构建什么
产品经理规划新功能
在将需求交给工程团队之前，使用此技能来建立清晰的UX方向、成功指标和设计约束。
开发者开始实施
在编码前使用以明确需要构建的内容，避免因需求误解或遗漏边界情况而返工。
设计师定义交互模式
在创建视觉模型或原型之前，围绕用户流程、状态和内容需求来组织思路。
试试这些提示
I need to design a [feature description]. Run the discovery interview and create a design brief.
Shape the UX for [feature]. I already have design context from /impeccable, so use that when discussing constraints and patterns.
Plan the UX for [feature] with these constraints: [list constraints like mobile-first, accessibility requirements, performance budgets]. Focus the interview on how these shape the design.
I want to design [feature] but I'm worried about [specific concern like complexity overwhelm]. Make sure the discovery interview explores anti-goals and what this should NOT be.
最佳实践
- 在使用此技能之前调用 /impeccable，以确保设计原则和项目上下文已加载
- 即使认为某个细节是显而易见的，也要深思熟虑地回答访谈问题
- 在确认之前仔细检查生成的设计简报
- 将确认的简报交给 /impeccable craft 或 /impeccable 以实现无缝实施
避免
- 跳过发现访谈直接跳到设计建议
- 用没有上下文的一个词答案回答访谈问题
- 期望此技能输出代码而不是设计文档
- 忽略简报确认步骤，在理解不完整的情况下继续
常见问题
何时应该使用此技能而不是 /impeccable craft？
此技能会写代码吗？
我如何使用设计简报？
为什么此技能要调用 /impeccable？
我可以用此技能来重新设计现有功能吗？
发现访谈需要多长时间？
开发者详情
文件结构
📄 SKILL.md