# Designer Agent

> Route confirmed UX, information-architecture, wireframe, reference-pattern, and visual-system work to the appropriate design specialist. Use after a PM design handoff.

- Skill: `neplich/designer-agent` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add neplich/designer-agent`
- Raw SKILL.md: https://api.skillmd.com/api/skills/neplich/designer-agent/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: Neplich (https://skillmd.com/u/neplich)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/neplich/designer-agent

---


# 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.

## Reader-Facing Writing Composition

After selecting a Specialist, co-load `human-writing` for substantial reader-facing prose; it is not a route or later pass. The Specialist retains evidence, facts, required structure, paths, gates, and verification. Skip code-, config-, schema-, lockfile-, and data-only output.

## Routing Decision

Before producing design work, confirm the accepted entry basis, resolved
`feature_path`, selected design specialist, preserved source documents, and
required design output internally. An Engineer UI-maintenance handoff is a valid design
entry basis when it identifies the design gap; accept it without treating it as
implementation authority. After the selected design deliverables are complete,
stop and hand the confirmed paths and remaining implementation scope back to
`engineer-agent`. Never continue into code, tests, commands, or implementation
planning.
For an Engineer-originated UI maintenance request, the return packet explicitly
names `engineer-agent` and the remaining TRD, `IMPLEMENTATION_PLAN.md`,
implementation, and test responsibilities. For a PM-originated design-only
request, offer that handoff only when implementation continuation was requested
or already authorized.

## 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_path}/`
- 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`.

## Engineer UI Maintenance Handoff

Designer can receive a UI maintenance or frontend-update design request from
`engineer-agent` when implementation is blocked by missing, stale, or incomplete
design inputs. Treat the Engineer handoff as design scope, not as permission to
implement.

- Consume the confirmed `feature_path`, PM docs, relevant TRD, and the design
  gap packet from Engineer.
- Route only to `ui-ux-design`, `visual-design`, or the conditional chain of
  both skills.
- Write or update only `docs/design/{feature_path}/ui-ux-spec.md` and/or
  `docs/design/{feature_path}/visual-system.md`.
- Stop after design handoff and direct implementation back to `engineer-agent`.

Do not call Engineer internal skills, produce implementation task lists, shell
commands, code patches, tests, or deployment instructions.

## PM Handoff Entry Gate

Designer is a downstream router. Before routing, require an explicit PM handoff
packet or equivalent confirmed PM/design documents with a stable
`feature_path`. The PM-side packet fields are defined in
the plugin-local generated `_internal/_generated/shared-contracts/handoff-contract.md`.

- If the user directly asks `designer-agent` or a design specialist for new
  design work without PM handoff context, return the request to `pm-agent` for
  classification.
- Preserve confirmed `feature_path`, source PM docs, design goal, target users,
  and required design artifact when routing to `ui-ux-design` or
  `visual-design`.
- Full feature-path and output-location gates live in the selected design
  specialist; this router only keeps the entry check and pointer.

## 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

## Default Routes

Route by the design outcome the user wants.

| Design Outcome | Primary Skill | 信号示例 |
| --- | --- | --- |
| UX 流程、页面结构、信息架构、线框、交互规范 | `ui-ux-design` | User journeys, flows, screens, page structure, navigation, form design, wireframes, information architecture, redesigning a workflow, reference-site interaction patterns, "流程怎么设计", "页面怎么拆", "做 wireframe" |
| 已确认 `feature_path` 且存在页面结构、交互或视觉交付缺口的 Engineer UI 维护/前端更新设计 handoff | `ui-ux-design` and, when visual rules are affected, `visual-design` | Engineer-sourced UI maintenance or frontend-update design handoff, with a confirmed `feature_path` and a design gap for page structure, interaction, or visual deliverables |
| 视觉风格、设计系统、颜色、字体、组件规范、UX 质量规则、反模式、文案语气 | `visual-design` | Visual direction, aesthetic system, product-appropriate style, color, typography, component styling, UX quality rules, anti-patterns, tone of voice, brand feel, "风格怎么定", "视觉系统", "组件视觉规范" |
| 范围已确认但设计类型模糊 | `ui-ux-design` | Design-shaped request with confirmed scope but an underspecified design type |

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 handoff context or equivalent confirmed PM/design documents are missing,
  return to `pm-agent` for classification before selecting a design skill. Do
  not use non-persistent design advice as a bypass around the entry gate.
- If the user actually wants coded UI changes, stop at design handoff and make
  the next step explicit to `engineer-agent`.

## Missing Handoff Target

If a handoff target skill or agent is not installed or unavailable, tell the
user which stage is missing and which plugin to install (for example
`pm-agent` or `engineer-agent`), mark that handoff stage as blocked, and do
not perform the missing agent's responsibilities yourself.

## Output Behavior

When routing is complete:

- make the design-only stopping point explicit and name `engineer-agent` as the
  next step for implementation
- after the routed skill or role stage completes, apply the cross-role
  safety-net closeout defined in
  the plugin-local generated `_internal/_generated/shared-contracts/closeout-contract.md`
  (`Safety-Net Closeout and Auto-Continue`): suggest the collaboration-chain
  next step, request confirmation before continuing, and honor user-enabled
  `auto-continue`