ui-design
UI design workflow that takes a [UI] Jira story and optional UX handoff artifact, produces a component decomposition with hook design, state management, route structure, and data flow mapping, reviews the API surface for gaps, and syncs [DEV] stories for backend work to Jira. Activated by commands: /ingest, /plan, /review-api, /revise, /publish, /respond, /sync.
84%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
UI Design Workflow Orchestrator
Quick Start
- If the user invoked a specific command, read
commands/{command}.mdand follow it. Phases:ingest,plan,review-api,revise,publish,respond,sync. - Otherwise, read
skills/controller.mdto load the workflow controller:- If the user provided a Jira issue key or URL, execute the
/ingestphase - Otherwise, execute the first phase the user requests
- If the user provided a Jira issue key or URL, execute the
If a step fails or produces unexpected output (e.g., Jira MCP errors, network failures, codebase exploration failures), stop and report the error to the user. Do not advance to the next phase. Offer to retry the failed step or escalate.
For principles, hard limits, safety, quality, and escalation rules, see guidelines.md.
- Repository
flightctl/ai-workflows
- Revision
b369da0
- Last updated
- First committed
Also appears in
since Oct 14, 2026
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.