Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
UI UX Pro Max is Next Level Builder's local design-reference skill for agents working on interfaces. It combines searchable CSV and JSON catalogs with Python tools that return guidance for a particular product, UX concern or implementation stack.
The bundled references cover visual styles, product palettes, font pairing, icons, charts, motion and accessibility. A design-system mode combines relevant matches into a proposed direction and can save a master document with page-specific overrides. The package contains guidance and metadata, not a ready-made application or a library of rendered components.
Use this skill when
- A new interface needs a coherent direction for layout, color, type and interaction.
- You need focused guidance on an observable UX issue such as hidden focus, confusing errors or labels that overflow.
- You want recommendations grounded in the project's actual framework rather than an assumed default stack.
- A team needs a saved design-system reference that can be extended with page-specific decisions.
What it can do
- Search local references by one clear intent, such as form error summaries, font pairing or dashboard chart selection.
- Generate a proposed design system using product, style, palette, typography and reasoning matches.
- Provide implementation-oriented guidance across web, mobile and desktop stacks.
- Filter selected guidance for right-to-left compatibility and distinguish matching results from fallback advice.
- Adjust optional variation, motion and density settings when generating a design direction.
- Save a master design-system document and page overrides while preserving existing files unless replacement is explicitly requested.
Typical workflows
- Identify the product, audience, UI problem and actual technology stack from the project.
- Use design-system mode for a broader direction, or a focused domain search for a specific interface concern.
- Check whether the returned matches fit the product and platform, then consult stack-specific guidance where useful.
- Apply the selected recommendations to the interface and verify the resulting behavior, layout and accessibility.
- Persist agreed decisions under the project root if a reusable master reference is needed.
Inputs and output
Provide the product context, target platform, detected stack and a concise description of the design task. Outputs can be terminal or Markdown recommendations, structured JSON and saved design-system documents. The agent remains responsible for implementing and checking the actual interface.
Limitations
The search tools require Python 3 and their complete bundled data directory. Upstream command examples assume a Claude plugin directory layout; a manual installation must resolve the matching local skill path rather than run those examples from an unrelated folder. Catalog matches are recommendations, not proof of accessibility, visual quality or current framework behavior. Font and icon metadata are included, while the fonts, icon packages and their binaries are not. Preserve the bundled provenance and license metadata, and follow each selected asset's own terms when using it. The catalog has not executed the search tools or tested generated interfaces.
What is inside the skill
Section headings from the original SKILL.md (about 2,015 words of instructions). Read the full text in the source repository before installing.
- When to Apply
- Rule Categories by Priority
- Running the search tool
- Workflow
- Query Contract
- Step 1: Analyze User Requirements
- Step 2: Generate Design System (REQUIRED for new pages/projects)
- Step 2b: Persist Design System (Master + Overrides Pattern)
- Step 2c: Design Dials (optional)
- Step 3: Supplement with Detailed Searches (as needed)
- Step 4: Stack Guidelines
- If a search returns 0 results
- Example Workflow
- Output Formats
- Tips for Better Results
- Before Delivering App UI
Bundled files
data/app-interface.csvdata/catalog-summary.jsondata/charts.csvdata/colors.csvdata/data-provenance.jsondata/google-font-licenses.jsondata/google-fonts.csvdata/icons.csvdata/landing.csvdata/motion.csvdata/phosphor-icons-upstream.jsondata/products.csvdata/react-performance.csvdata/stacks/angular.csvdata/stacks/astro.csvdata/stacks/avalonia.csvdata/stacks/flutter.csvdata/stacks/html-tailwind.csvdata/stacks/javafx.csvdata/stacks/jetpack-compose.csvdata/stacks/laravel.csvdata/stacks/nextjs.csvdata/stacks/nuxt-ui.csvdata/stacks/nuxtjs.csvdata/stacks/react-native.csvdata/stacks/react.csvdata/stacks/shadcn.csvdata/stacks/svelte.csvdata/stacks/swiftui.csvdata/stacks/threejs.csvdata/stacks/uno.csvdata/stacks/uwp.csvdata/stacks/vue.csvdata/stacks/winui.csvdata/stacks/wpf.csvdata/styles.csvdata/typography.csvdata/ui-reasoning.csvdata/ux-guidelines.csvreferences/pro-rules.md
Example prompts
- Plan the design system for a Next.js appointment-booking product used on mobile. Compare appropriate layout, palette and typography options from the local references, explain the tradeoffs, and save the agreed master system under the project root without overwriting existing files.
- Review this React checkout form for keyboard navigation, clear errors and narrow-screen reflow. Search the relevant UX outcome first, then React implementation guidance, and turn the applicable findings into specific component changes and checks.
- Choose an accessible chart approach for a dense operations dashboard with 12 monthly series. Use the chart and color references, include a table alternative, and explain which recommendations come from a matching catalog result versus general fallback guidance.
How to install UI UX Pro Max
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
UI UX Pro Max FAQ
What does the UI UX Pro Max skill do?
UI UX Pro Max gives an agent searchable local design references for styles, palettes, typography, accessibility and stack-specific UI decisions, plus a design-system generator.
Which AI agents can use UI UX Pro Max?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install UI UX Pro Max in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made UI UX Pro Max and what is the license?
UI UX Pro Max is published by Next Level Builder under the MIT license. The source is https://github.com/nextlevelbuilder/ui-ux-pro-max-skill/tree/main/.claude/skills/ui-ux-pro-max. The catalog keeps the original attribution.
What permissions does UI UX Pro Max need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.