CodeVetter
← All unpacks
CodeVetter · Repo Unpack evidence

nextlevelbuilder/ui-ux-pro-max-skill

Scanned commit dcc40ff513 dated 2026-09-21 — last upstream commit. Generated by codevetter 1.12.0 on 2026-09-22.

github.com/nextlevelbuilder/ui-ux-pro-max-skill ↗ · 616 files · 12.7 MB

UI UX Pro Max 🇮🇩 Bahasa Indonesia | 🇰🇷 한국어 | 🇻🇳 Tiếng Việt | 🇨🇳 简体中文 | 🇺🇸 English An AI skill that provides design intelligence for building professional UI/UX across multiple platforms and frameworks.

Deep analysis by swe-2 via the devin CLI on 2026-09-22 (runtime not recorded) — every claim below links to its cited source files.

Overview

UI/UX Pro Max is a design-intelligence toolkit packaged three ways: a dependency-free Python search engine (BM25 + regex over canonical CSV datasets) under src/ui-ux-pro-max/, an npm CLI (ui-ux-pro-max-cli, bin `uipro`) that installs the skill into ~20 AI coding assistants via per-platform templates, and a Claude Code plugin rooted at .claude/skills/ with 6 sibling sub-skills. Its flagship feature is a --design-system generator that aggregates five domain searches plus a 192-row reasoning-rules CSV into a formatted design system with an optional Master+Overrides persistence layer. A Next.js style gallery, a separate 'website design stack' bundle (stack/), six GitHub Actions workflows, and a relevance-evaluation harness round out the repo.

System map

The repo is a content product, not a running service: the runtime is a stdlib-only Python 3 CLI (search.py over core.py/design_system.py) reading canonical CSVs under src/ui-ux-pro-max/data/. The TypeScript CLI under cli/ is purely an installer that renders platform templates and copies bundled assets; it never executes the Python. Distribution happens through three mirrored copies of the same data (src/ -> cli/assets/ -> .claude/skills/ui-ux-pro-max/) kept in sync by cli/scripts/sync-assets.mjs and enforced by CI. Supporting surfaces: a Next.js 14 style gallery, a stack/ sub-project that wraps the skill with Playwright/MCP tooling, and six GitHub Actions workflows covering tests, asset sync, catalog refresh, release, and version bumping.

Feature catalog

User-facing surface splits into (a) the Python search CLI with 12 search domains, 22 stack datasets, domain auto-detection, identity exact-match, typo suggestions, and cross-domain redirects; (b) the --design-system generator with dials and persistence; (c) the uipro installer CLI supporting 20 AI platforms plus 'all', global installs, dry-run, update, and uninstall; and (d) the style gallery web app. Data products include 88 style rows (79 searchable / 50 active), 192 product+palette+reasoning triples, 74 font pairings, 25 charts, 105 curated icons, 17 GSAP presets, and 1271 stack guidelines.

All 14 feature catalog claims →

Data flow

Data flows one direction: canonical CSV/JSON datasets under src/ui-ux-pro-max/data/ are consumed in-process by the Python engine (csv.DictReader -> BM25 index -> projected row dicts -> formatted text/JSON), and physically mirrored by sync-assets.mjs into cli/assets/ and .claude/skills/. The CLI copies those bundled assets into the user's project at install time; at query time the skill instructs the agent to shell out to the installed scripts/search.py. Upstream catalog data (Google Fonts API, Phosphor npm packages, google/fonts repo metadata) enters only through the refresh-catalogs workflow as review-only candidates validated by refresh-*.py scripts.

Behavior traces

Three primary flows were traced end-to-end. (1) Domain search: argparse -> search() -> identity/auto-detect -> _search_csv_detailed -> BM25 -> calibrated abstention -> format_output. (2) Design system: generate_design_system -> DesignSystemGenerator.generate -> product search -> reasoning rules -> 5-domain fan-out -> mode-aware palette -> formatter -> optional atomic persist. (3) Install: uipro init -> detectAIType -> prompt -> templateInstall -> renderSkillFile + copyDataAndScripts + copySubSkills. A fourth maintenance flow (sync/check-assets and the relevance gate) is also traced.

Testing signals

Testing is unusually heavy for a dataset repo: 13 stdlib unittest modules under src/ui-ux-pro-max/scripts/tests/ (mirrored into .claude/skills), a fixture-driven relevance evaluator with fingerprint-pinned thresholds, 5 Playwright e2e specs for the CLI (run as a Node test harness, not browser tests), node --test unit tests for the gallery, two bash smoke suites over all domains/stacks, and four validation scripts (CSV structure, semantic data contract, agent-guide claims, catalog summary). The aggregate `npm run verify:data` gate runs all of it and is wired into tests.yml, smoke-stacks.yml, release.yml, and prepublishOnly.

Risk map

The codebase is defensively written (closed decision-rule grammar, slug sanitization, atomic writes, calibrated abstention), but risk concentrates in (a) triple-mirrored data that must stay byte-identical, (b) dead/legacy install paths in the CLI, (c) a hand-rolled CSV parser in the gallery, (d) doc drift, and (e) CI-only network surfaces (GitHub API token, Google Fonts key, npm install of pinned packages). The symlinked gallery data file also contradicts the repo's stated no-symlink rule.

Extension points

Extension is deliberately data-driven: new search domains register in CSV_CONFIG, new stacks in STACK_CONFIG + STACK_CURRENT_* tables, new product categories as aligned rows across products/colors/ui-reasoning.csv, new decision-rule signals in CONDITION_SIGNALS, new dial tiers in DIAL_TIERS, new AI platforms via AI_TYPES + AI_TO_PLATFORM + a templates/platforms/*.json file, and new sub-skills via the subSkills array in sync-assets.mjs. Smoke tests and validators auto-enumerate these registries, so additions are picked up without wiring — but several guards (192-row parity, expected domain/stack counts, identity uniqueness) will fail CI if invariants are missed.

Contributor handoff

Read CLAUDE.md first — it documents the src/ source-of-truth rule and the sync contract. Edit data/scripts/templates only under src/ui-ux-pro-max/, then run `cd cli && npm run sync:assets && npm run check:assets`. Never edit cli/assets/ or .claude/skills/ui-ux-pro-max/{data,scripts} directly (mirrored), but DO edit .claude/skills/ui-ux-pro-max/SKILL.md by hand (it is not generated). The Python layer is stdlib-only — no pip installs. Gate everything through `npm --prefix cli run verify:data` which runs both validators, unittest discovery, the relevance evaluator, both smoke suites, and the asset-sync check.

Languages

LanguageFilesShare of source
Markdown145docs/config
Python10361%
JSON102docs/config
TypeScript4325%
JavaScript2112%
YAML9docs/config
HTML4docs/config
Shell32%

Start reading here

Probable source entrypoint: src/ — inferred from the directory tree and manifest, not the upstream docs.

Source roots

src/ (92 files)

Repository structure

Top-level pathFiles
cli/222
.claude/206
src/92
gallery/34
stack/18
scripts/10
.github/9
docs/5

Docs found: CLAUDE.mdCONTRIBUTING.mdREADME.mddocs/journals/260812-1844-search-data-quality-planning.mddocs/journals/260813-0816-phase-6-accessibility-refresh.mddocs/journals/260813-1622-phase-7-web-stack-freshness.mddocs/journals/260813-1800-search-data-overhaul-completion.mddocs/三个 data-scripts-templates 的区别.md

Package

cli/package.json — ui-ux-pro-max-cli v2.5.0, 9 declared dependencies.

@playwright/test@types/bun@types/node@types/promptschalkcommanderorapromptstypescript

CI & config entrypoints

Structural health signals

Average score 7.6/10 across 92 analyzed source files; 24 hotspots surfaced.

These are deterministic review leads — size, churn, and structural signals — not proof of a bug in this project.

Recent history