ui ux pro max

Design Community

Skill notes

When to Apply

Use this Skill when the task involves UI structure, visual design decisions, interaction patterns, or user experience quality control: designing new pages, creating/refactoring UI components, choosing color/typography/spacing/layout systems, reviewing UI for UX/accessibility/consistency, implementing navigation/animation/responsive behavior, or improving perceived quality and usability. Skip it for pure backend logic, API/database design, non-visual performance work, infrastructure/DevOps, or non-visual scripts — unless the task changes how something looks, feels, moves, or is interacted with.

Rule Categories by Priority

Follow priority 1→10 to decide which category to focus on first; use --domain <Domain> to query full details. The full rule text for every category lives in references/quick-reference.md — read it on demand rather than loading it every time. Priority · Category · Impact · Domain · Key Checks (Must Have) · Anti-Patterns (Avoid) 1 · Accessibility · CRITICAL · ux · Contrast 4.5:1, Alt text, Keyboard nav, Aria-labels · Removing focus rings, Icon-only buttons without labels

Running the search tool

The search script lives inside this skill's own directory, not the project directory. Always invoke it by its full path — do not assume a particular working directory: If python is not found, try python3, then py -3. Requires Python 3.x, no external dependencies (see README for install instructions if Python is missing).

Query Contract

Choose the smallest search mode that fits the request: New project/page or system-wide visual direction → use --design-system. Targeted concern or component bug → use one explicit --domain.

Step 1: Analyze User Requirements

Extract from the user request: Product type: SaaS, e-commerce, portfolio, dashboard, entertainment, tool, productivity, or hybrid Target audience & context: age group, usage context (commute, leisure, work) Style keywords: playful, vibrant, minimal, dark mode, content-first, immersive, etc. Stack: detect from the project — check package.json deps (react/next/vue/svelte/nuxt/@angular), pubspec.yaml (Flutter), *.xcodeproj/Package.swift (SwiftUI), composer.json (Laravel), or React Native markers (app.json + react-native dep).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nextlevelbuilder · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview ui-ux-pro-max-53f0c5f438.preview
# If a search returns 0 results

1. Retry once with a narrower query or an explicit domain/stack.
2. If still empty, fall back to the priority table above and say explicitly to the user that this recommendation came from the built-in defaults, not a database match (e.g. "no palette match for X, using general SaaS defaults").
3. Never present a 0-result search as if it returned data.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.