Design generator
skillTurn requirements into a design-system proposal.
UI/UX design-intelligence skill with searchable styles, palettes, typography, charts, stack guidance, anti-patterns, and UX rules.
UI/UX design-intelligence skill with searchable styles, palettes, typography, charts, stack guidance, anti-patterns, and UX rules.
uipro init --ai claude --globalEach card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.
Turn requirements into a design-system proposal.
Search visual styles.
Select palettes.
Select font pairs/rules.
Apply UX and stack rules.
These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns intelligent design system generation. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns 192 industry-specific reasoning rules. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns features. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns resilient text and compact ui. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns style taxonomy. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns 💎 basic vs. premium version comparison. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns 🟢 basic version (this repository). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns 🟡 premium version. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns using claude marketplace (claude code). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns using cli (recommended). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns skill mode (auto-activate). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream treats this as a distinct part of nextlevelbuilder/ui-ux-pro-max-skill. In plain language, use this area when your task concerns workflow mode (slash command). Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.
Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.
Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.
Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.
Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.
These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.
/ui-ux-pro-max Build a landing page for my SaaS productBuild a landing page for my SaaS product
Create a dashboard for healthcare analytics
Design a portfolio website with dark mode
Make a mobile app UI for e-commerce
Build a fintech banking app with dark themeuipro versions # List available versions
uipro update # Refresh skill files from installed CLI package
uipro update --global # Refresh global skill files from installed CLI package
uipro init --offline # Compatibility flag; installs bundled templates
uipro uninstall # Remove skill (auto-detect platform)
uipro uninstall --ai claude # Remove specific platform
uipro uninstall --global # Remove from global installNone documented
A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.
None documented
Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.
None documented
Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.
None documented
Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.
git diff before committing.127.0.0.1 unless you intentionally secure and expose them.The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.