[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CXFNFFTVZ77W9S855KQMSR":3,"skill-same:01M7CXFNFFTVZ77W9S855KQMSR":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CXFNFFTVZ77W9S855KQMSR","ui-design-system",null,"React UI component systems with TailwindCSS + Radix + shadcn\u002Fui. Stack: TailwindCSS (styling), Radix UI (primitives), shadcn\u002Fui (components), React\u002FNext.js. Capabilities: design system architecture, accessible components, responsive layouts, theming, dark mode, component composition. Actions: review, design, build, improve, refactor UI components. Keywords: TailwindCSS, Radix UI, shadcn\u002Fui, design system, component library, accessibility, ARIA, responsive, dark mode, theming, CSS variables, component architecture, atomic design, design tokens, variant, slot, composition. Use when: building component libraries, implementing shadcn\u002Fui, creating accessible UIs, setting up design systems, adding dark mode\u002Ftheming, reviewing UI component architecture.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamhvw8-dot-claude\u002Fui-design-system\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ui-design-system\ndescription: \"React UI component systems with TailwindCSS + Radix + shadcn\u002Fui. Stack: TailwindCSS (styling), Radix UI (primitives), shadcn\u002Fui (components), React\u002FNext.js. Capabilities: design system architecture, accessible components, responsive layouts, theming, dark mode, component composition. Actions: review, design, build, improve, refactor UI components. Keywords: TailwindCSS, Radix UI, shadcn\u002Fui, design system, component library, accessibility, ARIA, responsive, dark mode, theming, CSS variables, component architecture, atomic design, design tokens, variant, slot, composition. Use when: building component libraries, implementing shadcn\u002Fui, creating accessible UIs, setting up design systems, adding dark mode\u002Ftheming, reviewing UI component architecture.\"\nlicense: MIT\nversion: 2.0.0\n---\n\n# UI\u002FUX Design & Development Expert\n\n**Comprehensive UI\u002FUX design, review, and improvement for modern web applications.**\n\nProduction-ready implementations with **TailwindCSS + Radix UI + shadcn\u002Fui** and modern React patterns.\n\n## Stack Architecture\n\n### The Three Pillars\n\n**Layer 1: TailwindCSS (Styling Foundation)**\n- Utility-first CSS framework with build-time generation\n- Zero runtime overhead, minimal production bundles\n- Design tokens: colors, spacing, typography, breakpoints\n- Responsive utilities and dark mode support\n\n**Layer 2: Radix UI (Behavior & Accessibility)**\n- Unstyled, accessible component primitives\n- WAI-ARIA compliant with keyboard navigation\n- Focus management and screen reader support\n- Unopinionated - full styling control\n\n**Layer 3: shadcn\u002Fui (Beautiful Components)**\n- Pre-built components = Radix primitives + Tailwind styling\n- Copy-paste distribution (you own the code)\n- Built-in React Hook Form + Zod validation\n- Customizable variants with type safety\n\n### Architecture Hierarchy\n\n```\nApplication Layer\n    ↓\nshadcn\u002Fui Components (Beautiful defaults, ready-to-use)\n    ↓\nRadix UI Primitives (Accessible behavior, unstyled)\n    ↓\nTailwindCSS Utilities (Design system, styling)\n```\n\n**Key Principle:** Each layer enhances the one below. Start with Tailwind for styling, add Radix for accessible behavior, use shadcn\u002Fui for complete components.\n\n## Core Capabilities\n\n### UI\u002FUX Review & Audit\nSystematic evaluation of existing interfaces:\n- **Component Architecture Review:** Analyze component composition, reusability, and single responsibility\n- **Accessibility Audit:** WCAG 2.1\u002F2.2 AA\u002FAAA compliance, keyboard navigation, screen reader support\n- **Performance Analysis:** Core Web Vitals (LCP, FID, CLS), bundle size, render performance\n- **Responsive Design Review:** Mobile-first implementation, breakpoint usage, container queries\n- **Design System Consistency:** Token usage, spacing scale adherence, color palette compliance\n- **Code Quality:** React best practices, hooks usage, state management patterns\n- **Visual Hierarchy:** Typography scale, spacing rhythm, color contrast, focus indicators\n\n### UI\u002FUX Design\nCreating production-ready interface designs:\n- **Component Design:** Atomic design principles, composition patterns, variant systems\n- **Layout Architecture:** Grid systems, flexbox patterns, responsive containers\n- **Interaction Design:** Hover states, focus states, loading states, error states\n- **Design Tokens:** Three-tier token system (primitive → semantic → component)\n- **Color Systems:** OKLCH color space, accessible palettes, dark mode support\n- **Typography Systems:** Scale design, hierarchy, readability optimization\n- **Animation & Transitions:** Micro-interactions, loading feedback, state changes\n\n### UI\u002FUX Improvement\nEnhancing existing implementations:\n- **Accessibility Enhancement:** ARIA patterns, semantic HTML, keyboard navigation\n- **Performance Optimization:** Code splitting, lazy loading, virtualization, image optimization\n- **Responsive Refinement:** Breakpoint optimization, mobile-first improvements\n- **Component Refactoring:** Extract shared patterns, reduce complexity, improve reusability\n- **Visual Polish:** Spacing consistency, typography refinement, color harmony\n- **State Management:** Optimistic updates, error handling, loading states\n- **Developer Experience:** Component documentation, Storybook stories, type safety\n\n### Styling Integration\nFramework-agnostic styling approaches:\n- **Tailwind with Components:** Utility-first styling for any framework\n- **CSS-in-JS:** emotion, styled-components, vanilla-extract\n- **CSS Modules:** Scoped styles without runtime overhead\n- **Design System Integration:** Token-based styling across frameworks\n\n## When to Use Each Layer\n\n### Use TailwindCSS Directly When:\n- Building custom layouts and spacing\n- Styling static content and containers\n- Rapid prototyping without complex interactions\n- Non-interactive UI elements\n\n**Example scenarios:** Hero sections, grid layouts, cards without interaction, text styling\n\n### Use Radix UI Primitives When:\n- Building custom component libraries\n- Need accessibility but require custom design\n- shadcn\u002Fui doesn't have the component you need\n- Full control over component structure required\n\n**Example scenarios:** Custom date picker, unique navigation pattern, specialized modal behavior\n\n### Use shadcn\u002Fui Components When:\n- Building standard UI components quickly\n- Need beautiful defaults with customization options\n- Enterprise application development\n- Form-heavy applications with validation\n\n**Example scenarios:** Admin dashboards, CRUD applications, settings pages, data tables\n\n## Critical Design Principles\n\n### 1. Progressive Enhancement\nStart simple, enhance as needed:\n1. Tailwind utilities for basic styling\n2. Add Radix primitives for interaction\n3. Use shadcn\u002Fui for complete solutions\n4. Customize components in your codebase\n\n### 2. Composition Over Complexity\nBuild complex UIs from simple, reusable components:\n- Small, focused components (single responsibility)\n- Compose primitives rather than creating monoliths\n- Leverage component slots and children patterns\n\n### 3. Accessibility First\nRadix UI handles accessibility automatically:\n- ARIA attributes applied correctly\n- Keyboard navigation built-in\n- Focus management and trapping\n- Screen reader compatibility\n\n**Never override accessibility features** - enhance them.\n\n### 4. Design Token Consistency\nUse Tailwind's design system consistently:\n- Stick to spacing scale (4, 8, 16, 24px)\n- Use color palette (50-950 shades)\n- Apply typography scale systematically\n- Avoid arbitrary values unless necessary\n\n### 5. Mobile-First Responsive\nAlways design mobile-first, scale up:\n- Base styles for mobile\n- Use breakpoints (sm, md, lg, xl, 2xl) to enhance\n- Test on actual devices, not just browser resize\n\n## Setup Strategy\n\n### Installation Order\n1. **TailwindCSS** - Foundation\n2. **shadcn\u002Fui CLI** - Includes Radix dependencies\n3. **Add components** - Install only what you need\n4. **Configure theme** - CSS variables + Tailwind config\n5. **Setup dark mode** - Theme provider + toggle\n\n### Configuration Best Practices\n\n**Tailwind Config:**\n- Use `content` paths correctly (scan all component files)\n- Extend theme with CSS variables, not hardcoded values\n- Enable dark mode with `class` strategy\n- Install `tailwindcss-animate` plugin\n\n**CSS Variables (Three-Tier System):**\n```css\n:root {\n  \u002F* Tier 1: Primitives (immutable) *\u002F\n  --gray-50: 250 250 250;\n  --gray-900: 24 24 27;\n  --blue-500: oklch(0.55 0.22 264);\n\n  \u002F* Tier 2: Semantics (theme-aware) *\u002F\n  --background: var(--gray-50);\n  --foreground: var(--gray-900);\n  --primary: var(--blue-500);\n\n  \u002F* Tier 3: Components *\u002F\n  --button-height: 2.5rem;\n  --card-padding: 1.5rem;\n}\n\n.dark {\n  \u002F* Only semantic tokens change *\u002F\n  --background: var(--gray-900);\n  --foreground: var(--gray-50);\n}\n```\n\n**Color Space Recommendation:**\n- **Modern**: Use OKLCH for perceptual uniformity\n- **Legacy support**: Use HSL with fallbacks\n- **Avoid**: RGB\u002FHEX for design tokens (not human-readable)\n\n**Token Storage:**\n- Store in JSON for platform-agnostic distribution\n- Transform to CSS variables, Swift, XML using Style Dictionary\n- Version control tokens separately from component code\n\n**Path Aliases:**\n- Configure `@\u002Fcomponents` and `@\u002Flib` in tsconfig\n- Ensure consistency between Next.js and TypeScript configs\n- Use aliases in imports for cleaner code\n\n## Integration Patterns\n\n### Pattern 1: shadcn\u002Fui + Custom Tailwind\nUse shadcn\u002Fui components as base, customize with Tailwind classes:\n- Apply custom spacing, colors via className prop\n- Override default styles with Tailwind utilities\n- Maintain component accessibility\n\n### Pattern 2: Radix Primitives + Tailwind\nBuild custom components from scratch:\n- Use Radix for behavior (Dialog, Dropdown, etc.)\n- Style completely with Tailwind utilities\n- Full control over structure and appearance\n\n### Pattern 3: Hybrid Approach\nModify shadcn\u002Fui components in your codebase:\n- Edit component files in `components\u002Fui\u002F`\n- Add new variants, sizes, or styles\n- Maintain type safety with CVA (Class Variance Authority)\n\n### Pattern 4: Component Composition\nCombine multiple primitives for complex UIs:\n- Popover + Select for searchable dropdown\n- Dialog + Form for modal forms\n- Tabs + Cards for multi-section interfaces\n\n## Design Token Architecture\n\nUse three-tier token system for scalable, maintainable design systems:\n- **Tier 1 (Primitive)**: Raw values (`gray-50`, `spacing-4`)\n- **Tier 2 (Semantic)**: Purpose-driven (`background-primary`, `text-error`)\n- **Tier 3 (Component)**: Component-specific (`button-height`, `card-padding`)\n\n**Modern Color:** Use OKLCH color space for perceptual uniformity and better accessibility calculations.\n\n**📖 See [DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md) for:**\n- Complete three-tier token system implementation\n- OKLCH color space guide and examples\n- Token naming conventions and best practices\n- CSS variable configuration\n- Multi-theme support patterns\n\n## Responsive Design Strategy\n\n**Mobile-first approach:** Start with mobile (0-639px), scale up through sm\u002Fmd\u002Flg\u002Fxl\u002F2xl breakpoints.\n\n**Key patterns:** Layout shifts (column→row), component switching (Dialog→Drawer), container queries for modular responsiveness.\n\n**📖 See [RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md) for:**\n- Complete breakpoint strategy and implementation\n- Responsive component patterns and examples\n- Container queries guide\n- Image optimization strategies\n- Performance considerations for responsive design\n- Comprehensive testing checklist\n\n## Form Architecture\n\n**Strategy:** React Hook Form + Zod for schema-first validation with type inference and accessible error handling.\n\n**📖 See [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md#form-architecture) for:**\n- Complete React Hook Form + Zod setup\n- Reusable field wrapper patterns\n- Multi-step form implementation\n- Accessibility requirements checklist\n\n## Performance Best Practices\n\n**Core strategies:** Code splitting (React.lazy), Tailwind optimization (accurate content paths), virtualization (@tanstack\u002Freact-virtual for long lists).\n\n**📖 See [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md) for:**\n- Complete performance optimization guide\n- Core Web Vitals optimization strategies\n- Bundle analysis and tree shaking\n- Common pitfalls and solutions\n- Performance monitoring setup\n\n## Component Customization & Dark Mode\n\n### Customization Strategies\n1. **Direct Modification**: Edit shadcn\u002Fui files in your codebase\n2. **Variant Extension**: Use CVA for type-safe variants\n3. **Wrapper Components**: Add custom logic around base components\n4. **Theme Customization**: Modify CSS variables globally\n\n### Dark Mode Setup\n1. **ThemeProvider** with next-themes\n2. **Class strategy** (`class`, not media query)\n3. **CSS variables** in `.dark` class\n4. **Accessible toggle** component\n\n**📖 See [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md) for:**\n- Complete customization strategies with examples\n- CVA variant implementation guide\n- Dark mode setup and configuration\n- Design considerations and testing\n- Form architecture patterns\n\n## Accessibility Standards\n\n### Radix UI Built-In Guarantees\n- ✅ ARIA attributes applied correctly\n- ✅ Keyboard navigation functional\n- ✅ Focus management and trapping automatic\n- ✅ Screen reader compatible\n\n### WCAG Contrast Requirements (Critical)\n\n**WCAG 2.1 Level AA (Legal Minimum):**\n- Normal text: **4.5:1** minimum contrast ratio\n- Large text (18pt\u002F14pt bold+): **3:1** minimum\n- UI components\u002Fgraphics: **3:1** minimum\n- **Industry standard**: Most legal requirements specify AA\n\n**WCAG Level AAA (Enhanced):**\n- Normal text: **7:1** contrast ratio\n- Large text: **4.5:1** contrast ratio\n- **Best practice**: Aim for AAA when design constraints allow\n\n**Measurement:**\n- Contrast ratio range: 1:1 (white on white) to 21:1 (black on white)\n- Use tools: WebAIM Color Contrast Checker, browser DevTools\n- Test during design phase, not after implementation\n\n**OKLCH Advantage:**\nPerceptually uniform color space makes contrast calculations more reliable and predictable compared to HSL.\n\n### Implementation Checklist\n- ✅ All text meets 4.5:1 minimum (AA standard)\n- ✅ Interactive elements meet 3:1 minimum\n- ✅ Provide descriptive labels (`aria-label`, `\u003Clabel>`)\n- ✅ Test complete keyboard navigation flow\n- ✅ Verify visible focus indicators (not just browser default)\n- ✅ Test with screen readers (NVDA, JAWS, VoiceOver)\n- ✅ Use semantic HTML elements (`\u003Cbutton>`, `\u003Cnav>`, `\u003Cmain>`)\n- ✅ Provide alternative text for images and icons\n- ✅ Ensure dark mode maintains contrast standards\n\n### Testing Strategy\n1. **Automated**: Use contrast checkers during design\n2. **Manual**: Tab through entire interface\n3. **Screen readers**: Test with at least one screen reader\n4. **Real users**: Include users with disabilities in testing\n\n## Common Pitfalls\n\nAvoid these frequent issues:\n1. **Dynamic classes**: Tailwind doesn't generate at runtime → use conditionals\n2. **Content config**: Verify paths include all component files\n3. **Import paths**: Check tsconfig.json aliases\n4. **Dark mode**: Ensure ThemeProvider setup and CSS variables\n5. **Accessibility**: Never remove ARIA attributes\n\n**📖 See [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md#common-pitfalls) for complete troubleshooting guide with 10+ common issues and solutions.**\n\n## Resources\n\n### Official Documentation\n- **TailwindCSS:** https:\u002F\u002Ftailwindcss.com\u002Fdocs\n- **Radix UI:** https:\u002F\u002Fwww.radix-ui.com\u002Fprimitives\n- **shadcn\u002Fui:** https:\u002F\u002Fui.shadcn.com | https:\u002F\u002Fui.shadcn.com\u002Fllms.txt\n\n### Authoritative Design System Sources\n- **USWDS Design Tokens:** https:\u002F\u002Fdesignsystem.digital.gov\u002Fdesign-tokens\u002F\n- **Smashing Magazine Naming:** https:\u002F\u002Fwww.smashingmagazine.com\u002F2024\u002F05\u002Fnaming-best-practices\u002F\n- **OKLCH Color Space:** https:\u002F\u002Fevilmartians.com\u002Fchronicles\u002Foklch-in-css-why-quit-rgb-hsl\n- **WCAG Contrast:** https:\u002F\u002Fwebaim.org\u002Farticles\u002Fcontrast\u002F\n\n### Reference Files (Detailed Guides & Patterns)\n\n**Core Concepts:**\n- **[DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md)** - Three-tier token system, OKLCH, naming\n- **[RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md)** - Breakpoints, container queries, testing\n- **[CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md)** - Component customization, dark mode, forms\n- **[PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md)** - Performance, Core Web Vitals, pitfalls\n\n**Implementation References:**\n- **[TAILWIND_REFERENCE.md](references\u002FTAILWIND_REFERENCE.md)** - Complete utilities\n- **[RADIX_REFERENCE.md](references\u002FRADIX_REFERENCE.md)** - Primitives with code\n- **[SHADCN_REFERENCE.md](references\u002FSHADCN_REFERENCE.md)** - Components with install\n- **[INTEGRATION_PATTERNS.md](references\u002FINTEGRATION_PATTERNS.md)** - Advanced patterns\n\n## Triggers & Use Cases\n\n**Activate for:** UI\u002FUX review\u002Faudit | Design system architecture | Accessibility audit (WCAG) | Design tokens (3-tier system) | Color systems (OKLCH) | Typography systems | Spacing\u002Flayout design | Tailwind\u002FRadix\u002Fshadcn\u002Fui setup | Responsive design patterns | Dark mode theming | Component library design\n\n**Do NOT activate for:** React\u002FNext.js architecture (use react-nextjs-expert) | State management | Server Components | Backend APIs | Database design | Infrastructure\u002FDevOps\n\n## Behavioral Traits\n\n**Core Philosophy:** User-centric | Performance-aware (Core Web Vitals) | Accessibility-first (WCAG AA) | Evidence-based | Maintainable | Type-safe\n\n**Design Principles:** Progressive enhancement | Mobile-first | Atomic design | Consistent tokens (3-tier) | Semantic HTML | Comprehensive error handling\n\n**Code Quality:** Component composition | Single responsibility | Proper hooks usage | Optimized rendering | Comprehensive testing\n\n## Response Approach\n\n**Review:** Understand context → Systematic audit → Identify issues → Provide evidence → Recommend solutions → Prioritize\n\n**Design:** Gather requirements → Choose architecture → Design tokens → Component structure → Implement accessibly → Include states → Responsive → Document\n\n**Improve:** Analyze current state → Identify bottlenecks → Plan improvements → Implement incrementally → Measure impact → Document → Test\n\n**Integration:** Verify compatibility → Follow official patterns → Best practices → Type safety → Performance budget → Error boundaries\n\n## Implementation Checklist\n\n**Setup:** Install Tailwind + shadcn\u002Fui | Configure three-tier tokens | Set up dark mode | Create `cn()` helper\n\n**Development:** Apply mobile-first design | Implement dark mode | Test accessibility | Verify WCAG AA contrast\n\n**Production:** Validate Tailwind purging | Test all states | Cross-browser testing | Performance audit\n\n**📖 Detailed checklists available in:**\n- [DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md#implementation-checklist)\n- [RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md#testing-checklist)\n- [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md#accessibility-requirements)\n- [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md#optimization-checklist)\n\n## Best Practices Summary\n\n**Design Tokens:** Three-tier system | OKLCH color space | Purpose-driven naming\n**Accessibility:** WCAG AA minimum (4.5:1 text, 3:1 UI) | Keyboard navigation | Screen readers\n**Performance:** Code splitting | Virtualization | Tailwind optimization\n**Maintenance:** Modular components | Documentation | Version control tokens\n\n## Skill Summary\n\n**Primary Functions:**\n1. **Review:** Audit UI\u002FUX for accessibility, performance, and design system consistency\n2. **Design:** Create production-ready interfaces with modern React and styling systems\n3. **Improve:** Enhance existing implementations for better UX, performance, and maintainability\n\n**Technology Focus:**\n- TailwindCSS, Radix UI, shadcn\u002Fui (styling layer)\n- Design tokens and design systems\n- Accessibility standards (WCAG 2.1\u002F2.2)\n- Responsive design and mobile-first patterns\n- Color systems (OKLCH) and typography\n\n**Activation Triggers:**\n- UI\u002FUX review, audit, or analysis requests\n- Design system architecture and token design\n- Accessibility improvements (WCAG compliance)\n- Tailwind\u002FRadix\u002Fshadcn\u002Fui implementation\n- Responsive design and mobile-first development\n- Color system and typography design\n\n**Boundaries:**\n✅ Design systems, styling, accessibility, design tokens, UI patterns\n❌ React architecture (react-nextjs-expert), state management, backend APIs, infrastructure\n\n---\n\n**Skill Version:** 2.1.0\n**Last Updated:** 2025-11-15\n**Enhanced With:** UI\u002FUX review capabilities, design system architecture, framework-agnostic patterns\n**Authoritative Sources:** WCAG 2.1\u002F2.2, OKLCH color science, industry design systems (USWDS, Carbon, Polaris)\n**Progressive Disclosure:** Reference files for detailed guides ✅\n**Scope:** Design systems, styling, accessibility, UI\u002FUX patterns (framework-agnostic)\n**Companion Skills:** react-nextjs-expert (for React\u002FNext.js architecture and state management)\n","# UI\u002FUX Design & Development Expert\n\n**Comprehensive UI\u002FUX design, review, and improvement for modern web applications.**\n\nProduction-ready implementations with **TailwindCSS + Radix UI + shadcn\u002Fui** and modern React patterns.\n\n## Stack Architecture\n\n### The Three Pillars\n\n**Layer 1: TailwindCSS (Styling Foundation)**\n- Utility-first CSS framework with build-time generation\n- Zero runtime overhead, minimal production bundles\n- Design tokens: colors, spacing, typography, breakpoints\n- Responsive utilities and dark mode support\n\n**Layer 2: Radix UI (Behavior & Accessibility)**\n- Unstyled, accessible component primitives\n- WAI-ARIA compliant with keyboard navigation\n- Focus management and screen reader support\n- Unopinionated - full styling control\n\n**Layer 3: shadcn\u002Fui (Beautiful Components)**\n- Pre-built components = Radix primitives + Tailwind styling\n- Copy-paste distribution (you own the code)\n- Built-in React Hook Form + Zod validation\n- Customizable variants with type safety\n\n### Architecture Hierarchy\n\n```\nApplication Layer\n    ↓\nshadcn\u002Fui Components (Beautiful defaults, ready-to-use)\n    ↓\nRadix UI Primitives (Accessible behavior, unstyled)\n    ↓\nTailwindCSS Utilities (Design system, styling)\n```\n\n**Key Principle:** Each layer enhances the one below. Start with Tailwind for styling, add Radix for accessible behavior, use shadcn\u002Fui for complete components.\n\n## Core Capabilities\n\n### UI\u002FUX Review & Audit\nSystematic evaluation of existing interfaces:\n- **Component Architecture Review:** Analyze component composition, reusability, and single responsibility\n- **Accessibility Audit:** WCAG 2.1\u002F2.2 AA\u002FAAA compliance, keyboard navigation, screen reader support\n- **Performance Analysis:** Core Web Vitals (LCP, FID, CLS), bundle size, render performance\n- **Responsive Design Review:** Mobile-first implementation, breakpoint usage, container queries\n- **Design System Consistency:** Token usage, spacing scale adherence, color palette compliance\n- **Code Quality:** React best practices, hooks usage, state management patterns\n- **Visual Hierarchy:** Typography scale, spacing rhythm, color contrast, focus indicators\n\n### UI\u002FUX Design\nCreating production-ready interface designs:\n- **Component Design:** Atomic design principles, composition patterns, variant systems\n- **Layout Architecture:** Grid systems, flexbox patterns, responsive containers\n- **Interaction Design:** Hover states, focus states, loading states, error states\n- **Design Tokens:** Three-tier token system (primitive → semantic → component)\n- **Color Systems:** OKLCH color space, accessible palettes, dark mode support\n- **Typography Systems:** Scale design, hierarchy, readability optimization\n- **Animation & Transitions:** Micro-interactions, loading feedback, state changes\n\n### UI\u002FUX Improvement\nEnhancing existing implementations:\n- **Accessibility Enhancement:** ARIA patterns, semantic HTML, keyboard navigation\n- **Performance Optimization:** Code splitting, lazy loading, virtualization, image optimization\n- **Responsive Refinement:** Breakpoint optimization, mobile-first improvements\n- **Component Refactoring:** Extract shared patterns, reduce complexity, improve reusability\n- **Visual Polish:** Spacing consistency, typography refinement, color harmony\n- **State Management:** Optimistic updates, error handling, loading states\n- **Developer Experience:** Component documentation, Storybook stories, type safety\n\n### Styling Integration\nFramework-agnostic styling approaches:\n- **Tailwind with Components:** Utility-first styling for any framework\n- **CSS-in-JS:** emotion, styled-components, vanilla-extract\n- **CSS Modules:** Scoped styles without runtime overhead\n- **Design System Integration:** Token-based styling across frameworks\n\n## When to Use Each Layer\n\n### Use TailwindCSS Directly When:\n- Building custom layouts and spacing\n- Styling static content and containers\n- Rapid prototyping without complex interactions\n- Non-interactive UI elements\n\n**Example scenarios:** Hero sections, grid layouts, cards without interaction, text styling\n\n### Use Radix UI Primitives When:\n- Building custom component libraries\n- Need accessibility but require custom design\n- shadcn\u002Fui doesn't have the component you need\n- Full control over component structure required\n\n**Example scenarios:** Custom date picker, unique navigation pattern, specialized modal behavior\n\n### Use shadcn\u002Fui Components When:\n- Building standard UI components quickly\n- Need beautiful defaults with customization options\n- Enterprise application development\n- Form-heavy applications with validation\n\n**Example scenarios:** Admin dashboards, CRUD applications, settings pages, data tables\n\n## Critical Design Principles\n\n### 1. Progressive Enhancement\nStart simple, enhance as needed:\n1. Tailwind utilities for basic styling\n2. Add Radix primitives for interaction\n3. Use shadcn\u002Fui for complete solutions\n4. Customize components in your codebase\n\n### 2. Composition Over Complexity\nBuild complex UIs from simple, reusable components:\n- Small, focused components (single responsibility)\n- Compose primitives rather than creating monoliths\n- Leverage component slots and children patterns\n\n### 3. Accessibility First\nRadix UI handles accessibility automatically:\n- ARIA attributes applied correctly\n- Keyboard navigation built-in\n- Focus management and trapping\n- Screen reader compatibility\n\n**Never override accessibility features** - enhance them.\n\n### 4. Design Token Consistency\nUse Tailwind's design system consistently:\n- Stick to spacing scale (4, 8, 16, 24px)\n- Use color palette (50-950 shades)\n- Apply typography scale systematically\n- Avoid arbitrary values unless necessary\n\n### 5. Mobile-First Responsive\nAlways design mobile-first, scale up:\n- Base styles for mobile\n- Use breakpoints (sm, md, lg, xl, 2xl) to enhance\n- Test on actual devices, not just browser resize\n\n## Setup Strategy\n\n### Installation Order\n1. **TailwindCSS** - Foundation\n2. **shadcn\u002Fui CLI** - Includes Radix dependencies\n3. **Add components** - Install only what you need\n4. **Configure theme** - CSS variables + Tailwind config\n5. **Setup dark mode** - Theme provider + toggle\n\n### Configuration Best Practices\n\n**Tailwind Config:**\n- Use `content` paths correctly (scan all component files)\n- Extend theme with CSS variables, not hardcoded values\n- Enable dark mode with `class` strategy\n- Install `tailwindcss-animate` plugin\n\n**CSS Variables (Three-Tier System):**\n```css\n:root {\n  \u002F* Tier 1: Primitives (immutable) *\u002F\n  --gray-50: 250 250 250;\n  --gray-900: 24 24 27;\n  --blue-500: oklch(0.55 0.22 264);\n\n  \u002F* Tier 2: Semantics (theme-aware) *\u002F\n  --background: var(--gray-50);\n  --foreground: var(--gray-900);\n  --primary: var(--blue-500);\n\n  \u002F* Tier 3: Components *\u002F\n  --button-height: 2.5rem;\n  --card-padding: 1.5rem;\n}\n\n.dark {\n  \u002F* Only semantic tokens change *\u002F\n  --background: var(--gray-900);\n  --foreground: var(--gray-50);\n}\n```\n\n**Color Space Recommendation:**\n- **Modern**: Use OKLCH for perceptual uniformity\n- **Legacy support**: Use HSL with fallbacks\n- **Avoid**: RGB\u002FHEX for design tokens (not human-readable)\n\n**Token Storage:**\n- Store in JSON for platform-agnostic distribution\n- Transform to CSS variables, Swift, XML using Style Dictionary\n- Version control tokens separately from component code\n\n**Path Aliases:**\n- Configure `@\u002Fcomponents` and `@\u002Flib` in tsconfig\n- Ensure consistency between Next.js and TypeScript configs\n- Use aliases in imports for cleaner code\n\n## Integration Patterns\n\n### Pattern 1: shadcn\u002Fui + Custom Tailwind\nUse shadcn\u002Fui components as base, customize with Tailwind classes:\n- Apply custom spacing, colors via className prop\n- Override default styles with Tailwind utilities\n- Maintain component accessibility\n\n### Pattern 2: Radix Primitives + Tailwind\nBuild custom components from scratch:\n- Use Radix for behavior (Dialog, Dropdown, etc.)\n- Style completely with Tailwind utilities\n- Full control over structure and appearance\n\n### Pattern 3: Hybrid Approach\nModify shadcn\u002Fui components in your codebase:\n- Edit component files in `components\u002Fui\u002F`\n- Add new variants, sizes, or styles\n- Maintain type safety with CVA (Class Variance Authority)\n\n### Pattern 4: Component Composition\nCombine multiple primitives for complex UIs:\n- Popover + Select for searchable dropdown\n- Dialog + Form for modal forms\n- Tabs + Cards for multi-section interfaces\n\n## Design Token Architecture\n\nUse three-tier token system for scalable, maintainable design systems:\n- **Tier 1 (Primitive)**: Raw values (`gray-50`, `spacing-4`)\n- **Tier 2 (Semantic)**: Purpose-driven (`background-primary`, `text-error`)\n- **Tier 3 (Component)**: Component-specific (`button-height`, `card-padding`)\n\n**Modern Color:** Use OKLCH color space for perceptual uniformity and better accessibility calculations.\n\n**📖 See [DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md) for:**\n- Complete three-tier token system implementation\n- OKLCH color space guide and examples\n- Token naming conventions and best practices\n- CSS variable configuration\n- Multi-theme support patterns\n\n## Responsive Design Strategy\n\n**Mobile-first approach:** Start with mobile (0-639px), scale up through sm\u002Fmd\u002Flg\u002Fxl\u002F2xl breakpoints.\n\n**Key patterns:** Layout shifts (column→row), component switching (Dialog→Drawer), container queries for modular responsiveness.\n\n**📖 See [RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md) for:**\n- Complete breakpoint strategy and implementation\n- Responsive component patterns and examples\n- Container queries guide\n- Image optimization strategies\n- Performance considerations for responsive design\n- Comprehensive testing checklist\n\n## Form Architecture\n\n**Strategy:** React Hook Form + Zod for schema-first validation with type inference and accessible error handling.\n\n**📖 See [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md#form-architecture) for:**\n- Complete React Hook Form + Zod setup\n- Reusable field wrapper patterns\n- Multi-step form implementation\n- Accessibility requirements checklist\n\n## Performance Best Practices\n\n**Core strategies:** Code splitting (React.lazy), Tailwind optimization (accurate content paths), virtualization (@tanstack\u002Freact-virtual for long lists).\n\n**📖 See [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md) for:**\n- Complete performance optimization guide\n- Core Web Vitals optimization strategies\n- Bundle analysis and tree shaking\n- Common pitfalls and solutions\n- Performance monitoring setup\n\n## Component Customization & Dark Mode\n\n### Customization Strategies\n1. **Direct Modification**: Edit shadcn\u002Fui files in your codebase\n2. **Variant Extension**: Use CVA for type-safe variants\n3. **Wrapper Components**: Add custom logic around base components\n4. **Theme Customization**: Modify CSS variables globally\n\n### Dark Mode Setup\n1. **ThemeProvider** with next-themes\n2. **Class strategy** (`class`, not media query)\n3. **CSS variables** in `.dark` class\n4. **Accessible toggle** component\n\n**📖 See [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md) for:**\n- Complete customization strategies with examples\n- CVA variant implementation guide\n- Dark mode setup and configuration\n- Design considerations and testing\n- Form architecture patterns\n\n## Accessibility Standards\n\n### Radix UI Built-In Guarantees\n- ✅ ARIA attributes applied correctly\n- ✅ Keyboard navigation functional\n- ✅ Focus management and trapping automatic\n- ✅ Screen reader compatible\n\n### WCAG Contrast Requirements (Critical)\n\n**WCAG 2.1 Level AA (Legal Minimum):**\n- Normal text: **4.5:1** minimum contrast ratio\n- Large text (18pt\u002F14pt bold+): **3:1** minimum\n- UI components\u002Fgraphics: **3:1** minimum\n- **Industry standard**: Most legal requirements specify AA\n\n**WCAG Level AAA (Enhanced):**\n- Normal text: **7:1** contrast ratio\n- Large text: **4.5:1** contrast ratio\n- **Best practice**: Aim for AAA when design constraints allow\n\n**Measurement:**\n- Contrast ratio range: 1:1 (white on white) to 21:1 (black on white)\n- Use tools: WebAIM Color Contrast Checker, browser DevTools\n- Test during design phase, not after implementation\n\n**OKLCH Advantage:**\nPerceptually uniform color space makes contrast calculations more reliable and predictable compared to HSL.\n\n### Implementation Checklist\n- ✅ All text meets 4.5:1 minimum (AA standard)\n- ✅ Interactive elements meet 3:1 minimum\n- ✅ Provide descriptive labels (`aria-label`, `\u003Clabel>`)\n- ✅ Test complete keyboard navigation flow\n- ✅ Verify visible focus indicators (not just browser default)\n- ✅ Test with screen readers (NVDA, JAWS, VoiceOver)\n- ✅ Use semantic HTML elements (`\u003Cbutton>`, `\u003Cnav>`, `\u003Cmain>`)\n- ✅ Provide alternative text for images and icons\n- ✅ Ensure dark mode maintains contrast standards\n\n### Testing Strategy\n1. **Automated**: Use contrast checkers during design\n2. **Manual**: Tab through entire interface\n3. **Screen readers**: Test with at least one screen reader\n4. **Real users**: Include users with disabilities in testing\n\n## Common Pitfalls\n\nAvoid these frequent issues:\n1. **Dynamic classes**: Tailwind doesn't generate at runtime → use conditionals\n2. **Content config**: Verify paths include all component files\n3. **Import paths**: Check tsconfig.json aliases\n4. **Dark mode**: Ensure ThemeProvider setup and CSS variables\n5. **Accessibility**: Never remove ARIA attributes\n\n**📖 See [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md#common-pitfalls) for complete troubleshooting guide with 10+ common issues and solutions.**\n\n## Resources\n\n### Official Documentation\n- **TailwindCSS:** https:\u002F\u002Ftailwindcss.com\u002Fdocs\n- **Radix UI:** https:\u002F\u002Fwww.radix-ui.com\u002Fprimitives\n- **shadcn\u002Fui:** https:\u002F\u002Fui.shadcn.com | https:\u002F\u002Fui.shadcn.com\u002Fllms.txt\n\n### Authoritative Design System Sources\n- **USWDS Design Tokens:** https:\u002F\u002Fdesignsystem.digital.gov\u002Fdesign-tokens\u002F\n- **Smashing Magazine Naming:** https:\u002F\u002Fwww.smashingmagazine.com\u002F2024\u002F05\u002Fnaming-best-practices\u002F\n- **OKLCH Color Space:** https:\u002F\u002Fevilmartians.com\u002Fchronicles\u002Foklch-in-css-why-quit-rgb-hsl\n- **WCAG Contrast:** https:\u002F\u002Fwebaim.org\u002Farticles\u002Fcontrast\u002F\n\n### Reference Files (Detailed Guides & Patterns)\n\n**Core Concepts:**\n- **[DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md)** - Three-tier token system, OKLCH, naming\n- **[RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md)** - Breakpoints, container queries, testing\n- **[CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md)** - Component customization, dark mode, forms\n- **[PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md)** - Performance, Core Web Vitals, pitfalls\n\n**Implementation References:**\n- **[TAILWIND_REFERENCE.md](references\u002FTAILWIND_REFERENCE.md)** - Complete utilities\n- **[RADIX_REFERENCE.md](references\u002FRADIX_REFERENCE.md)** - Primitives with code\n- **[SHADCN_REFERENCE.md](references\u002FSHADCN_REFERENCE.md)** - Components with install\n- **[INTEGRATION_PATTERNS.md](references\u002FINTEGRATION_PATTERNS.md)** - Advanced patterns\n\n## Triggers & Use Cases\n\n**Activate for:** UI\u002FUX review\u002Faudit | Design system architecture | Accessibility audit (WCAG) | Design tokens (3-tier system) | Color systems (OKLCH) | Typography systems | Spacing\u002Flayout design | Tailwind\u002FRadix\u002Fshadcn\u002Fui setup | Responsive design patterns | Dark mode theming | Component library design\n\n**Do NOT activate for:** React\u002FNext.js architecture (use react-nextjs-expert) | State management | Server Components | Backend APIs | Database design | Infrastructure\u002FDevOps\n\n## Behavioral Traits\n\n**Core Philosophy:** User-centric | Performance-aware (Core Web Vitals) | Accessibility-first (WCAG AA) | Evidence-based | Maintainable | Type-safe\n\n**Design Principles:** Progressive enhancement | Mobile-first | Atomic design | Consistent tokens (3-tier) | Semantic HTML | Comprehensive error handling\n\n**Code Quality:** Component composition | Single responsibility | Proper hooks usage | Optimized rendering | Comprehensive testing\n\n## Response Approach\n\n**Review:** Understand context → Systematic audit → Identify issues → Provide evidence → Recommend solutions → Prioritize\n\n**Design:** Gather requirements → Choose architecture → Design tokens → Component structure → Implement accessibly → Include states → Responsive → Document\n\n**Improve:** Analyze current state → Identify bottlenecks → Plan improvements → Implement incrementally → Measure impact → Document → Test\n\n**Integration:** Verify compatibility → Follow official patterns → Best practices → Type safety → Performance budget → Error boundaries\n\n## Implementation Checklist\n\n**Setup:** Install Tailwind + shadcn\u002Fui | Configure three-tier tokens | Set up dark mode | Create `cn()` helper\n\n**Development:** Apply mobile-first design | Implement dark mode | Test accessibility | Verify WCAG AA contrast\n\n**Production:** Validate Tailwind purging | Test all states | Cross-browser testing | Performance audit\n\n**📖 Detailed checklists available in:**\n- [DESIGN_TOKENS.md](references\u002FDESIGN_TOKENS.md#implementation-checklist)\n- [RESPONSIVE_PATTERNS.md](references\u002FRESPONSIVE_PATTERNS.md#testing-checklist)\n- [CUSTOMIZATION.md](references\u002FCUSTOMIZATION.md#accessibility-requirements)\n- [PERFORMANCE_OPTIMIZATION.md](references\u002FPERFORMANCE_OPTIMIZATION.md#optimization-checklist)\n\n## Best Practices Summary\n\n**Design Tokens:** Three-tier system | OKLCH color space | Purpose-driven naming\n**Accessibility:** WCAG AA minimum (4.5:1 text, 3:1 UI) | Keyboard navigation | Screen readers\n**Performance:** Code splitting | Virtualization | Tailwind optimization\n**Maintenance:** Modular components | Documentation | Version control tokens\n\n## Skill Summary\n\n**Primary Functions:**\n1. **Review:** Audit UI\u002FUX for accessibility, performance, and design system consistency\n2. **Design:** Create production-ready interfaces with modern React and styling systems\n3. **Improve:** Enhance existing implementations for better UX, performance, and maintainability\n\n**Technology Focus:**\n- TailwindCSS, Radix UI, shadcn\u002Fui (styling layer)\n- Design tokens and design systems\n- Accessibility standards (WCAG 2.1\u002F2.2)\n- Responsive design and mobile-first patterns\n- Color systems (OKLCH) and typography\n\n**Activation Triggers:**\n- UI\u002FUX review, audit, or analysis requests\n- Design system architecture and token design\n- Accessibility improvements (WCAG compliance)\n- Tailwind\u002FRadix\u002Fshadcn\u002Fui implementation\n- Responsive design and mobile-first development\n- Color system and typography design\n\n**Boundaries:**\n✅ Design systems, styling, accessibility, design tokens, UI patterns\n❌ React architecture (react-nextjs-expert), state management, backend APIs, infrastructure\n\n---\n\n**Skill Version:** 2.1.0\n**Last Updated:** 2025-11-15\n**Enhanced With:** UI\u002FUX review capabilities, design system architecture, framework-agnostic patterns\n**Authoritative Sources:** WCAG 2.1\u002F2.2, OKLCH color science, industry design systems (USWDS, Carbon, Polaris)\n**Progressive Disclosure:** Reference files for detailed guides ✅\n**Scope:** Design systems, styling, accessibility, UI\u002FUX patterns (framework-agnostic)\n**Companion Skills:** react-nextjs-expert (for React\u002FNext.js architecture and state management)\n",{"name":5,"license":15,"version":24,"description":7},"2.0.0","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fsamhvw8-dot-claude\u002Fui-design-system",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill ui-design-system",{"tool":39,"command":40},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill ui-design-system",{"tool":42,"command":43},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill ui-design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamhvw8-dot-claude\u002Fui-design-system\u002FSkill.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"metadata.json","REFERENCE","参考文档",439,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fsamhvw8-dot-claude\u002Fui-design-system\u002Fmetadata.json",[54,61,66,73,78,85],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":62,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":74,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":86,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]