Agent skill

Software UI/UX Design Skill: Audit and Design with a Craft Bar

The software-ui-ux-design skill has an AI coding agent audit or design interfaces across six modes, with state coverage, computed contrast and a ten-row Craft Bar before handoff.

Install
/plugin marketplace add vasilyu1983/AI-Agents-public
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the software-ui-ux-design skill?

The software-ui-ux-design skill is a SKILL.md in the vasilyu1983 AI-Agents-public repository that designs and audits interfaces, flows and design systems for an AI coding agent. It works in six modes, covers loading, empty, error and offline states, reviews a ten-row Craft Bar, and ends with acceptance criteria.

The software-ui-ux-design skill will not call a screen finished on accessibility alone. It reviews work against ten Craft Bar rows, and if three or more fail, the skill treats the screen as debt regardless of what metrics say.

The skill sits at skills/universal/software-ui-ux-design in the vasilyu1983 AI-Agents-public repository, which packages 140 skills for coding agents. This one owns design direction, interaction behavior, state coverage and implementation-ready handoff, and leaves user research and code fixes to other skills.

Six modes

ModeUse whenRequired output
Audit existing UIUsability, accessibility, consistency or conversion issuesFindings plus acceptance criteria
Design new UIA flow or screen must be shaped from scratchFlow, states, components, handoff spec
Design-system decisionA team must choose primitives or token structureRecommendation with tradeoffs
AI frontend briefAn AI will generate the UIVisual thesis, interaction thesis, verification plan
AI UX reviewThe product includes chat, agents or automationTransparency, control and failure handling guidance
Style, palette and font selectionA new surface needs a concrete directionDesign system generated from the offline database

For that last mode the agent runs python3 scripts/search.py with a product, industry and tone, adding --design-system. The reference describes an offline searchable database of more than 80 styles, more than 190 palettes, font pairings and UX guidelines.

The Craft Bar

Consumer-grade product work is judged on these rows, not just task completion, because a screen that meets WCAG and still feels lifeless is not done.

DimensionPassFail
Time to first valueUnder 60 seconds for the primary userA multi-step setup wizard
Empty stateModels the populated state with one verb CTANo items yet plus a grey illustration
Loading stateA skeleton matching the populated layoutA centered spinner
Error recoveryNames the cause and offers a specific next stepSomething went wrong
MotionFunctional, showing origin to destination and hierarchyDecorative bounces on every state change
Recovery without restartBack, undo and edit-without-redo paths existAre you sure gating every action

Four more rows cover microcopy, touch feedback, optical alignment and first-run delight. For agent surfaces that act over multiple steps, four extra rows score steerability, action reversibility, cost visibility and memory legibility.

Checks before handoff

  • Cover all five state types: loading, empty, error, offline or degraded, and happy path.
  • Keep one primary action per view, with secondary actions visually subordinate.
  • Compute every contrast ratio with scripts/contrast_check.py instead of estimating it, and measure it against the surface the text actually renders on.
  • Give any live-updating region an aria-live politeness level and a batching rule.
  • Provide a prefers-reduced-motion fallback for scroll-driven or CSS animation.
  • Verify AI-generated UI in a browser with real content, not placeholder text.

Platform defaults differ: web focuses on semantic structure, focus behavior, reflow and target size, iOS on system navigation, Dynamic Type and safe areas, and Android on Material 3 patterns, edge-to-edge and predictive back.

Who the software-ui-ux-design skill is for

Best for

  • Reviewing or shaping flows where loading, empty and error states decide trust.
  • Choosing design-system primitives and token structure. For related patterns, see design-system-patterns.
  • Writing a strong brief before an AI generates frontend work, with a visual thesis and an interaction thesis.
  • Reviewing chat, agent or automation UX for transparency, control and failure handling.
  • Accessibility-minded design specs. For a focused review, see accessibility-review.

Not for

  • User research and study design, which the skill routes to a separate UX research skill.
  • Code-level accessibility fixes, accessibility test automation and frontend implementation, which it routes elsewhere.
  • Product strategy and roadmaps, which it hands to a product management skill.

Use it with UiChemy

This skill produces specs, flows and acceptance criteria, not WordPress pages. It does suit the step before a build: audit interfaces, flows and component systems, cover empty, loading and error states, and settle hierarchy before anything is converted.

Then convert the approved frames with UiChemy Figma to WordPress. If you build with UiChemy Composer instead, use the skill's brief structure, a visual thesis, an interaction thesis and real content, in your prompt. Click Get Started on uichemy.com.