| name | zl-ui-phase |
| description | Zhulong native UI phase workflow for Claude Code with conditional Taste design routing. |
Zhulong UI Phase
Use this when the user invokes /zl-ui-phase.
- Run
{{ZL_CLI}} workflow run ui-phase --target . "$ARGUMENTS". For an
explicit user override, pass --design-strategy <mode> and/or
--taste <enabled|disabled>.
- Read the generated context packet and handoff under
.planning/context/.
- Follow
core/workflows/ui-phase.md.
- Read
{{ZL_KIT_ROOT}}/core/design/taste-adapter.md, the project and
dependency manifests, design evidence, tokens, components, and screens.
Verify the generated preserve, evolve, create, or system decision
against that evidence; do not replace it silently.
- Complete the generated
Frontend Design Decision before implementation. In preserve,
do not introduce new visual systems or UI/motion dependencies without
approval. Taste is bundled; do not request a separate Taste installation.
- Identify UI scope, states, data contracts, permissions, validation,
accessibility, and verification needs.
- Use Graphify/code-map context before risky UI edits.
- Suggest only
/zl-* commands.
GSD is reference design only; do not route the user to /gsd-*.