web-ui-design-guide
Apply modern, professional web UI design principles when building any web UI component. Only execute this when the current project is a web project and involves UI-related work. Use this skill for UI tasks involving buttons, forms, cards, layouts, navigation, or any visual web component. Ensures clean minimal design, neutral color palettes with single accent color, 8px grid spacing, clear typography hierarchy, and subtle visual effects. Prevents common anti-patterns like rainbow gradients, tiny text, and inconsistent spacing.
What this skill does
# Web UI Design Guide ## Overview Ensure every web UI component built looks modern and professional by applying systematic design principles. This skill provides comprehensive guidelines for color, spacing, typography, and component-specific patterns to achieve clean, minimal, and consistent user interfaces. ## When to Use This Skill Activate this skill when: - Building any web UI component (buttons, forms, cards, navigation, modals, etc.) - Creating layouts or page designs - Implementing design systems or component libraries - Working with UI frameworks (React, Vue, Next.js, shadcn/ui, etc.) - Receiving requests like: - "Create a login form" - "Design a dashboard card" - "Build a navigation header" - "Make this UI look modern" - "Style this component" **Do NOT activate** for: - Backend API development - Database queries - Server configuration - Non-visual code tasks ## Core Design Philosophy Follow these fundamental principles for all UI work: 1. **Clean and Minimal** - Prioritize whitespace, reduce visual clutter 2. **Neutral Color Palette** - Gray/off-white base (80-90%) + ONE accent color (5-10%) 3. **8px Grid System** - All spacing uses multiples of 8: 8, 16, 24, 32, 48, 64px 4. **Typography Hierarchy** - Minimum 16px body text, maximum 2 font families 5. **Subtle Effects** - Understated shadows, selective rounded corners 6. **Mobile-First** - Design for small screens first, expand to larger ## How to Use This Skill ### Step 1: Load Relevant Reference Before implementing any UI component, load the appropriate reference file: ``` Read references/design-principles.md - Core philosophy and principles Read references/color-palette.md - Color system and accent usage Read references/spacing-system.md - 8px grid spacing scale Read references/typography.md - Font sizes, weights, line heights Read references/component-patterns.md - Component-specific best practices Read references/anti-patterns.md - Common mistakes to avoid ``` **Recommendation**: Start with `design-principles.md` for overall philosophy, then load component-specific files as needed. ### Step 2: Apply Component-Specific Patterns For each component type, reference the corresponding section in `component-patterns.md`: - **Button**: `component-patterns.md` → Button section - **Card**: `component-patterns.md` → Card section - **Form**: `component-patterns.md` → Form section - **Navigation**: `component-patterns.md` → Navigation section - **Modal**: `component-patterns.md` → Modal section - **Table**: `component-patterns.md` → Table section - **Badge/Tag**: `component-patterns.md` → Badge section - **Dropdown**: `component-patterns.md` → Dropdown section ### Step 3: Validate Against Anti-Patterns Before finalizing implementation, check `anti-patterns.md` to ensure the design avoids: - ❌ Rainbow gradients or generic purple/blue gradients - ❌ Text smaller than 16px for body content - ❌ Inconsistent spacing (non-8px multiples) - ❌ More than 2 font families - ❌ Border + shadow on the same element - ❌ Unclear interactive states (hover, focus, active) ### Step 4: Ensure System Consistency Apply the **8px grid system** for all spacing: - Use only: 4px (rare), 8px, 12px, 16px, 24px, 32px, 48px, 64px - Reference `spacing-system.md` for component-specific spacing guidelines Use **neutral color palette** as foundation: - Base: #FFFFFF, #FAFAFA, #F5F5F5 - Grays: #E0E0E0, #CCCCCC, #999999, #666666, #333333, #1A1A1A - ONE accent color for actions and emphasis - Reference `color-palette.md` for detailed color usage Maintain **typography hierarchy**: - Body text: minimum 16px, line-height 1.6 - Maximum 2 font families - Clear heading scales (32px H1, 24px H2, 20px H3) - Reference `typography.md` for complete type scale ## Resources ### references/ Documentation loaded into context as needed to inform design decisions: - **design-principles.md** - Core philosophy: clean minimal design, neutral palette, 8px grid, typography hierarchy, subtle effects, mobile-first - **color-palette.md** - Neutral base colors, single accent color usage, semantic colors, examples and anti-patterns - **spacing-system.md** - 8px grid scale, component spacing guidelines, responsive spacing - **typography.md** - Font selection, type scale, weights, line lengths, component typography - **component-patterns.md** - Design patterns for buttons, cards, forms, navigation, modals, tables, badges, dropdowns - **anti-patterns.md** - Common design mistakes to avoid with alternatives ## Quick Decision Tree ``` UI Component Request │ ├─ What component? → Load component-patterns.md section │ ├─ What spacing? → Use 8px grid (spacing-system.md) │ ├─ What colors? → Neutral base + accent (color-palette.md) │ ├─ What typography? → 16px+ body, clear hierarchy (typography.md) │ └─ Validation → Check anti-patterns.md ``` ## Examples **Good Request Flow**: ``` User: "Create a login form" → Read references/component-patterns.md (Form section) → Read references/spacing-system.md (Form spacing) → Apply: 16px input text, 8px label gap, 24px button spacing → Validate against anti-patterns.md → Implement with neutral colors + accent for primary button ``` **Component Implementation Checklist**: - ✅ Spacing uses 8px multiples - ✅ Text minimum 16px for body - ✅ Neutral colors (80-90%) + accent color (5-10%) - ✅ Clear hover/focus/active states - ✅ No rainbow gradients or generic purple/blue - ✅ Maximum 2 font families - ✅ Mobile-first responsive design
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.