菜单
Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX"
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
| name | draft-patterns |
| description | Use when asked about UX patterns, interaction best practices, form design, navigation patterns, or loading states. Examples: "best practice for form validation", "navigation pattern for dashboard", "loading state UX" |
| allowed-tools | Read, Bash, Glob, Grep |
| version | 0.6.6 |
| author | tonone-ai <hello@tonone.ai> |
| license | MIT |
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
User asks about interaction patterns, best practices, form design, navigation, or loading/empty states.
python3 -m draft_agent.uiux search --domain ux --query "{pattern_category}" --limit 5
┌─ UX Patterns — {pattern_category} ──────────────────────────────────────────┐
│ Category │ Issue │ Do │ Don't │ Severity │
├─────────────┼────────────────────┼─────────────────────┼──────────┼──────────┤
│ {category} │ {issue} │ {do} │ {dont} │ Critical │
│ {category} │ {issue} │ {do} │ {dont} │ High │
│ {category} │ {issue} │ {do} │ {dont} │ Medium │
└─────────────┴────────────────────┴─────────────────────┴──────────┴──────────┘
Code example ({do_example_label}):
{code_block}
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.