tool-ui-ux-pro-max
Tool: UI/UX Pro Max (Searchable Design Intelligence)
This is a lookup tool, not a page generator.
Use it to quickly retrieve concrete inputs (palette tokens, typography pairings, UX constraints, stack-specific implementation notes) that can be synthesized into:
design-system.md- a UI refactor plan / acceptance criteria
- review checklists for “looks good but feels broken” issues
Prerequisites
Ensure Python is available:
python3 --version || python --version
Core command
Domain search:
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "<query>" --domain <domain> [-n <max_results>]
Stack search:
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "<query>" --stack <stack> [-n <max_results>]
Available stacks:
html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter
Recommended workflow
When asked to design / improve UI, do this:
- Identify these inputs:
- Product type: SaaS / e-commerce / content / tool / dashboard / landing
- Tone keywords: minimal / premium / playful / warm / corporate / technical / bold
- Industry: healthcare / fintech / education / consumer / …
- Stack: React / Next.js / … (default to
html-tailwindif unspecified)
- Search domains (pick 1–3 results per domain, then synthesize):
product— product type → style directionstyle— style details (color/shape/motion/complexity)typography— heading/body pairing (includes Google Fonts + CSS import)color— palette tokens (primary/secondary/CTA/background/text/border)landing— landing structure (section order + CTA placement)chart— chart recommendations (dashboards)ux— UX + a11y rules and anti-patterns
- Search by stack to ground decisions in implementation constraints:
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "responsive layout" --stack nextjs
Domain reference
| Domain | Use for | Example keywords |
|---|---|---|
product |
Style direction by product type | saas, ecommerce, portfolio, healthcare |
style |
UI style concepts & implementation hints | minimalism, brutalism, glassmorphism |
typography |
Font pairings + import instructions | elegant, playful, professional |
color |
Palette tokens (Hex) | saas, ecommerce, fintech |
landing |
Landing structure & CTA strategy | hero, testimonial, pricing |
chart |
Chart type selection | trend, comparison, funnel |
ux |
UX/a11y rules & anti-patterns | accessibility, animation, navigation |
prompt |
Prompt / technical keywords | (style name) |
Example (beauty / wellness landing)
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --domain product
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "elegant minimal soft" --domain style
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "elegant luxury" --domain typography
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "beauty spa wellness" --domain color
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "hero-centric social-proof" --domain landing
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "accessibility" --domain ux
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "animation" --domain ux
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind
Then: turn palette + typography + motion constraints + component rules into design-system.md, and convert the checklist below into acceptance criteria.
Common professional UI rules (quick scan)
Icons & visuals
| Rule | Do | Don’t |
|---|---|---|
| No emoji icons | Use a consistent SVG icon set (Heroicons/Lucide/Simple Icons) | Mix emoji/icons randomly |
| Stable hover states | Use color/opacity/shadow transitions | Use transforms that cause layout shift |
| Correct brand logos | Use official SVG sources | Guess logos or use inconsistent variants |
| Consistent sizing | Normalize icon sizing (e.g., 24×24) | Mix different viewBox/sizes |
Interaction
| Rule | Do | Don’t |
|---|---|---|
| Pointer cursor | Add cursor-pointer to clickable surfaces |
Leave clickable surfaces without affordance |
| Clear feedback | Change border/shadow/color on hover | Make hover states indistinguishable |
| Reasonable transitions | 150–300ms, consistent | Instant changes or sluggish >500ms |
Layout
| Rule | Do | Don’t |
|---|---|---|
| Spacing from edges | Leave room for floating navs | Stick UI to viewport edges |
| Avoid hidden content | Account for fixed headers | Let content sit behind fixed bars |
| Consistent containers | Keep one container width system | Use multiple container widths randomly |
Pre-delivery checklist (use as acceptance criteria)
Visual quality
- No emoji used as UI icons
- Icons are from a consistent icon set
- Brand logos are correct (not guessed)
- Hover states do not cause layout shift
- Color usage follows a token system (avoid scattered raw hex values)
Interaction
- All clickable surfaces have
cursor-pointer - Hover/focus states provide clear feedback
- Transitions are consistent (150–300ms)
- Keyboard focus is visible
Layout & responsive
- Works at 320px / 768px / 1024px / 1440px
- No horizontal scroll on mobile
- Fixed elements do not cover content
Accessibility (a11y)
- Images have alt text
- Form inputs have labels
- Color is not the only indicator
- Respects
prefers-reduced-motion
More from heyvhuang/ship-faster
mcp-supabase
Execute database operations via Supabase MCP (query/write/migration/logs/type generation). Triggers: query/statistics/export/insert/update/delete/fix/backfill/migrate/logs/alerts/type generation. Does not trigger for: pure architecture discussion or code planning. Write operations require confirmation; UPDATE/DELETE without WHERE is refused.
76tool-openclaw
Help users install, configure, and operate OpenClaw (gateway, channels, nodes, plugins). Use when answering OpenClaw setup/debug questions; use the local docs snapshot bundled with this skill as the source of truth. Triggers: openclaw, clawdbot, clawd, clawdhub, gateway, onboard, channels login, whatsapp, telegram, discord, mattermost, pairing, nodes, sandboxing, tailscale.
62review-doc-consistency
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
53tool-design-style-selector
Use when you need to define or converge a project's visual direction. Scan project documentation to identify intent, then produce a design-system.md (either preserve existing style or pick from 30 presets). Triggers: design system, design spec, UI style, visual style, design tokens, color palette, typography, layout. Flow: scan → intent → (gate) preserve vs preset → deploy design-system.md after confirmation → (default) implement UI/UX per design-system.md (plan first, then execute).
52tool-schema-markup
When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see review-seo-audit.
51review-react-best-practices
Review or refactor React / Next.js code for performance and reliability using a prioritized rule library (waterfalls, bundle size, server/client data fetching, re-renders, rendering). Use when writing React components, Next.js pages (App Router), optimizing bundle size, improving performance, or doing a React/Next.js performance review.
51