UI Ux Pro Max Agent Skill
| Catalog-only UI/UX Pro Max entry. The full upstream templates, data, and search workflow are not bundled in Open Design.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/nexu-io/open-design --skill ui-ux-pro-maxThe instruction itself
5 sections, as written by the authorui-ux-pro-max
> Curated from @nextlevelbuilder.
What it does
Catalog-only UI/UX Pro Max entry. The full upstream templates, data, and search workflow are not bundled in Open Design.
Current Open Design scope
Open Design currently ships this entry as discovery metadata only. If this SKILL.md
is the only file under skills/ui-ux-pro-max/, the upstream UI/UX Pro Max
workflow is not available locally.
The full upstream workflow expects additional assets such as the searchable
data CSVs, the scripts/search.py helper, reference material, templates, and
related upstream skill instructions. Without those files, do not tell users that
the full UI/UX Pro Max pattern library or template search is active.
Source
- Upstream: https://github.com/nextlevelbuilder/ui-ux-pro-max-skill
- Category:
design-systems
How to use
This catalogue entry advertises the skill in Open Design so the agent
discovers it during planning. To run the full upstream workflow with
its original assets, scripts, and references, install the upstream
bundle into your active agent's skills directory:
# Inspect the upstream README for exact paths
open https://github.com/nextlevelbuilder/ui-ux-pro-max-skill
Then ask the agent to invoke this skill by name (ui-ux-pro-max) or with
one of the trigger phrases listed in this skill's frontmatter.
If those upstream files are not installed, explain that Open Design only has the
catalog entry for this skill and ask whether to continue with Open Design's
default design-system guidance instead.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take nexu-io/ui-ux-pro-max from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.