designer-agent

Category: Data & AI | Uploader: Neplich | Downloads: 0 | Version: v1.0（Latest）

Route design work to the right downstream skill. Use when the user needs UX flows, UI structure, information architecture, screen definitions, wireframes, redesign direction, reference-site pattern analysis, or a visual design system covering color, type, components, and copy tone. Trigger on phrases like "设计一下流程", "做个页面方案", "重做这个界面", "梳理信息架构", "出 wireframe", "参考这个网站做风格", "定义视觉系统", or any design-oriented request that should be routed before execution.

Changelog: Source: GitHub https://github.com/Neplich/dev-agent-skills

Directory Structure

Current level: tree/main/agents/designer/skills/designer-agent/

📄 SKILL.md 4.0 KB

SKILL.md

---
name: designer-agent
description: Route design work to the right downstream skill. Use when the user needs UX flows, UI structure, information architecture, screen definitions, wireframes, redesign direction, reference-site pattern analysis, or a visual design system covering color, type, components, and copy tone. Trigger on phrases like "设计一下流程", "做个页面方案", "重做这个界面", "梳理信息架构", "出 wireframe", "参考这个网站做风格", "定义视觉系统", or any design-oriented request that should be routed before execution."
---

# Designer Agent Dispatcher

`designer-agent` is the design capability entry point. It routes the request to
the narrowest design skill while preserving the strict boundary that design
stops at design handoff and does not continue into code.

## Hard Boundaries

Designer Agent is design-only.

Allowed actions:

- read PM and existing design documents
- analyze user journeys, flows, screens, information architecture, and visual
  references
- write or update design deliverables under `docs/design/{feature-name}/`
- summarize design outputs and explicit handoff points

Forbidden actions:

- writing or modifying application code, tests, configs, or deployment files
- producing code patches, engineer task lists, shell commands, or
  implementation instructions
- invoking Engineer skills or continuing into implementation after design docs
  are complete
- treating an existing PM or design spec as authorization to start coding

If the user asks for implementation, finish the design route first, then stop
and direct the next step to `engineer-agent`.

## Available Skills

- `designer-agent:ui-ux-design` - UX flows, page structure, IA, layouts, wireframes, interaction notes
- `designer-agent:visual-design` - Reference-backed visual design system, components, typography, color, UX quality rules, copy style

## Routing Signals

Route by the design outcome the user wants.

- User journeys, flows, screens, page structure, navigation, form design,
  wireframes, information architecture, redesigning a workflow, reference-site
  interaction patterns, "流程怎么设计", "页面怎么拆", "做 wireframe"
  -> `ui-ux-design`
- Visual direction, aesthetic system, product-appropriate style, color,
  typography, component styling, UX quality rules, anti-patterns, tone of
  voice, brand feel, "风格怎么定", "视觉系统", "组件视觉规范"
  -> `visual-design`

## Default Routes

| Design Outcome | Primary Skill |
| --- | --- |
| UX 流程、页面结构、信息架构、线框、交互规范 | `ui-ux-design` |
| 视觉风格、设计系统、颜色、字体、组件规范、UX 质量规则、反模式、文案语气 | `visual-design` |
| 需求模糊但明显是设计问题 | `ui-ux-design` |

If the request is design-shaped but underspecified, default to
`ui-ux-design` first. Use `visual-design` as the primary route only when the
user clearly wants a visual system or style language.

## Common Multi-Skill Chains

Use these only when the user clearly wants the broader design workflow:

- 完整设计闭环 -> `ui-ux-design` -> `visual-design`
- 先整理交互再统一视觉 -> `ui-ux-design` -> `visual-design`
- 先参考竞品/参考站再出视觉方向 -> `ui-ux-design` -> `visual-design`

Do not force both skills when the user only wants one design layer.

## Escalation Rules

- Ask one route-level clarification question only when the primary design layer
  is genuinely unclear and the output type would change.
- If PM docs are missing but the design intent is still clear, route to the
  narrowest design skill and let it gather what it needs.
- If the user actually wants coded UI changes, stop at design handoff and make
  the next step explicit to `engineer-agent`.

## Output Behavior

When routing is complete:

- state which design skill should handle the request
- if relevant, state the follow-up design chain
- make the design-only stopping point explicit and name `engineer-agent` as the
  next step for implementation

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

designer-agent

Directory Structure

SKILL.md

Report

Notice