design-brief
Turn a product or visual request into a concrete interface brief, content hierarchy, user journey, and acceptance checklist before implementing a Design Studio artifact.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 827
- Forks
- 573
01 前言 Front Matter
- name
- design-brief
- description
- Turn a product or visual request into a concrete interface brief, content hierarchy, user journey, and acceptance checklist before implementing a Design Studio artifact.
03 SKILL.md 正文
Design brief
Translate the request into an implementation brief without asking for approval unless a genuinely blocking choice is missing.
- Identify the primary user, their immediate goal, and the single most important action on the screen.
- Extract required content and states: default, empty, loading, error, success, disabled, and destructive confirmation where relevant.
- Choose a clear page hierarchy. Each region must earn its space; avoid a dashboard grid when a focused flow would work better.
- Record constraints from the user or existing artifact. Preserve established brand language and useful structure during revisions.
- Define observable acceptance checks for layout, interaction, responsiveness, accessibility, and delivery.
Prefer specific product copy over placeholder prose. Do not invent metrics, customer quotes, legal claims, or functionality the brief did not request.
04 同仓库更多 Skills
whoami
Show current Xyne Claw auth identity.
sessions
List Xyne Claw sessions.
run
Run a Xyne Claw agent.
login
Log the user into Xyne Claw.
agents
List available Xyne Claw agents.
explanation-document
Structure a codebase/schema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.