'design-system' 검색 결과

Build or audit a design system including component library, design tokens, naming conventions, contribution model, and documentation. Use this skill whenever the user wants to build a design system, audit an existing system, define design tokens at the system level, structure a component library, or set up design system governance. Triggers on design system, component library, design tokens, atomic design, atoms, molecules, organisms, design system documentation, Storybook, Figma library, system governance, design contribution model. Also triggers when teams are inconsistent across products and a system is the answer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product design across UI/UX, design systems, prototyping, and user research. Use when creating user journey maps, building wireframes, defining design tokens and component systems, planning usability tests, or establishing design principles.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design tokens, light/dark theming, and WCAG contrast validation for HTML documents and decks, compiled into one inlinable CSS bundle. Use when theming a report or deck, auditing contrast, or fixing dark-mode color drift.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to write and maintain DESIGN.md as the visual specification layer for Cavekit projects. Nine-section format, design tokens, accessibility, integration with kits/plans. Use when defining or revising visual identity, importing a third-party design system, or auditing UI code against design tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Game Design Document authoring guide (8-section GDD format)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Classify a console screen (list/record/form), build it on @temps-sdk/ds templates and the shared shadcn primitives in @temps-sdk/ui, and follow the console's status vocabulary and status colour rules. Use for any new or changed console UI in web/src, and when building or extending web/packages/ds itself.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

UI/UX design-system intelligence - 84 styles, 192 palettes, 74 font pairings, 25 charts, 99 UX guidelines across 22 stacks (searchable dataset + CLI). Internal genjutsu module: loaded by /genjutsu:cast and /genjutsu:paint, not invoked directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforce Design Language System adherence in Flutter. Use when implementing design tokens, preventing hardcoded colors/spacing, or building a DLS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforce design token usage in SwiftUI apps using iOS Human Interface Guidelines. Use when implementing design tokens, colors, or typography in SwiftUI.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize Android strings, drawables, fonts, themes, localization, and concrete resource-backed Compose values such as MaterialTheme colors. Use for resource declarations and their direct UI lookup; defer design-system token architecture, network image loading, lint-rule configuration, and general Compose implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate design systems with color palettes, typography, spacing scales, component tokens, and Tailwind config

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract design tokens, text styles, and variables from a Figma design system and produce a design-tokens.json plus ready-to-use QML singletons. Use this skill whenever someone wants to pull their design system out of Figma — whether they say "export tokens from Figma", "get design tokens", "set up my design system", "read our Figma design system", "get Figma variables into QML", "pull our color palette from Figma", "import design tokens", "extract colors/typography/spacing from Figma", or similar. Trigger this skill at the start of any design-system workflow that involves a Figma source.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Extract component metadata from a Figma design system and generate production-ready QML controls. Use this skill whenever someone wants to turn Figma components into QML files — whether they say "generate components from Figma", "create QML controls based on a design system", "convert Figma components to QML", "build the component library", "extract button/input/checkbox from Figma", or anything similar. Requires design-tokens.json and QML design system singletons to already exist (from the token extraction skill). Uses Figma MCP to inspect components one at a time and maps variants, states, sizing, and token usage to idiomatic Qt Quick Controls 2 patterns. Trigger this skill at the component generation step of any QML design-system workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build scalable design systems with design tokens, theming infrastructure, and component architecture patterns. Use when creating design tokens, implementing theme switching, building component libraries, or establishing design system foundations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create design systems with tokens, components, and documentation. Use when building design systems, creating component libraries, or establishing design tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate a complete, premium design system from a brand brief or an existing site — color tokens, type scale, spacing/radius/elevation, motion language, and component specs — exported as Tailwind config, CSS variables, and a usage doc. Built to look editorial and human-crafted, not template-generated. Use when starting a new product/site, unifying an inconsistent UI, or codifying a brand into reusable tokens.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Skill for creating and managing a Design System using Tailwind CSS and shadcn/ui. Use when defining design tokens, setting up theming with CSS variables, building a consistent UI component library, initializing a design system configuration, or wrapping shadcn/ui components into design system primitives.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Autonomous Principal Design Technologist. Cures vibe-coded software from AI frontend slop using curated token archetypes and 7-axis quality gating.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Writes and reviews composables for Compose and CMP: the Route/Screen/leaf split, state-read placement and stability, loading/empty/error UX states, LazyColumn lists and grids, animation choice, accessibility and semantics, design-system tokens, CMP Res resources, Coil images, and keyboard/focus. Use when touching @Composable code, recomposition, stability, LazyColumn, animation, shimmer or skeleton, accessibility, theme, colors, Res.string, Coil, focus, or keyboard. Do NOT use for MVI, error tiers, or module graph (compose-architecture), ViewModel or data work (compose-feature, compose-data), Gradle or module work (compose-project), or expect/actual splits (compose-platform).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, edit, replicate, import, and export draw.io diagrams with an offline YAML-first workflow: architecture, network topologies, flowcharts, UML/ER, org charts, Mermaid/CSV conversion, existing .drawio bundles, style presets, themes, and non-publication formula diagrams. For publication figures (paper, thesis, IEEE, camera-ready) use drawio-academic-skills instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when creating or maintaining UI design systems, design tokens, component documentation, responsive calculations, quality checks, or design-dev handoff materials.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.