UI/UX Pro Max

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

Security Scan

The skill's description and bundled data align with a UI/UX helper, but it includes runnable Python scripts shipped inside the skill that the SKILL.md encourages you to execute — that makes the package coherent but potentially risky unless you inspect those scripts first.

Purpose & Capability

Name/description (UI/UX design + implementation guidance) matches the included assets (color palettes, patterns, heuristics) and the presence of a design-system generator script; none of the declared requirements (no env vars, no external binaries) appear out of place.

Instruction Scope

Runtime instructions restrict the agent to reading bundled data files and optionally running a local Python script (scripts/design_system.py). The guidance does not ask for unrelated system files, credentials, or remote endpoints — however, executing bundled scripts grants them arbitrary runtime capability (file I/O, network, subprocess), so running them without code review elevates risk.

Install Mechanism

There is no install spec and no external downloads; all assets are bundled in the skill. That avoids supply-chain download risks. Note: the skill is not purely instruction-only — it includes Python scripts that would be executed from the skill directory rather than installed from a third party.

Credentials

The skill declares no required environment variables, credentials, or config paths, which is proportional for a UI/UX assistant. There are no hidden credential requests in the SKILL.md.

Persistence & Privilege

always:false and default invocation settings are appropriate. The skill does not request permanent platform-wide privilege in metadata. The main persistence concern would be if the bundled scripts modify system state, but that behavior is not declared — you must inspect the scripts to confirm.

What to consider before installing

This skill appears to be what it claims (UI/UX guidance with local data), but exercise caution before running any bundled scripts. Specifically: - The SKILL.md explicitly suggests running python3 skills/ui-ux-pro-max/scripts/design_system.py — executing that will run code included in the skill with whatever privileges your agent/workspace has. Review scripts/core.py, scripts/design_system.py, and scripts/search.py before running. - Look for network calls (requests, urllib, socket), subprocess usage (subprocess, os.system, sh), file writes/reads outside the skill folder, and any hardcoded endpoints or credentials. If you are not comfortable reading the Python, ask the publisher to summarize what the scripts do or run them in an isolated sandbox/container with no network and limited filesystem access. - Because the skill source and homepage are unknown, prefer: (1) manual code review, (2) running the scripts offline in a restricted environment, or (3) using the skill only for its human-readable assets (CSV/README) and not executing the scripts. - If you decide to run the script, run it with a non-privileged user account, with network disabled, and monitor for unexpected connections or filesystem changes. If you want, I can scan the actual Python source (paste it here) for suspicious constructs and point to specific lines to review.

Follow these steps to deliver high-quality UI/UX output with minimal back-and-forth.

1) Triage

Ask only what you must to avoid wrong work:

• Target platform: web / iOS / Android / desktop
• Stack (if code changes): React/Next/Vue/Svelte, CSS/Tailwind, component library
• Goal and constraints: conversion, speed, brand vibe, accessibility level (WCAG AA?)
• What you have: screenshot, Figma, repo, URL, user journey

If the user says "全部都要" (design + UX + code + design system), treat it as four deliverables and ship in that order.

2) Produce Deliverables (pick what fits)

Always be concrete: name components, states, spacing, typography, and interactions.

• UI concept + layout: Provide a clear visual direction, grid, typography, color system, key screens/sections.
• UX flow: Map the user journey, critical paths, error/empty/loading states, edge cases.
• Design system: Tokens (color/typography/spacing/radius/shadow), component rules, accessibility notes.
• Implementation plan: Exact file-level edits, component breakdown, and acceptance criteria.

3) Use Bundled Assets

This skill bundles data you can cite for inspiration/standards.

• Design intelligence data: Read from skills/ui-ux-pro-max/assets/data/ when you need palettes, patterns, or UI/UX heuristics.
• Upstream reference: If you need more phrasing/examples, consult skills/ui-ux-pro-max/references/upstream-skill-content.md.

4) Optional Script (Design System Generator)

If you need to quickly generate tokens and page-specific overrides, use the bundled script:

python3 skills/ui-ux-pro-max/scripts/design_system.py --help

Prefer running it when the user wants a structured token output (ASCII-friendly).

Output Standards

• Default to ASCII-only tokens/variables unless the project already uses Unicode.
• Include: spacing scale, type scale, 2-3 font pair options, color tokens, component states.
• Always cover: empty/loading/error, keyboard navigation, focus states, contrast.