UI Design entry — ui-design-use

Invocation identity

The installed plugin ID is ui-design; this skill name is ui-design-use. When the user asks to use "UI Design" or the ui-design plugin, resolve the actually available ui-design-use entry from the host skill inventory. Never submit ui-design as a skill name. Use the host-reported qualified name when required; do not guess a namespace.

When to use this skill

Design frontend experiences using the host model, local editable artifacts and optional available image generation. The package does not require Stitch, MCP, an API key or an image backend for ordinary design work.

How to use this skill

1. Locate the user's project, current source/changes, design contracts, approved baseline and requested output. Keep all existing product, navigation, page and task IDs. Do not silently choose a new framework or overwrite a baseline.
2. Route by outcome: specification → ui-design-spec spec mode with ui-design-feature/ui-design-nav; theme → ui-design-theme; editable UI → ui-design-visual; actual preview → ui-design-preview; candidate bitmap or raster asset → ui-design-to-image; comparison → ui-design-review. A screenshot-only input cannot prove interaction.
3. Initial, inherited and correction work uses ui-design-continuity preflight. A scoped correction preserves navigation, theme and frozen regions. Missing approved reference blocks inheritance, not all independent design work.
4. Use existing project contracts and component conventions. Default logical viewports are Mobile 390×884, Tablet 768×1024, Desktop 1280×1024; deliver requested devices, not automatically every device. Images use actual backend-supported raster dimensions and disclose approximation. Exact screenshots and text require actual frontend rendering.
5. For a one-shot request, run the bounded specialist directly. For resumable multi-step work, use the existing ui-design-harness run discovery/profiles and dispatch contracts. Resolve the actually available ui-design-harness runtime and supply an absolute project --store; no parallel ledger or implicit agent spawning. A plugin wrapper is optional and must actually exist before use.
6. Image generation is optional and only for explicit image/asset production. Native imagegen is the Codex default if available; baoyu-image-gen is an optional explicitly selected, actually installed backend. Read its current settings and instructions. No copied system skill, no silent setup, no paid fallback or provider switch without the user's chosen route. Missing tools yield a labeled prompt/brief, not an imaginary image.
7. Inspect actual artifacts and review contract/continuity consistency. Report generated, inspected, approved and runtime-verified separately. Approval follows the current project/Harness rules and actual user scope; never invent a receipt from tool success.

Entry examples