UX

ux-ui-design

An end-to-end design tool for creating wireframes, flows, and HTML/CSS prototypes.

Install

mkdir -p .claude/skills/ux-ui-design && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10181" && unzip -o skill.zip -d .claude/skills/ux-ui-design && rm skill.zip

Installs to .claude/skills/ux-ui-design

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Design user experiences with wireframing, prototyping, user flows, accessibility, and production-ready HTML prototypes. Use when creating wireframes, building interactive prototypes, designing user flows, implementing accessibility standards, or producing HTML/CSS design deliverables.
285 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Design user flows and information architecture
  • Create wireframes and high-fidelity mockups
  • Build interactive HTML/CSS prototypes
  • Perform accessibility (WCAG) audits
  • Define design systems and token sets

How it works

It follows a structured design process from research and IA to prototyping, enforcing accessibility and design system standards throughout.

Inputs & outputs

You give it
Product requirements or design brief
You get back
Wireframes, prototypes, or accessibility audit reports

When to use ux-ui-design

  • Design a new user flow
  • Create a high-fidelity prototype
  • Perform an accessibility audit
  • Build a production-ready HTML interface

About this skill

UX/UI Design & Prototyping

Purpose: Create user-centered designs, wireframes, prototypes, and production-ready HTML/CSS interfaces.


When to Use This Skill

  • Creating wireframes or high-fidelity mockups
  • Building interactive HTML/CSS prototypes
  • Designing user flows and information architecture
  • Implementing accessibility (WCAG) standards
  • Setting up design systems or component libraries

Prerequisites

  • Basic HTML/CSS knowledge for prototyping
  • Design tool access

Decision Tree

Use this to pick the right UX approach for your task:

Start: What is the deliverable?
|
+- New feature / epic?
| - 1. User Research -> 2. IA -> 3. Wireframes -> 4. User Flows
| -> 5. Hi-Fi Mockups -> 6. HTML Prototype -> 7. Usability Test
|
+- Bug fix / small change?
| - Skip to step 5 (Hi-Fi) or 6 (HTML Prototype)
|
+- Design system update?
| - Jump to Design Systems - update tokens + components
|
+- Accessibility audit?
| - Jump to Accessibility - run checklist + fix
|
- Responsive issue?
 - Jump to Responsive Design - breakpoint check + fix

Table of Contents

  1. User Research & Analysis
  2. Information Architecture
  3. Wireframing
  4. User Flows
  5. High-Fidelity Mockups
  6. Interactive Prototypes
  7. HTML/CSS Prototypes
  8. Design Systems
  9. Accessibility (A11y)
  10. Responsive Design
  11. Usability Testing
  12. Best Practices
  13. Tools & Resources

Core Rules

[PASS] DO

Research & Wireframing:

  • Define Product Posture & Archetype BEFORE sketching any screens
  • Start with lo-fi sketches; iterate on paper first
  • Use real content, never lorem ipsum in final designs
  • Annotate interactions on every wireframe
  • Test with diverse user demographics

Design & Prototyping:

  • Follow the 8px spacing grid
  • Design for ALL states: empty, loading, error, success, partial
  • Build production-ready HTML/CSS prototypes (mandatory)
  • Use semantic HTML5 + ARIA attributes from the start
  • Use CSS custom properties for all design tokens (see prototype-craft asset)
  • Validate HTML & CSS

Collaboration:

  • Document every design decision
  • Share prototypes early and gather developer feedback
  • Version-control design files
  • Hand off with detailed specifications

[FAIL] DON'T

  • Skip user research or design in isolation
  • Leave placeholder content in final deliverables
  • Ignore edge cases and error states
  • Forget mobile/tablet breakpoints
  • Neglect accessibility until the end
  • Hardcode values instead of using design tokens
  • Use large unoptimized images
  • Inline all styles (use external stylesheets)
  • Block rendering with synchronous scripts

Anti-Patterns

  • Skipping user research: Designing based on assumptions -> conduct interviews or surveys with 5+ users before wireframing
  • Lorem ipsum in deliverables: Placeholder text hides content layout problems -> use realistic content from the actual domain
  • Desktop-first design: Retrofitting mobile after desktop -> design mobile breakpoints first, then enhance upward
  • Ignoring error states: Only designing the happy path -> design empty, loading, error, partial, and success states for every screen
  • Pixel-perfect handoff without tokens: Hardcoded colors and sizes -> define a design token system (CSS custom properties) and reference tokens in specs
  • Accessibility as afterthought: Running audits only at the end -> integrate WCAG checks from wireframe stage, not after prototyping
  • Overly complex user flows: 10+ step flows without progress indicators -> limit critical paths to 3-5 steps with clear progress feedback
  • No version control on designs: Overwriting files with no history -> use Git for HTML prototypes and Figma version history for mockups

Tools & Resources

Design & Wireframing

ToolUse CaseLink
FigmaCollaborative designfigma.com
SketchMac designsketch.com
PenpotOpen-source designpenpot.app
BalsamiqQuick wireframesbalsamiq.com
WhimsicalFlowcharts + wireframeswhimsical.com
ExcalidrawHand-drawn diagramsexcalidraw.com

Prototyping

ToolUse CaseLink
CodePenQuick HTML/CSS/JScodepen.io
Tailwind CSSUtility-first CSStailwindcss.com
BootstrapComponent frameworkgetbootstrap.com

Accessibility

ToolUse CaseLink
WAVEAccessibility checkerwave.webaim.org
axe DevToolsBrowser extensiondeque.com/axe
WCAG Quick RefGuidelinesw3.org/WAI

Inspiration

Dribbble - Behance - awwwards


Reference Files

Detailed code blocks and templates are extracted into dedicated reference files:

ReferenceContents
html-prototype-code.mdFull HTML/CSS/JS prototype code (dashboard, modals, forms, tokens)
research-templates.mdPersona template, user journey map template
accessibility-patterns.mdScreen reader markup, keyboard navigation JS, ARIA patterns
responsive-patterns.mdBreakpoint CSS, responsive grid, mobile-first examples
usability-testing-template.mdFull usability test plan, script, and results template

Related Skills:


Version: 2.0.0 - Last Updated: February 10, 2026

Troubleshooting

IssueSolution
Prototype not accessibleRun WAVE or axe-core audit, ensure ARIA labels and keyboard navigation
Inconsistent design across pagesCreate a design token system with shared colors, spacing, typography
User flow too complexReduce steps to 3-5 maximum, add progress indicators

References

When not to use it

  • When skipping user research
  • When designing in isolation
  • When ignoring mobile/tablet breakpoints

Prerequisites

Basic HTML/CSS knowledgeDesign tool access

Limitations

  • Requires design tool access
  • Cannot replace user research with assumptions

How it compares

It mandates production-ready HTML/CSS prototypes and accessibility integration from the wireframe stage, unlike purely visual design workflows.

Compared to similar skills

ux-ui-design side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ux-ui-design (this skill)04moNo flagsIntermediate
frontend-design06moReviewIntermediate
ui-ux-designer414moNo flagsIntermediate
ui41moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jnPiyush

View all by jnPiyush

copilot-studio-agents

jnPiyush

Design Microsoft Copilot Studio agents (formerly Power Virtual Agents) -- topics, trigger phrases, generative answers, knowledge sources, connector and MCP actions, authentication, channels, and agent flows -- so an agent can author the conversational logic that ships as a Bot component inside a Pow

00

verification-before-completion

jnPiyush

Block false completion claims. Force the agent to identify the claim, run the exact verification command, read the actual output, compare against the claim, and only then report. Use whenever an agent is about to say "done", "fixed", "tests pass", "deployed", "loop complete", or close an issue.

00

configuration

jnPiyush

Implement configuration management patterns including environment variables, secrets, feature flags, and validation strategies. Use when setting up app configuration, managing environment-specific settings, implementing feature flags, storing secrets securely, or validating configuration at startup.

00

docx

jnPiyush

Read, write, and transform Microsoft Word .docx files. Use when extracting text or tables from Word documents, generating reports from templates, applying styles, inserting images, building tables, or converting Markdown/HTML to Word.

00

error-handling

jnPiyush

Implement robust error handling with exceptions, retry logic, circuit breakers, and graceful degradation. Use when designing error handling strategies, implementing retry policies, adding circuit breakers, configuring timeouts, or building health check endpoints.

00

mcp-apps-development

jnPiyush

Build MCP Apps (ext-apps) that render interactive UI inside conversational AI clients. Use when creating visual tool outputs, interactive dashboards, form-based tools, or rich media experiences in MCP-compatible hosts like Claude Desktop, VS Code Copilot Chat, or other MCP clients that support the A

00

You might also like

frontend-design

darthlinuxer

Design thinking and decision-making for web UI. Use when designing components,

00

ui-ux-designer

sickn33

Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.

4171

ui

nuxt

Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.

427

userinterface-wiki

raphaelsalaja

UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.

00

impeccable

rawkode-academy

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding,

00

visual-design-foundations

wshobson

Apply typography, color theory, spacing systems, and iconography principles to create cohesive visual designs. Use when establishing design tokens, building style guides, or improving visual hierarchy and consistency.

547

Search skills

Search the agent skills registry