UI/UX Pro Max

Follow these steps to deliver high-quality UI/UX output with minimal back-and-forth.

1) Triage

Ask only what you must to avoid wrong work:

• Target platform: web / iOS / Android / desktop
• Stack (if code changes): React/Next/Vue/Svelte, CSS/Tailwind, component library
• Goal and constraints: conversion, speed, brand vibe, accessibility level (WCAG AA?)
• What you have: screenshot, Figma, repo, URL, user journey

If the user says "全部都要" (design + UX + code + design system), treat it as four deliverables and ship in that order.

2) Produce Deliverables (pick what fits)

Always be concrete: name components, states, spacing, typography, and interactions.

• UI concept + layout: Provide a clear visual direction, grid, typography, color system, key screens/sections.
• UX flow: Map the user journey, critical paths, error/empty/loading states, edge cases.
• Design system: Tokens (color/typography/spacing/radius/shadow), component rules, accessibility notes.
• Implementation plan: Exact file-level edits, component breakdown, and acceptance criteria.

3) Use Bundled Assets

This skill bundles data you can cite for inspiration/standards.

• Design intelligence data: Read from skills/ui-ux-pro-max/assets/data/ when you need palettes, patterns, or UI/UX heuristics.
• Upstream reference: If you need more phrasing/examples, consult skills/ui-ux-pro-max/references/upstream-skill-content.md.

4) Optional Script (Design System Generator)

If you need to quickly generate tokens and page-specific overrides, use the bundled script:

python3 skills/ui-ux-pro-max/scripts/design_system.py --help

Prefer running it when the user wants a structured token output (ASCII-friendly).

Output Standards

• Default to ASCII-only tokens/variables unless the project already uses Unicode.
• Include: spacing scale, type scale, 2-3 font pair options, color tokens, component states.
• Always cover: empty/loading/error, keyboard navigation, focus states, contrast.

子代理执行策略

• 默认执行模式：优先使用子代理独立执行；主会话负责接单、补齐必要上下文、控制范围，并在最后整合结果回报给用户。
• 适合交给子代理的任务：预计超过 30 秒的处理、多步骤流水线、多文件/多产物生成、批处理、审计、转写、总结、离线分析。
• 主会话保留职责：只在必要时追问关键缺口、确认边界、挑选最终结果，并把输出改写成面向用户的完成答复。
• 不建议默认交给子代理的情况：一次性极短任务、需要高频来回确认的对话、强依赖当前聊天即时上下文的动作。
• 回报节点：默认只保留“已受理 / 已开始 / 已完成 / 已失败”四类关键节点，避免刷屏。