design-workflow
Trigger: design workflow, design pipeline, before coding a page, UI process, how we design. Shared team convention: Excalidraw sketch → Penpot design+tokens → code skills, unidirectional.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-26
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- design-workflow
- license
- Apache-2.0
- metadata
- { "author": "gentleman-programming", "version": "1.0" }
- description
- Trigger: design workflow, design pipeline, before coding a page, UI process, how we design. Shared team convention: Excalidraw sketch → Penpot design+tokens → code skills, unidirectional.
03 SKILL.md 正文
Design Workflow — Shared Team Convention
Activation Contract
Use at the START of any UI/page work to establish the agreed pipeline BEFORE producing artifacts: landing pages, dashboards, auth flows, or any frontend surface. This is the TEAM CONVENTION — agents and skills MUST follow it, not improvise a different flow.
Pipeline:
flowchart LR
A[Brief] --> B[Excalidraw<br/>low-fi sketch]
B --> C[Penpot<br/>high-fi design + tokens]
C --> D[Code skills<br/>ui-craft / frontend-design]
D --> E[App code]
Hard Rules
- UNIDIRECTIONAL: Excalidraw → Penpot → code. Never skip backward or run stages as competing sources of truth.
- ONE source of truth per stage. Excalidraw is NOT the design spec; Penpot is NOT the code.
- Excalidraw = low-fidelity ideation only (use the
excalidrawskill). Hand-drawn on purpose. - Penpot = high-fidelity design system + design tokens (CSS variables). External tool.
- Code = generated by ui-craft / frontend-design / design-prototype, consuming Penpot tokens via DESIGN.md or CSS variables (ui-craft already honors an external token source).
- The bridge between stages is HUMAN: confirm the artifact, then pass a brief forward.
- Never duplicate the design in two tools. If it lives in Penpot, consume its tokens — do not redraw from scratch in code.
Decision Gates
| Stage | Tool | Output | Hands off to |
|---|---|---|---|
| Sketch / wireframe / flow / ER | excalidraw skill |
.excalidraw |
Penpot |
| High-fi design + tokens | Penpot | design + token JSON/CSS | code skills |
| Production code | ui-craft / frontend-design / design-prototype | app code | — |
Shortcut: a simple landing may skip Penpot (Excalidraw + code skills); a pure backend diagram may stay in Excalidraw. Decide per brief, but never skip the human handoff.
Execution Steps
- Receive the brief; pick the stages needed.
- Stage 1: if structure/flow is unclear, use the
excalidrawskill to sketch. - Stage 2: convert the agreed sketch into a Penpot design; export design tokens.
- Stage 3: feed tokens + brief to the code skills; they generate the implementation.
- At every handoff, confirm with the user before advancing.
Output Contract
- A clear statement of which stage the current task is in and the next handoff.
- Artifacts placed in the correct tool, never duplicated.
References
skills/excalidraw/SKILL.md— low-fidelity sketch skill.skills/ui-craft/SKILL.md,skills/frontend-design/SKILL.md,skills/design-prototype/SKILL.md— code generation.- Penpot (https://github.com/penpot/penpot) — high-fidelity design + tokens (external, open source).
04 同仓库更多 Skills
zustand-5
Zustand 5 state management patterns. Trigger: When managing React state with Zustand.
zod-4
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
x-bookmark-quote-posts
Workflow para revisar bookmarks de X/Twitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.