Search: "design system"
Showing 15 of 15 results
Design System
Build design systems with tokens, components, and documentation that scale across teams and products.
Tailwind Design System
Build scalable, themable Tailwind CSS component libraries using CVA for variants, compound components, design tokens, dark mode, and responsive grids.
System Design
Deep system design workflow—requirements, capacity, APIs, data, consistency, failure modes, trade-offs, and evolution. Use when preparing interviews, RFCs, g...
Minimalist Design System
专家级前端架构师与UI/UX设计系统集成指南。极简现代主义设计系统，帮助将精密设计系统无缝集成到现有代码库。适用于：前端组件开发、UI设计实现、设计令牌配置、Tailwind CSS定制、响应式布局、动效设计、无障碍优化。触发场景：用户需要实现极简现代风格UI、配置设计令牌、创建组件库、优化视觉一致性。
Design System Creation
Complete workflow for creating distinctive design systems from scratch. Orchestrates aesthetic documentation, token architecture, components, and motion. Use when starting a new design system or refactoring an existing one. Triggers on create design system, design tokens, design system setup, visual identity, theming.
ui-design-system
UI 视觉设计系统——配色主题（10预设+自定义生成）+ 美学变体（soft/minimalist/brutalist）+ 协同选择流程
Design System Hub
Create and operate a local Design System Hub that stores multiple design systems, generates complete entries from screenshots, URLs, or written style descriptions, and exposes browsable documentation, live mocks, copied tokens, DESIGN.md, standalone HTML, and JSON APIs. Use when the user asks to ini
edic-design-system
Generate UI components, full pages, documents, emails, and assets that strictly follow the EDIC design system (Editorial × Olive Green, OKLch tokens, dark-mode ready, CJK-optimized). Use this skill whenever the user asks to build, style, or refactor anything for EDIC, or explicitly requests the EDIC / "editorial olive" design system. Output token-driven, accessible, framework-agnostic HTML/CSS.
perception-design-system
A perception-driven product experience design methodology: 四层感知强度 × 四维度矩阵 + MustBe/NotToBe 约束 + 认知心理学底座. 适用于金融、电商、SaaS、工具类等任何软件产品的体验设计.
design-system-governance
# Design System Governance You are an expert in the operational and organizational structures that keep a design system healthy over time. ## What You Do You define the processes, roles, and decision frameworks that allow a design system to evolve without fragmenting — so contributors know how to participate, consumers know how to depend on it, and the system stays coherent as the product scales. ## Core Governance Questions A governance model must answer: 1. **Who owns the system?** Dedicated team, federat
design-system-adoption
# Design System Adoption You are an expert in driving design system adoption across design and engineering teams. ## What You Do You create strategies and materials that help teams adopt and consistently use a design system. ## Adoption Strategy ### Awareness - Launch announcements and demos - Documentation site with search and examples - Regular updates and changelog communication - Showcase projects that use the system well ### Education - Getting started guides for designers and developers - Component us
agent-arch-system-design
--- name: "system-architect" description: "Expert agent for system architecture design, patterns, and high-level technical decisions" type: "architecture" color: "purple" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "System design, architectural patterns, scalability planning" complexity: "complex" autonomous: false # Requires human approval for major decisions triggers: keywords: - "architecture" - "system design" - "scalability" - "microservices" - "design pattern
figma-create-design-system-rules
# Create Design System Rules ## Overview This skill helps you generate custom design system rules tailored to your project's specific needs. These rules guide AI coding agents to produce consistent, high-quality code when implementing Figma designs, ensuring that your team's conventions, component patterns, and architectural decisions are followed automatically. ### Supported Rule Files | Agent | Rule File | |-------|-----------| | Claude Code | `CLAUDE.md` | | Codex CLI | `AGENTS.md` | | Cursor | `.cursor/
expo-design-system
# Expo Design Systems Make every screen in an app draw from one visual source of truth: a token theme and a small set of reusable components. This skill defines where tokens live, what they cover, how reusable components are shaped, and when a repeated view earns promotion into the system. Sibling skills own the layers around this one: - `expo-native-ui` - platform styling rules (HIG, semantic colors, controls, shadows syntax). Follow it for **what values look native**; follow this skill for **where values
design-system-patterns
# Design System Patterns Master design system architecture to create consistent, maintainable, and scalable UI foundations across web and mobile applications. ## When to Use This Skill - Creating design tokens for colors, typography, spacing, and shadows - Implementing light/dark theme switching with CSS custom properties - Building multi-brand theming systems - Architecting component libraries with consistent APIs - Establishing design-to-code workflows with Figma tokens - Creating semantic token hierarchi