home / skills / z980944038-dev / openclawwdl / ui-ux-pro-max-0.1.0

ui-ux-pro-max-0.1.0 skill

/skills/ui-ux-pro-max-0.1.0

This skill delivers polished UI/UX guidance and concrete code-ready outputs for layouts, tokens, and accessibility across web stacks.

npx playbooks add skill z980944038-dev/openclawwdl --skill ui-ux-pro-max-0.1.0

Review the files below or copy the command above to add this skill to your agents.

Files (56)
SKILL.md
2.6 KB
---
name: ui-ux-pro-max
description: UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.
---

Follow these steps to deliver high-quality UI/UX output with minimal back-and-forth.

## 1) Triage
Ask only what you must to avoid wrong work:
- Target platform: web / iOS / Android / desktop
- Stack (if code changes): React/Next/Vue/Svelte, CSS/Tailwind, component library
- Goal and constraints: conversion, speed, brand vibe, accessibility level (WCAG AA?)
- What you have: screenshot, Figma, repo, URL, user journey

If the user says "全部都要" (design + UX + code + design system), treat it as four deliverables and ship in that order.

## 2) Produce Deliverables (pick what fits)
Always be concrete: name components, states, spacing, typography, and interactions.

- **UI concept + layout**: Provide a clear visual direction, grid, typography, color system, key screens/sections.
- **UX flow**: Map the user journey, critical paths, error/empty/loading states, edge cases.
- **Design system**: Tokens (color/typography/spacing/radius/shadow), component rules, accessibility notes.
- **Implementation plan**: Exact file-level edits, component breakdown, and acceptance criteria.

## 3) Use Bundled Assets
This skill bundles data you can cite for inspiration/standards.

- **Design intelligence data**: Read from `skills/ui-ux-pro-max/assets/data/` when you need palettes, patterns, or UI/UX heuristics.
- **Upstream reference**: If you need more phrasing/examples, consult `skills/ui-ux-pro-max/references/upstream-skill-content.md`.

## 4) Optional Script (Design System Generator)
If you need to quickly generate tokens and page-specific overrides, use the bundled script:

```bash
python3 skills/ui-ux-pro-max/scripts/design_system.py --help
```

Prefer running it when the user wants a structured token output (ASCII-friendly).

## Output Standards
- Default to ASCII-only tokens/variables unless the project already uses Unicode.
- Include: spacing scale, type scale, 2-3 font pair options, color tokens, component states.
- Always cover: empty/loading/error, keyboard navigation, focus states, contrast.

Overview

This skill provides UI/UX design intelligence and hands-on implementation guidance for building polished interfaces. It covers layout concepts, interaction flows, design-system tokens, component specs, accessibility checks, and turning UX recommendations into concrete frontend code. Use it to generate, critique, or refine interfaces across web and native stacks.

How this skill works

I triage minimal but essential constraints (platform, stack, goals, artifacts) then produce targeted deliverables: UI concepts, UX flows, design-system tokens, and implementation plans. Deliverables are concrete: named components, spacing/type scales, color tokens, states, and file-level edit suggestions. Accessibility, keyboard navigation, focus states, and empty/loading/error handling are included by default.

When to use it

  • Starting a new product UI or redesign
  • You need a component-based design system and tokens
  • Improving conversion, accessibility, or usability of an existing interface
  • Converting UX recommendations into code (React/Next/Vue/Svelte/Tailwind)
  • Creating specs for developers and QA to implement and test

Best practices

  • Triage first: collect platform, stack, goals, and a single artifact (screenshot, URL, or Figma)
  • Be explicit: name components, states, spacing, and acceptance criteria
  • Default to accessible choices: WCAG AA contrast, visible focus, keyboard paths
  • Provide ASCII-friendly tokens and a spacing/type scale for easy handoff
  • Ship in stages when asked for multiple outputs: design, UX, code, then design system

Example use cases

  • Generate a responsive dashboard layout with typography, grid, and component specs
  • Audit an existing checkout flow and produce prioritized UX fixes and microcopy
  • Create design-system tokens (colors, spacing, type scale) and component rules for a React + Tailwind project
  • Convert a Figma screen into a file-level implementation plan and acceptance criteria
  • Improve accessibility: add keyboard navigation, focus styles, and error states for forms

FAQ

What do you need to start?

Platform (web/iOS/Android/desktop), tech stack (React/Next/Vue/Svelte, CSS/Tailwind), primary goal, and one artifact (screenshot, URL, or Figma).

Will you produce code?

Yes. I can provide concrete code suggestions, component breakdowns, and exact file edits for supported stacks, plus acceptance criteria for QA.