tpn-labs/claudeskills

ui-ux-pro-max

UI/UX design intelligence for web and mobile.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/tpn-labs/claudeskills --skill ui-ux-pro-max

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

UI/UX Pro Max — Design Intelligence

A searchable design knowledge base plus a small Python query tool. It turns a vague "make this look good" into concrete, defensible decisions: a matched visual style, an accessible color palette, a font pairing, a landing/dashboard structure, the right chart for the data, and the platform-correct UX rules — with anti-patterns called out — across 17 web and mobile stacks.

At TPN Labs we build across web, mobile, and cloud for many industries, so this skill is stack-agnostic: always pass the stack the current project actually uses.

Adapted from the open-source, MIT-licensed `ui-ux-pro-max` skill (© Next Level Builder). See references/ for the full rule catalogs. Attribution is in NOTICE.

When to Apply

Use this skill whenever a task will change how a feature looks, feels, moves, or is interacted with.

Must use:

  • Designing new pages (landing, dashboard, admin, SaaS, e-commerce, portfolio, mobile app)
  • Creating or refactoring UI components (buttons, modals, forms, tables, charts, navigation)
  • Choosing a color scheme, typography system, spacing scale, or layout/grid system
  • Reviewing UI code for accessibility, usability, or visual consistency
  • Implementing dark mode, animation, or responsive behavior

Recommended:

  • UI feels "not professional enough" but the reason is unclear
  • Reacting to usability/experience feedback, or doing pre-launch UI polish
  • Aligning cross-platform design (Web / iOS / Android) or building a design system

Skip: pure backend/API/database work, non-visual scripts, infra/DevOps, or performance work unrelated to the interface.

Rule Categories by Priority

When reviewing or building, work the categories top-down — fix CRITICAL before MEDIUM. Full rule lists with platform notes and code examples live in references/ux-rules.md (search them live with --domain ux).

PriorityCategoryImpactDomainMust HaveAvoid
1AccessibilityCRITICALuxContrast 4.5:1, alt text, keyboard nav, aria-labelsRemoving focus rings, icon-only buttons without labels
2Touch & InteractionCRITICALuxMin target 44×44px, 8px+ spacing, loading feedbackHover-only interactions, instant (0ms) state changes
3PerformanceHIGHuxWebP/AVIF, lazy loading, reserve space (CLS < 0.1)Layout thrashing, cumulative layout shift
4Style SelectionHIGHstyle, productMatch product type, consistency, SVG iconsMixing styles randomly, emoji as icons
5Layout & ResponsiveHIGHuxMobile-first breakpoints, viewport meta, no h-scrollHorizontal scroll, fixed px widths, disabling zoom
6Typography & ColorMEDIUMtypography, colorBase 16px, line-height 1.5, semantic tokensBody text < 12px, gray-on-gray, raw hex in components
7AnimationMEDIUMux150–300ms, motion conveys meaning, spatial continuityDecorative-only motion, animating width/height, no reduced-motion
8Forms & FeedbackMEDIUMuxVisible labels, error near field, helper textPlaceholder-only labels, errors only at top
9NavigationHIGHuxPredictable back, bottom nav ≤5, deep linkingOverloaded nav, broken back, no deep links
10Charts & DataLOWchartLegends, tooltips, accessible colorsConveying meaning by color alone

Prerequisites

The query tool is Python 3 with no third-party dependencies. Check it's available:

bash
python3 --version || python --version

On Windows, use python instead of python3 to run the scripts.

How to Use

Run the commands below from this skill's directory (the folder containing this SKILL.md) so the relative scripts/ and data/ paths resolve. The script reads its CSV data relative to its own location, so it works regardless of which project you're in.

Step 1 — Analyze the request

Pull out: product type (e.g. SaaS, e-commerce, fintech, healthcare, beauty/wellness, portfolio, tool), audience & context, style keywords (minimal, playful, dark, content-first, immersive…), and the stack the project actually uses.

Step 2 — Generate a design system (start here)

--design-system searches the product, style, color, landing, and typography domains in parallel, applies the reasoning rules, and returns a complete recommendation (pattern, style, colors, typography, effects) plus anti-patterns to avoid:

bash
python3 scripts/search.py "<product_type> <industry> <keywords>" --design-system [-p "Project Name"]
# Example:
python3 scripts/search.py "beauty spa wellness service" --design-system -p "Serenity Spa"
# Markdown instead of the ASCII box:
python3 scripts/search.py "fintech crypto" --design-system -f markdown

Persist it across sessions with --persist (writes design-system/MASTER.md), and add --page "<name>" to also create a page-specific override under design-system/pages/:

bash
python3 scripts/search.py "<query>" --design-system --persist -p "Project Name" --page "dashboard"

When later building a specific page, read design-system/MASTER.md; if design-system/pages/<page>.md exists, its rules override the master.

Step 3 — Deep-dive any dimension (as needed)

bash
python3 scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]
# Examples:
python3 scripts/search.py "glassmorphism dark" --domain style
python3 scripts/search.py "fintech vibrant" --domain color
python3 scripts/search.py "real-time dashboard" --domain chart
python3 scripts/search.py "animation accessibility loading" --domain ux

Step 4 — Stack-specific implementation guidance

Always pass the project's real stack:

bash
python3 scripts/search.py "<keyword>" --stack <stack>
# Examples:
python3 scripts/search.py "rerender memo list" --stack react
python3 scripts/search.py "navigation list performance" --stack react-native
python3 scripts/search.py "server components streaming" --stack nextjs

Then synthesize the design system + deep-dives + stack guidance and implement.

Search Reference

Domains (--domain)

DomainUse forExample keywords
productProduct-type recommendationssaas, e-commerce, portfolio, healthcare, beauty, fintech
styleUI styles, effects, colorsglassmorphism, minimalism, dark mode, brutalism
colorColor palettes by product typesaas, ecommerce, healthcare, fintech, beauty
typographyFont pairingselegant, playful, professional, modern
google-fontsIndividual Google Font lookupsans serif, monospace, variable, popular
landingPage structure & CTA strategyhero, social-proof, pricing, testimonial
chartChart-type selection & librariestrend, comparison, timeline, funnel, pie
iconsIcon set / glyph lookupnavigation, settings, social, arrows
uxBest practices & anti-patternsaccessibility, animation, z-index, loading
reactReact/Next.js performancewaterfall, bundle, suspense, memo, rerender
webApp-interface a11y/touch (iOS/Android/RN)accessibilityLabel, touch targets, safe areas

Stacks (--stack)

react, nextjs, vue, nuxtjs, nuxt-ui, svelte, astro, html-tailwind, shadcn, swiftui, react-native, flutter, jetpack-compose, angular, laravel, javafx, threejs

Reviewing existing UI

For a UI review or fix, you don't need the generator — go straight to the checklist:

  1. Walk references/ux-rules.md top-down (CRITICAL → LOW). Stop at the first category the UI clearly violates.
  2. For native/mobile work, also run references/app-ui-checklist.md (safe areas, tap feedback, dark-mode parity).
  3. Search --domain ux "<symptom>" for the specific rule, its rationale, and good/bad code examples.

Common sticking points → where to look:

ProblemLook at
Can't decide on style/colorRe-run --design-system with different keywords
Dark-mode contrast issuesux-rules §6: color-dark-mode, color-accessible-pairs
Animations feel unnaturalux-rules §7: spring-physics, easing, exit-faster-than-enter
Form UX is poorux-rules §8: inline-validation, error-clarity, focus-management
Navigation confusingux-rules §9: nav-hierarchy, bottom-nav-limit, back-behavior
Breaks on small screensux-rules §5: mobile-first, breakpoint-consistency
Jank / performanceux-rules §3: virtualize-lists, main-thread-budget, debounce-throttle

Tips

  • Use multi-dimensional queries — product + industry + tone + density ("saas analytics professional data-dense"), not just "app".
  • If results miss, rephrase: "playful neon" → "vibrant dark" → "content-first minimal".
  • --design-system first for the full picture, then --domain to settle any single dimension you're unsure about.
  • As a pre-delivery pass: run --domain ux "animation accessibility loading", then walk ux-rules §1–§3 (the CRITICAL/HIGH tiers).