
When someone asks you to make their interface feel like Linear or Stripe or just "more premium," this resolves those aesthetics into actual design tokens without guessing. You pick from five archetypes (brutalist, soft-SaaS, dark-tech, etc.) or 138 named design systems, and it maps the colors, typography, spacing, shadows, and motion into your token system while enforcing contrast checks at every step. The brief inference requirement up front is smart: it forces you to name the mood and audience before generating anything, which keeps the output from drifting into generic territory. It's opinionated about accessibility. You can't apply a brand aesthetic that fails WCAG, which is the right call but means you'll sometimes need to adjust aspirational references to meet contrast ratios.
$ npx -y skills add plugin87/ux-ui-agent-skills --skill apply-aesthetic --agent claude-codeInstalls into .claude/skills of the current project.
Step 0: is the kit here? This skill reads files from the kit. Check once:
ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSINGOnKIT_MISSINGonly the skill folders were installed, which is whatnpx skills adddoes. Say so plainly, point the user atnpx ux-ui-agent-skills initor the plugin install, and stop. Do not guess the contents of a file you could not open.
Choose and apply a design direction without breaking accessibility.
${CLAUDE_SKILL_DIR}/../../../taste/design-taste.md → Brief Inference + Variance Mandate). Generating before deciding = slop.${CLAUDE_SKILL_DIR}/../../../taste/aesthetic-systems.md:
python3 ${CLAUDE_SKILL_DIR}/../../../scripts/design_systems.py list (or search <term> / show <name>). Then run node ${CLAUDE_SKILL_DIR}/../../../scripts/library.mjs get <name> and read the DESIGN.md at the path it prints. An npm install carries the index and no spec, so this is what fetches it (checked against the sha256 the kit ships); where the spec is already on disk it fetches nothing. If it prints refused, say the spec could not be fetched and pick from an archetype instead; never write a spec from memory.aesthetic-systems.md): re-point semantic.* tokens to the chosen system's color roles; map typography/spacing/radius/shadow/motion to ${CLAUDE_SKILL_DIR}/../../../tokens/*.json.${CLAUDE_SKILL_DIR}/../../../scripts/contrast.py / a11y-audit). A brand value that fails must be adjusted. Taste never overrides POUR.${CLAUDE_SKILL_DIR}/../../../taste/motion-choreography.md; run the pre-flight aesthetic check in design-taste.md.Updated/overridden semantic tokens + notes on type/space/motion, then render via design-code. Confirm the result passes both the aesthetic check and accessibility.
Sponsors