'design-system' 검색 결과

Convert long Markdown specifications, reports, and plans into a single HTML document with a sticky table of contents, search, section tracking, and code-copy buttons. Apply previously configured brand colors and layout styles.

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

• Turn long specifications into navigable HTML documents
• Add search and a table of contents to reports
• Apply consistent brand styling to technical documents

Review a design system for inconsistent names and hardcoded visual values, document component variants and accessibility behavior, or propose new interface patterns that follow existing rules. Produce structured audits, component references, and design proposals.

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

• Auditing component names and visual consistency
• Documenting component variants and states
• Recording keyboard and screen reader behavior

Turn long Markdown files into a single HTML file for reading, reviewing code, or presenting slides. Routes each input to a specialized converter and applies shared design settings, with navigation and interaction suited to the document type.

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

• Converting long specifications or reports into navigable HTML
• Presenting code reviews with diffs and severity annotations
• Turning Markdown into slides with keyboard navigation

Review a design system for inconsistent names and hardcoded visual values, document component variants and accessibility behavior, or propose new interface patterns that follow existing rules. Produce structured audits, component references, and design proposals.

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

• Auditing component names and visual consistency
• Documenting component variants and states
• Recording keyboard and screen reader behavior

Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).

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

Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).

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

Link Figma design components with their code counterparts through Code Connect, helping design-system updates flow into the codebase. This catalogue entry points agents toward the full upstream workflow.

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

• Linking Figma components to code components
• Reflecting design-system updates in code
• Introducing a Code Connect workflow

Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use `design-system-governance` (design-systems).

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

Roast the current repo's design system with real data. Runs a deterministic scanner (no tokens, ~1s) that counts everything that betrays a design system, from colours and their near-identical twins to greys, spacing values, typefaces, duplicated and never-imported components, inline styles, !important and arbitrary Tailwind values, and compares them against Ideal Design System norms, a benchmark of 119 public repos (a 34-repo core fleet plus groups for shadcn, Tailwind, MUI, Mantine, Chakra, Ant Design and web components) and 10 reputable design systems, generates a shareable HTML diagnosis, and can generate design-system-rules.md, the agent rules file that stops the mess regrowing.

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

Reviews existing UI components for design-system consistency, states, responsiveness and accessibility using consumer-owned context. Use when asked to review component quality, check design-system adherence or audit component consistency.

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

Create, list, and apply Stitch design systems from DESIGN.md using the verified Stitch MCP design-system tools and safe upload fallbacks.

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

Create a blank Figma Design or FigJam file as the starting point for agent workflows. Use it to prepare a new workspace before building a design system or organizing workshop activities.

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

• Starting a blank Figma Design file
• Preparing a FigJam file for a workshop
• Beginning a scripted design-system workflow

Run scripts through the Figma Plugin API, an interface for operating on designs. Use it to write to the canvas, inspect content, work with variables, and carry out design-system tasks.

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

• Writing to the Figma canvas with scripts
• Inspecting Figma canvas content
• Working with variables and design systems

Review web page headings for skipped levels, unclear labels, and incorrect structure. Organize HTML headings around the content so people using screen readers can understand page sections and navigate between them.

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

• Audit heading levels on a web page
• Improve navigation for screen reader users
• Review headings in design-system patterns

Review whether ARIA roles, which describe interface elements to assistive technology, have the required parent roles. Find misplaced menu items, tabs, or list items, suggest suitable containers, and explain how to verify the corrected structure.

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

• Checking parent roles for menu items
• Reviewing tab and list structures
• Auditing design-system components

Turn a Markdown slide deck into a single HTML file for browser presentations. Navigate with the keyboard, view speaker notes and the next slide in presenter mode, and print the deck as a PDF with one slide per page.

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

• Converting Markdown notes into browser slides
• Presenting with speaker notes and a next-slide preview
• Exporting a deck as a PDF with one slide per page

Set shared brand colors, fonts, layout style, and table of contents behavior for markdown-html outputs. A guided setup checks text and link contrast, derives twelve reusable CSS settings, and saves preferences globally or per project.

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

• Setting a shared style for HTML documents and slides
• Checking text and link color contrast
• Saving a separate brand style for a project

Create project-specific rules for turning Figma designs into code. The skill examines existing components and styling, then saves conventions for naming, file locations, reusable design values, and implementation steps in the coding agent's rule file.

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

• Setting up Figma implementation rules for a new project
• Teaching an AI agent existing component conventions
• Standardizing Figma implementation across a team

Write a game design document for one system, such as combat, crafting, or dialogue. Work through sections with specialist agent input, check dependencies against existing designs, and save approved sections with progress records for later continuation.

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

• Writing a combat or crafting system design
• Checking dependencies against existing game designs
• Developing specifications with specialist agent input

Build and update Kortix web screens with established interface components and reference layouts. Guides component selection for forms, lists, modals, loading states, and notifications, including replacements for deprecated components and consistent responsive page structure.

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

• Build a settings screen with existing components
• Replace deprecated interface components
• Standardize loading, empty, and error states

Apply Carapace styling to existing OpenClaw interfaces through shared CSS, themes, and semantic tokens—named values for visual roles. Reuse existing components and check interaction states, accessibility, and browser screenshots for consistent presentation.

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

• Align existing OpenClaw screens with Carapace styling
• Reuse shared CSS and existing interface components
• Review focus states, status colors, and accessible names

Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use `design-system-adoption` (designer-toolkit); for design file history use `version-control-strategy` (design-ops).

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

Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use `design-system-governance` (design-systems).

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

Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when creating or organizing theme files and design tokens (theme.ts / theme/), extending an existing theme or styling library (NativeWind, Tamagui, Restyle, Unistyles) in its own idiom, standardizing styles so screens (including AI-generated ones) look consistent and polished, fixing an app that looks AI-generated or generic instead of native (the named native-slop tells), building an in-app component library, or auditing an app for design-system drift (hardcoded colors, spacing, fonts). For platform styling specifics (semantic colors, HIG rules, native controls) use expo-native-ui; for folder layout of a new app use expo-project-structure.

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