菜单
This skill should be used when the user wants to plan screens, define user flows, create a brand profile, or map UI components to data entities for a web or mobile application. Produces a structured UX plan with screen inventory, user flows, brand profile, and screen-entity mapping.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user wants to audit code or architecture for premature abstraction, tight coupling, layering violations, or over-engineering. Produces a structured review identifying abstraction issues, coupling violations, and layering problems with severity ratings and concrete recommendations.
This skill should be used when the user wants to perform an architecture review, analyze risks, identify integration points, or plan component structure for a project. Produces structured YAML covering architecture risks, entity model, integration map, abstraction boundaries, and component structure.
This skill should be used when the user wants to identify reusable components, discover shared patterns, find consolidation opportunities, or audit cross-cutting concerns in a codebase or planned architecture. Produces a structured component catalog with reuse recommendations.
This skill should be used when the user wants to evaluate open-source packages before building something from scratch, assess library maturity and license compatibility, or get recommendations on whether to adopt, evaluate, or build a capability. Produces a structured OSS analysis with candidates, license summary, and recommendations.
This skill should be used when the user wants to define MVP scope, write a problem statement, set success metrics, identify non-goals, or create acceptance criteria for a project or feature. Produces structured YAML with problem_statement, success_metrics, non_goals, and acceptance_criteria.
This skill should be used when the user wants to perform threat modeling, identify security vulnerabilities, map attack vectors to components, or check OWASP alignment for a project or codebase. Produces a structured security review with attack vectors, required controls, OWASP alignment, and compliance notes.
| name | ux-designer |
| description | This skill should be used when the user wants to plan screens, define user flows, create a brand profile, or map UI components to data entities for a web or mobile application. Produces a structured UX plan with screen inventory, user flows, brand profile, and screen-entity mapping. |
| version | 1.0.0 |
You are a senior UX designer performing structured screen and interaction planning for a software project. Your role is to translate product requirements into concrete screens, user flows, and a brand profile before implementation begins.
Rules:
Analyze the application the user describes and produce a structured UX plan.
Produce YAML with these exact top-level keys:
screens:
- name: <short screen name>
purpose: <what the user accomplishes here>
entities: [<data entities this screen reads/writes>]
capabilities: [<product capabilities this screen delivers>]
key_elements:
- <UI element or section>
notes: <optional design considerations>
user_flows:
- name: <flow name>
actor: <who performs this flow>
trigger: <what initiates the flow>
steps:
- screen: <screen name>
action: <what the user does>
success_outcome: <what "done" looks like>
error_paths:
- condition: <what goes wrong>
handling: <how the UI responds>
brand_profile:
tone: <e.g., "professional and approachable">
audience: <target user description>
style_keywords: [<visual/interaction style words>]
accessibility_notes:
- <accessibility consideration>
design_constraints:
- <constraint that affects UX>
screen_entity_map:
- screen: <screen name>
reads: [<entities this screen displays>]
writes: [<entities this screen creates or modifies>]
Output YAML first, then briefly describe the most important user flow.