brycewang-stanford/ui-ux-pro-max
skills/33-Galaxy-Dawn-claude-scholar/skills/ui-ux-pro-max/SKILL.md
This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.
$ install --global
skillsauthnpx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research ui-ux-pro-maxInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 4, 2026, 3:55 AM111.2s3 files scanned
SKILL.md
- name:
- ui-ux-pro-max
- description:
- This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.
- version:
- 0.2.0
UI/UX Pro Max
Use this skill to turn a vague UI request into a concrete design system plus implementation guidance.
Role
This skill is for:
- design-system selection,
- palette and typography choices,
- UX review and remediation,
- stack-aware frontend implementation guidance,
- lightweight design-system persistence for multi-page work.
It is not a replacement for product strategy or user research. Use it to make execution sharper after the product direction is already roughly known.
Core workflow
1. Infer the request shape
Extract the minimum design signals first:
- product type,
- industry,
- style keywords,
- target platform,
- implementation stack.
If the user does not specify a stack, default to html-tailwind.
2. Generate the design system first
Use the helper script to produce a compact design recommendation:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "<product_type> <industry> <keywords>" --design-system -p "Project Name"
This produces:
- recommended style direction,
- palette family,
- typography direction,
- interaction / visual effects,
- landing or layout bias,
- anti-patterns to avoid.
If the work spans multiple turns or pages, persist the design system:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "<query>" --design-system --persist -p "Project Name"
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "<query>" --design-system --persist -p "Project Name" --page "dashboard"
This creates:
design-system/MASTER.md- optional page-level override notes under
design-system/pages/
3. Pull targeted guidance only when needed
Use a focused search instead of loading everything at once:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "glassmorphism dark" --domain style
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "animation accessibility" --domain ux
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "real-time dashboard" --domain chart
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "elegant luxury serif" --domain typography
Supported domains:
productstylecolortypographylandingchartux
4. Add stack-specific guidance before coding
python3 "${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-pro-max/scripts/search.py" "forms table responsive" --stack html-tailwind
Supported stacks:
html-tailwindreactnextjsvuesvelteswiftuireact-nativefluttershadcnjetpack-compose
5. Synthesize before implementation
After gathering the design system, convert it into:
- layout structure,
- component rules,
- visual tokens,
- interaction rules,
- accessibility constraints,
- implementation notes for the chosen stack.
Do not dump raw search output into the final answer. Use it to justify a coherent design direction.
Default output shape
A good response should usually include:
- product and UI framing,
- recommended style system,
- palette and typography,
- component and layout rules,
- accessibility and interaction checks,
- stack-aware implementation notes.
Safety rules
- Do not hardcode a design language without connecting it to the product type.
- Do not use emoji as primary UI iconography.
- Do not weaken text contrast for visual flair.
- Do not scale interactive cards on hover if it destabilizes layout.
- Do not use animation that violates
prefers-reduced-motion. - Do not invent unsupported helper scripts or datasets; use the bundled
search.pyanddata/ui-reasoning.csvonly.
References
Load only what is needed:
references/USAGE.md- recommended command patterns and retrieval flowdata/ui-reasoning.csv- compact product-to-design heuristics used by the helper scriptscripts/search.py- deterministic helper for design-system, domain, and stack lookup
Related Skills
brycewang-stanford/thematic-analysis
development
VerifiedTrustedCommunity
Conduct rigorous thematic analysis (TA) of qualitative data following Braun and Clarke's (2006) six-phase framework. Use whenever the user mentions 'thematic analysis', 'TA', 'Braun and Clarke', 'qualitative coding', 'identifying themes', or asks for help analysing interviews, focus groups, open-ended survey responses, or transcripts to identify patterns. Also trigger for questions about inductive vs theoretical coding, semantic vs latent themes, essentialist vs constructionist epistemology, building a thematic map, or writing up a qualitative findings section. Covers all six phases, the four upfront analytic decisions, the 15-point quality checklist, and the five common pitfalls. Produces a Word document write-up and an annotated thematic map. Does NOT cover IPA, grounded theory, discourse analysis, conversation analysis, or narrative analysis — use a different method for those.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/slr-prisma
development
VerifiedTrustedCommunity
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a review paper. This skill covers the full PRISMA 2020 checklist (27 items), produces a Word document manuscript in strict journal article format, generates an annotated PRISMA flow diagram, and enforces APA 7th Edition referencing throughout. It does NOT cover meta-analysis or statistical pooling. By Chuah Kee Man.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/running-placebo-analysis
testing
VerifiedTrustedCommunity
Performs placebo-in-time sensitivity analysis with hierarchical null model and optional Bayesian assurance. Use when checking model robustness, verifying lack of pre-intervention effects, or estimating study power.
1,685SKILL.mdUpdated Jun 5, 2026
brycewang-stanford/running-causalpy-experiments
data-ai
VerifiedTrustedCommunity
Fit, summarize, plot, and interpret a chosen CausalPy experiment. Use after the causal method has been selected, including when configuring PyMC/sklearn models and scale-aware custom priors.
1,685SKILL.mdUpdated Jun 5, 2026