UI/UX pod that starts from whatever already exists. Screens in Figma → it ships the Figma MCP, extracts the spec and variables, builds to the design and gates on fidelity, with the jury offered rather than imposed. A brand design system in Figma → its variables and components become the project's tokens and vocabulary (workspace-wide), and the pod designs the screens within them, jury still gating. Neither → UX-narrative writer, Awwwards inspiration researcher, design-system owner, motion specialist, and a strict unbiased jury that renders the UI and gates on ≥9/10. New or existing projects, page or whole-app scope, honors brand references (logo/colors/fonts). Bundles the Figma and Playwright MCP servers it needs, so a backend-only workspace installs neither. Enabled by default; it only activates on UI items, so backend-only projects are unaffected.
0 on GitHubby Sourabh Sudheerv0.9.2MITupdated 15 days agodevelopment
/
Plugin aidlc-ux from marketplace aidlc in Sourabh1095/AIDLC. Commands read from the repo's manifest — 13 days ago.
This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (8)
design-jury
The Awwwards-style scoring rubric, anti-bias rules and the shared render-and-evidence protocol. Load when acting as the jury, rendering a built UI to check it, or reviewing a jury report.
design-research
How to mine award-winning work for techniques that serve a narrative, with cited sources. Load when producing or reviewing design/inspiration.md.
design-system
How to build a tokenized design system (color, type, spacing, radius, elevation) as the single source of truth. Load when defining or reviewing design tokens and design/design-system.md.
design
Run the UI/UX design pod on a page, a screen or the whole app, new or existing. Builds to Figma screens when they exist (fidelity gate); otherwise designs and iterates until the jury scores at least the threshold. Invoked as /aidlc-ux:design and by /aidlc:run for UI items.
figma-handoff
Working from an existing Figma file — reading it via MCP, extracting the spec, what fidelity means and how it is scored. Load when extracting from Figma, implementing from it, or reviewing a Figma spec or fidelity report.
figma
Link a project's Figma files (screens or a design system), map frames to routes, extract the spec, and re-sync to catch drift. Invoked as /aidlc-ux:figma; the design pod uses the same extraction.
motion
Motion and interaction design (animation, scroll effects, transitions, WebGL) that serves meaning within a performance and accessibility budget. Load when specifying, building or reviewing motion.
ux-narrative
How to write the UX narrative (vision, tone, journey, signature moment) that anchors design decisions. Load when writing or reviewing design/narrative.md.
Subagents (7)
aidlc-design-system
AIDLC design-system owner — turns the narrative and inspiration into tokens in code that every component consumes. Dispatched by /aidlc-ux:design, including jury fix rounds.
aidlc-fidelity
AIDLC fidelity checker for Figma-sourced UI — renders the built screen and compares it with the Figma reference, classifying each difference. Dispatched by /aidlc-ux:design.
aidlc-figma
AIDLC Figma handoff — reads a Figma file through MCP into a screen spec or design-system extraction, and diffs re-extractions for drift. Dispatched by /aidlc-ux:figma and the design pod; never edits product code.
aidlc-motion
AIDLC motion specialist — animation, micro-interactions, scroll effects and transitions within a performance and accessibility budget. Dispatched by /aidlc-ux:design, including jury fix rounds.
aidlc-ux-jury
AIDLC design jury — renders the built UI and scores it out of 10 with visual evidence, isolated from the makers. Gates /aidlc-ux:design at each jury round.
aidlc-ux-researcher
AIDLC design-inspiration researcher — visual and interaction references with sources, not technical research. Dispatched by /aidlc-ux:design in the research phase.
aidlc-ux-writer
AIDLC UX narrative writer — turns a work item into the experience story every design decision traces back to. Dispatched by /aidlc-ux:design in the narrative phase.
AIDLC (AI Development Life Cycle) orchestrator: reads work items (Jira/ADO/markdown), routes them through requirements, planning, implementation, review, QA and PR — across one repo or a multi-repo workspace, with or without a git remote, end to end. Stack-agnostic by design; language and framework expertise comes from stack packs.
The Azure DevOps MCP server for AIDLC's ADO adapter. Optional — the adapter's `az boards`/`az rest` tier covers every operation and is what headless runs already use, so ADO works without this. Install it for the richer interactive tier; needs ADO_MCP_ORG in the launching shell.
The Atlassian MCP server for AIDLC's Jira adapter. Required when workItems.source is "jira" — that adapter has no CLI fallback. Install only on Jira projects; core ships no tracker server, so a markdown or ADO workspace starts neither.
A mod (Claude Code 2.1.287+) that shows AIDLC beside the chat: a line above the prompt with the runs in flight and anything waiting on you, a board pane for runs and the sprint, /aidlc-board with no model turn, a desktop notification when a sprint run needs you, the module you're changing and what uses it, this session's files and checks, each epic as a tree of its stories, tasks and bugs, and what each work item cost by phase (feeds /aidlc:insights). It draws what core's scripts report, calls no model and gates nothing; it writes only its git-ignored cost ledger and board copy. Optional: AIDLC works the same without it, which matters where an organization allows only its own mods.
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.