UI UX Pro Max

The Problem

A collection of 5 self-contained projects providing design intelligence for professional UI/UX across platforms. The repository spans design-system generation, brand-context injection, gallery display, CLI tooling, and utility scripts. No unifying architecture connects the projects; each operates independently.

What This Does

INTERNAL CALL GRAPH

156 code files analyzed across JavaScript (20), Python (92), TypeScript (41), and Shell (3). Import graph contains 153 internal modules and 56 edges with zero circular dependencies. Module instability ranges from 0 (cli/src/types/index, highly stable) to 1 (cli/src.index, gallery.components.GalleryGrid, gallery.components.GalleryGrid - terminal nodes with no importers). Five modules exceed instability 0.85, indicating fragile coupling where changes ripple across multiple importers.

ENTRY POINTS

  • cli/src/index.ts - CLI main entry, degree 5 outgoing
  • cli/src/types/index.ts - type definitions, 7 importers, 0 dependencies
  • projects/healthcare-dashboard/index.html - healthcare vertical showcase
  • projects/portfolio-dark/index.html - dark portfolio showcase
  • projects/saas-landing/index.html - SaaS landing-page showcase

WHAT THIS CODE TOUCHES OUTSIDE ITSELF

The CLI (cli/src/) interfaces with npm-installed ui-ux-pro-max-cli package and manages projects via 217 files (50 code, 93 data). The .claude/skills/ directory (256 files, 35 code, 70 data) contains design-system generators, brand-context injectors, and style-templating scripts that write to project directories. Gallery (gallery/, 35 files) renders design showcases via Next.js. Projects reference design-data CSVs, color palettes, and token schemas that feed into generated output formats.

WHAT EACH FILE IS RESPONSIBLE FOR

  • cli/ (217 files): Command dispatch, project initialization/updates/uninstall, type definitions. Contains decision-heavy logic in cli/src/utils/detect.ts (49 branch points over 130 lines).
  • .claude/skills/ (256 files): Organized by domain - brand (color extraction, brand context injection, token sync), design-system (token embedding, slide generation, slide validation), design (CIP styles, icon systems, logo specifications). Each skill has scripts, references, and templates.
  • gallery/ (35 files): Next.js-configured static gallery displaying project showcards (healthcare, portfolio, SaaS).
  • src/ (89 files): 15 code files alongside 72 data files - design data CIP datasets, industry mappings, style taxonomies.
  • scripts/ (10 files): 7 code files for operational tasks (font refreshing, design-system generation).

Recurring techniques across projects: design-system generation from CSV data, brand-context injection into design tokens, color-palette extraction from assets, slide-template generation with Tailwind integration, and gallery display of generated designs.

How To Use It

Setup: npm install ui-ux-pro-max-cli (per README). Repository has no Dockerfile; local Node.js setup required.

Configuration: cli/package.json and cli/tsconfig.json define build targets. Gallery uses gallery/next.config.js and gallery/package.json. Design-system skills reference .claude/skills/design-system/references/ for token architecture and Tailwind integration specs.

Running it: CLI entry point cli/src/index.ts dispatches commands from cli/src/commands/. Example: npx ui-ux-pro-max-cli init initializes a new project with design-system scaffolding. No environment variables or API keys required for core functionality; skills operate on local project data.

Real-World Use

A designer runs ui-ux-pro-max-cli init to scaffold a new project. The CLI invokes cli/src/commands/init which references type definitions from cli/src/types/index. Design-system generation reads CSV data from .claude/skills/design-system/data/ and produces Tailwind-configured token outputs. The gallery (gallery/) displays the resulting design showcards. A developer can modify cli/src/utils/detect.ts branching logic to change project-detection behavior, or adjust .claude/skills/design-system/scripts/generate-tokens.cjs to alter token-output format.

Code Health & Issues

  • [HIGH] Pin third-party GitHub Actions to commit SHA - .github/workflows uses oven-sh/setup-bun@v2 without pinned SHA; tag can shift, executing unknown code with repository secrets.
  • [HIGH] Commit a lockfile beside the manifest - stack/package.json has no committed lockfile; tested artifact may differ from shipped artifact.
  • [MEDIUM] Declare least-privilege permissions for GITHUB_TOKEN - 2 workflow(s) in .github/workflows/check-asset-sync.yml declare no permissions; token inherits repository default.
  • [MEDIUM] Enable Dependabot or Renovate - 5 manifest(s) with no update bot configured; published advisories remain unpatched.
  • [MEDIUM] Gate pull requests on a dependency vulnerability scan - No dependency scan in CI; known-vulnerable packages may reach production.
  • [MEDIUM] Set persist-credentials: false on checkout - check-asset-sync.yml checkout retains token across all later steps; postinstall scripts could read pushable credentials.
  • [LOW] Set timeout-minutes on workflow jobs - 3 workflow(s) declare no job timeout; wedged steps run to six-hour platform default.
  • [LOW] Add convention files project lacks - Missing .editorconfig, .gitattributes (text=auto eol=lf), and formatter configuration; cross-contributor inconsistencies expected.

The Bottom Line

This repository functions as a portfolio of 5 independent design-intelligence tools rather than a unified codebase. Strengths include extensive design-data CSVs, well-structured skill organization under .claude/skills/, and functional CLI scaffolding. High-severity SDLC gaps center on GitHub Actions pinning, lockfile discipline, and CI gate configuration. Suitable for teams wanting design-system generation and brand-context injection capabilities who can address the identified CI hygiene items.