Provides UI design tokens, component catalogs, and visual quality rules for Vue/Vuetify projects.

Install

mkdir -p .claude/skills/ui-pierreb-devkit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18774" && unzip -o skill.zip -d .claude/skills/ui-pierreb-devkit && rm skill.zip

Installs to .claude/skills/ui-pierreb-devkit

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Design system reference for the Devkit Vue stack (Vuetify 4 + custom theme helpers). Use when asked about styling, theming, layout, design system, Vuetify components, visual verification, or UI patterns. Automatically consumed by /feature when the task has a visual component. Can also be invoked directly for design-only tasks (restyle, theme change, layout fix).
364 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Reference design tokens, typography, spacing, and breakpoints
  • Reference component catalog for Home sections, core layout, and key Vuetify components
  • Reference theme helpers and code patterns
  • Perform visual verification using screenshot flows and review checklists
  • Enforce MD3 typography classes
  • Enforce theme tokens for colors

How it works

The skill provides design system references for the Devkit Vue stack, including tokens, typography, and component catalogs. It enforces visual quality standards through key rules and a 'Beauty pass' checklist.

Inputs & outputs

You give it
styling, theming, layout, or UI pattern task for Devkit Vue stack
You get back
design system reference and visual quality guidelines

When to use ui

  • Update site theme
  • Apply layout fixes
  • Reference design tokens
  • Verify visual component structure

About this skill

UI

Design system reference and visual quality guidelines for the Devkit Vue stack.

This is not a standalone workflow. For full feature implementation, use /feature which automatically applies these guidelines when visual work is involved.

Invoke /ui directly only for pure design tasks (restyle, theme change, layout fix) that don't need the full /feature workflow.

This skill is an enforcer of the design system (Vuetify 4 + MD3 + theme helpers) and a craft baseline — the "Beauty pass" below is teachable, encodable craft (not taste-by-vibes), the difference between correct and beautiful. Net-new brand identity (a bold landing aesthetic, a new visual language) still belongs to creative direction outside this skill; the Beauty pass makes the everyday output stop looking generic.

References

WhatFileContent
Tokens, typography, spacing, breakpointsreferences/design-system.mdVuetify 4 MD3 classes, theme CSS variables, config paths
Component catalogreferences/components.mdHome sections, core layout, module pattern, key Vuetify components
Theme helpers & code patternsreferences/patterns.mdliquidGlassStyle(), style(), overlapStyle(), AOS, responsive
Visual verificationreferences/verification.mdPuppeteer screenshot flow, review checklist

Key rules (quick reminder)

  • Typography: MD3 classes only (text-display-large, NOT text-h1). Responsive: text-display-small text-sm-display-medium
  • Colors: Theme tokens via config or CSS variables (rgb(var(--v-theme-primary))), never hardcoded hex in templates
  • Dark/light: Everything must work in both modes
  • Config-driven: Prefer config options over hardcoded values
  • CSS last resort: Prefer in order: Vuetify props (flat, elevation, variant, density) → Vuetify utility classes (pa-0, d-flex) → Vuetify transitions (v-fade-transition, v-scale-transition) → <style scoped> only if no Vuetify alternative exists
  • Reuse: Check existing components before creating new ones
  • Verify: Screenshot desktop+mobile, light+dark after visual changes

Beauty pass (correct → beautiful)

Consistency + accessibility make a UI correct; these seven rules make it beautiful. Each is a checkable rule with a named failure mode — the inverse of each is exactly what makes a layout read as generic. Apply on every visual surface; they need no bespoke CSS (Vuetify props, spacing classes, elevation, and theme tokens carry all seven). Deeper config levers to push past the generic Material look: references/design-system.md § "Beauty levers".

  1. Whitespace first, then reduce. Start generous, don't fill the viewport; cramped padding is the #1 generic tell. Lean on pa-6/pa-8, section py-12+. Context-calibrate: dense dashboards tighten, but never start cramped.
  2. Hierarchy by weight + color, not size alone. Cap ~3 type sizes per view; de-emphasize secondary/tertiary with a lighter text-medium-emphasis / muted color, not just smaller. Size-only hierarchy is a slop signature.
  3. Spacing on the fixed scale only. Use the spacing classes (steps 016 = 4→64px); never an arbitrary inline margin: 13px. Off-scale spacing reads ad-hoc.
  4. Color reserved for emphasis. Mostly-neutral base (tinted greys via surface/background, not pure grey); primary for the ONE action that matters, not spread across the screen. Even color spread = the default-Material generic look. Never grey text on a colored background.
  5. Depth = soft, two-part elevation. Prefer low elevation-1/elevation-2 (Vuetify's shadows are already the layered contact+ambient pair) or elevation-0 + a subtle surface border; overlap elements to layer. One harsh high-contrast shadow reads cheap.
  6. Proximity groups related items (Gestalt). A field label sits tight to its input; a card's title/body/action cluster with less gap inside than between cards. Uniform spacing everywhere destroys grouping.
  7. Restraint over decoration. Fewer weights, one accent, generous rhythm — boring-and-consistent beats clever-and-busy. Delete an element before adding one.

These seven rules are the canonical craft baseline: name the visual intent when planning a surface, apply the rules while building, and score the rendered result against them in QA. This skill is where they're authored.

Anti-patterns

  • text-h1..text-h6 → use MD3: text-display-large, text-headline-medium
  • Hardcoded colors in templates → use theme variables
  • New components for things existing ones already handle
  • Ignoring dark mode
  • Skipping visual verification
  • Custom CSS when a Vuetify prop/class/transition covers the need
  • Generic-look tells (Beauty pass inverses): cramped padding · hierarchy by size alone · color spread evenly instead of reserved for emphasis · one harsh shadow · arbitrary off-scale spacing · pure untinted greys · grey text on colored backgrounds

When not to use it

  • For full feature implementation that requires more than visual work
  • For net-new brand identity or bold landing aesthetics
  • When hardcoded hex values are preferred for colors

Limitations

  • Not a standalone workflow; for full feature implementation, use `/feature`
  • Net-new brand identity still belongs to creative direction outside this skill
  • Requires everything to work in both dark and light modes

How it compares

This skill acts as an enforcer of specific design system guidelines (Vuetify 4 + MD3) and a craft baseline for visual quality, ensuring consistency and aesthetic appeal beyond basic correctness.

Compared to similar skills

ui side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ui (this skill)024dNo flagsIntermediate
ui-ux-pro-max1,9094moReviewIntermediate
ui-design11moReviewIntermediate
ui02moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

ui-ux-pro-max

nextlevelbuilder

UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

1,9092,023

ui-design

TencentCloudBase

Professional UI design and frontend interface guidelines. Use this skill when creating web pages, mini-program interfaces, prototypes, or any frontend UI components that require distinctive, production-grade design with exceptional aesthetic quality.

15

ui

tim-hub

Builds UI components, landing page sections, hero sections, and contact forms. Use when creating front-end visual elements.

00

design-with-taste

MaggieAppleton

Apply the "Family Values" design philosophy to every UI you build. Use this skill whenever creating frontends, components, apps, landing pages, dashboards, or any user-facing interface. Enforces three core principles — Simplicity (gradual revelation), Fluidity (seamless transitions), and Delight (se

00

ui-ux-pro-max

darkmatter

UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, cr

00

ui-ux-pro-max

majiayu000

Frontend UI/UX design intelligence - activate FIRST when user requests beautiful, stunning, gorgeous, or aesthetic interfaces. The primary skill for design decisions before implementation. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Nati

00

Search skills

Search the agent skills registry