design-frontend
Visual design system patterns for web UIs. Tailwind CSS v4 design tokens and CSS variables, responsive design with container queries, dark mode, layout patterns, and spacing scales. Use when implementing visual designs, working with Tailwind CSS, or building responsive layouts.
Best use case
design-frontend is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Visual design system patterns for web UIs. Tailwind CSS v4 design tokens and CSS variables, responsive design with container queries, dark mode, layout patterns, and spacing scales. Use when implementing visual designs, working with Tailwind CSS, or building responsive layouts.
Teams using design-frontend should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design-frontend/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design-frontend Compares
| Feature / Agent | design-frontend | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Visual design system patterns for web UIs. Tailwind CSS v4 design tokens and CSS variables, responsive design with container queries, dark mode, layout patterns, and spacing scales. Use when implementing visual designs, working with Tailwind CSS, or building responsive layouts.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Visual Design Systems for Web UIs Design system patterns for consistent, accessible, responsive interfaces. Tailwind CSS v4 changes the game with CSS variables for runtime theming. Core patterns: design tokens (colors, spacing, typography), responsive breakpoints and container queries, dark mode with proper contrast, component composition, and spacing scales. Key challenges: hardcoded values instead of tokens (unmaintainable), responsive design without mobile-first thinking, dark mode implemented post-hoc (inaccessible), container queries for component-level responsiveness (not just viewport-based). ## Workflow When implementing visual designs: 1. **Define tokens** — Colors, spacing, typography, shadows as CSS variables in `@theme` 2. **Choose container** — Wrap component in `@container` for container queries 3. **Build mobile-first** — Start with mobile layout, add breakpoints upward 4. **Test dark mode** — Use `dark:` variants; ensure contrast ratios 5. **Validate touch targets** — Min 44x44px for interactive elements 6. **Measure performance** — CSS-in-JS libraries impact paint time; Tailwind is zero-runtime ## Rules Patterns are organized by concern: - **Layout** — Max-width containers, consistent spacing, visual hierarchy - **Responsive Design** — Mobile-first approach, breakpoints, container queries - **Design Tokens** — Color scales, spacing scales, typography families - **Dark Mode** — Proper contrast, color pairs, CSS variables for theming - **Components** — Touch targets, affordances, accessibility See `rules/` for implementation patterns and examples. ## Examples ### Positive Trigger User: "Set up a Tailwind design token system with dark mode support for our component library." Expected behavior: Use `design-frontend` guidance, apply token patterns with CSS variables and color pairs. ### Non-Trigger User: "Write a Node.js REST API for user authentication." Expected behavior: Do not prioritize `design-frontend`; choose a more relevant skill or proceed without it. - Error: Hardcoding color values in classes; theme changes require refactoring - Cause: Not using design tokens; colors scattered across codebase - Solution: Use `@theme` to define colors as CSS variables; reference with `var(--color-*)` - Error: Dark mode looks washed out; low contrast on dark backgrounds - Cause: Color pairs not designed together; assumed inversion works - Solution: Test dark variants; use color scales with proper contrast ratios ## Troubleshooting - Error: Container queries not working; elements not responding to container size - Cause: Parent not marked with `@container` class - Solution: Add `@container` to parent; use `@sm:`, `@md:`, `@lg:` variants on children - Error: Dark mode styles not applying; dark: variants ignored - Cause: Dark mode not configured; use `darkMode: "class"` or `"media"` in config - Solution: Configure dark mode in `tailwind.config.js` or CSS `@custom-variant` - Error: Touch targets too small; users struggle to tap buttons - Cause: Over-optimizing for desktop; assuming mouse precision on mobile - Solution: Use `h-11` / `w-11` (44px) minimum for touch targets
Related Skills
platform-frontend
Framework-agnostic frontend architecture — state management, components, data fetching. Use when building any web frontend, choosing state patterns, or structuring UI code.
design-variations
Generate a gallery of design variations for a UI component. Takes an existing component (referenced by name, pasted code, or screenshot) and produces N distinct rendered alternatives in a single comparison page. Use when exploring visual directions, generating mockups, comparing design approaches for a component, creating A/B candidates, or when anyone says "show me options" or "give me variations" for a UI element.
design-accessibility
WCAG AA and ARIA best practices — screen readers, keyboard navigation, focus management. Use when building any user-facing interface or reviewing accessibility compliance.
agent-skills-manager
Manage AI skills from the Ravn AI Toolkit via corvus CLI — install, update, remove, search, and configure skills for any project. Use when: (1) Installing AI skills into a project, (2) Updating installed skills to latest versions, (3) Browsing or searching available skills, (4) Configuring global or per-project skill sets, (5) Troubleshooting corvus setup. Triggers on: "install skills", "add skills", "update skills", "corvus", "skill manager", "browse skills", "set up AI rules".
type-system-audit
Audit a repository for type-system weaknesses using recent bug-fix commits as hard evidence. Produces prioritized findings tied to specific commits showing which types allowed real bugs. Use when: reviewing type safety, auditing types, analyzing type bugs. Triggers on: type audit, type system review, audit types, type safety audit.
ts-linter
Set up and enforce a strict, production-grade ESLint configuration for TypeScript projects, then systematically fix all linting issues. Use this skill whenever the user asks to add a linter or ESLint, enforce code quality rules, fix linting errors, clean up code style, or add type-aware linting. Trigger on: "lint", "eslint", "code quality", "static analysis", "strict linting", "make it stricter", "make the code stricter", "add better rules", "clean up the codebase", "enforce standards", "fix all the warnings", or "ShadCN lint errors". Handles detection, config generation, dependency installation, auto-fix, and manual remediation. Do NOT use for Biome or Rome projects, Prettier-only formatting, non-TypeScript/JavaScript projects, writing custom ESLint rules or plugins, husky/lint-staged/pre-commit hook setup, or when the user just wants to run an existing linter without changing its configuration.
transcript-notes
Convert meeting transcript .txt files into structured .md notes with metadata, TL;DR, key topics, action items, and quotes. Use when processing raw transcripts into formatted notes. Triggers on: "process transcript", "generate notes from transcript", "transcript to notes", "/transcript-notes".
test-plan-gen
Generate professional QA Test Plan documents (.docx or .pdf) from a structured interview. Trigger on "create/write a test plan", "I need a test plan", "prepare QA documentation", /testplan, or when a user uploads a PRD/requirements and wants a test plan generated.
test-case-gen
Generate, evaluate, audit, and normalize QA test cases to RAVN standards. Trigger on "generate/write/create test cases", "evaluate/score my test cases", "audit my test suite", "review test coverage", "normalize/reformat test cases", or when a user wants test design help. Also triggered by /testcases.
tech-react
React 19 patterns for components, hooks, Server Components, and data fetching. Use when writing React components, managing state with hooks, implementing Suspense boundaries, optimizing renders with proper memoization, or building Server/Client component hierarchies.
tech-drizzle
Drizzle ORM typesafe schema design, relational queries, prepared statements, migrations, and transactions. Use when working with Drizzle ORM, writing database queries, managing migrations, or optimizing query performance with prepared statements.
tech-android
Android and Kotlin development patterns — Compose, architecture, coroutines, Room, navigation, Hilt. Use when building Android apps, writing Jetpack Compose UI, or reviewing Android-specific code.