'design' 검색 결과

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

Review a design against Dieter Rams' ten principles using evidence from code, screenshots, copy, and measurements. Receive a scorecard, a verdict on whether to create, refine, or redesign, and a prompt for planning the next steps.

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

• Audit a UI against Dieter Rams' ten principles
• Decide whether to refine or redesign a screen
• Check interface wording and usability with evidence

Turn Figma designs into screen code that fits an existing project. The workflow reuses existing components and shared style values, follows design notes, and uses exported images and icons to preserve the design’s appearance.

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

• Implement a screen from a Figma design
• Reuse existing components when building a design
• Reproduce images and icons from exported assets

Extract a design system from a screenshot (PNG/JPG/WEBP) or a live URL and produce a schema-compliant `design.v1.json` file plus a ready-to-use agent prompt for applying the design to any website/app. When run inside the sleek-ui repository, offers to add the extracted design to the public catalog as a PR — updating `public/designs/`, `src/data/designs/`, `src/data/designs.ts`, and generating a preview. Use when users ask to "extract a design from this screenshot", "clone this site's design", "reverse-engineer the design tokens", "reskin my app to look like {site}", "generate a sleek-ui design from this URL", or provide an image/URL and want a reusable design system.

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

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).

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

URL・画像・テキスト要件からAIコーディングエージェント向けのDESIGN.mdを生成するスキル。「example.comをDESIGN.md化して」「このサムネをDESIGN.md化して」「クールでポップなLP用のDESIGN.mdを作って」といったリクエストで使用する。Claude Code / Cursor / Stitch に渡せば一貫したUIを生成できる、getdesign.md / awesome-design-md 準拠の9セクション構成のデザイン仕様書を出力する。CSS解析・画像目視抽出・要件生成の3パターンに対応。

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

直近N日（デフォルト1日）にマージされた `cc-ui-design` ラベル付きPR（UIデザインPR）から確定したビジュアルアイデンティティ（カラー・タイポグラフィ・スペーシング・コンポーネント）をリポジトリルートの `DESIGN.md`（google-labs-code/design.md フォーマット）へ集約・更新し、`design.md` CLI の lint を通してから commit-push + create-pr でPRを作成する（`cc-triage-scope` ラベル + 自分自身をAssignee）。`DESIGN.md` は pencil-design-updater がデザイン時の前提として読み込む。

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

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).

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

Builds and maintains a DESIGN.md brief from existing screens, documentation, and components. It records product goals, visual rules, accessibility, and implementation constraints so future interface decisions have a shared reference.

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

• Documenting shared rules for interface design
• Preparing a design brief before implementation
• Reconciling existing screens, assets, and design constraints

Create and update shared design rules in Stitch, including colors, fonts, and corner shapes, then apply them to existing screens. Keep a DESIGN.md file and project metadata alongside the design system.

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

• Apply shared design rules across existing screens
• Turn a theme description into concrete design values
• Create or update a design system in Stitch

Analyze existing Stitch screens and document their colors, typography, components, and layout in DESIGN.md. The resulting design reference combines plain visual descriptions with precise color values to guide requests for new screens.

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

• Document design rules from an existing screen
• Prepare a design reference for new screen prompts
• Record color codes and their functional roles

Designing anatomically plausible, visually distinctive creatures that communicate threat, personality, and role through form - from terrifying bosses to collectible companionsUse when "creature design, design a creature, design a monster, monster design, boss design, enemy creature, companion creature, pet design, wildlife design, alien creature, fantasy creature, horror monster, cute creature, pokemon style, creature anatomy, creature silhouette, creature movement, hybrid animal, ecosystem creatures, creature family, mount design, dragon design, beast design, creature, monster, boss, enemy, companion, wildlife, horror, cute, pokemon, anatomy, silhouette, locomotion, ecosystem, hybrid, fantasy, sci-fi, kaiju, cryptid" mentioned.

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

Builds comprehensive design systems and design bibles with production-ready CSS. Expert in design tokens, component libraries, CSS architecture. Use for design system creation, token architecture, component documentation, style guide generation. Activate on "design system", "design tokens", "CSS architecture", "component library", "style guide", "design bible". NOT for typography deep-dives (use typography-expert), color theory mathematics (use color-theory-palette-harmony-expert), brand identity strategy (use web-design-expert), or actual UI implementation (use web-design-expert or native-app-designer).

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

要件定義と実装の間を埋める技術仕様書を体系的に作成するスキル。 画面設計、API設計、DB設計、シーケンス図、状態遷移図をMermaid形式で生成し、 IEEE 830/ISO 29148準拠の仕様書を出力する。Use when creating functional specifications, API design documents, database design documents, screen design specifications, or sequence/state diagrams from requirements. Triggers: "technical specification", "functional spec", "API design", "database design", "screen design", "画面設計書", "API設計書", "DB設計書", "技術仕様書", "シーケンス図", "状態遷移図"

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

Builds comprehensive design systems and design bibles with production-ready CSS. Expert in design tokens, component libraries, CSS architecture. Use for design system creation, token architecture, component documentation, style guide generation. Activate on "design system", "design tokens", "CSS architecture", "component library", "style guide", "design bible". NOT for typography deep-dives (use typography-expert), color theory mathematics (use color-theory-palette-harmony-expert), brand identity strategy (use web-design-expert), or actual UI implementation (use web-design-expert or native-app-designer).

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

기존 코드에서 색상·글꼴·여백 등의 공통 규칙을 추출하고 디자인 명세와 미리보기를 만듭니다. 화면의 일관성을 열 가지 항목으로 평가하고 수정할 위치도 제시합니다.

• 기존 코드에서 디자인 규칙을 추출합니다
• 개편 전에 화면의 일관성을 점검합니다
• 스타일을 변경하는 PR을 검토합니다

Review an iOS app’s appearance on a real iPhone using screenshots, Apple’s interface guidelines, and project design rules. Get scores for each design dimension and explanations of what would improve them.

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

• Reviewing an iOS app’s visuals on a real iPhone
• Checking screens against project design rules
• Identifying improvements from design scores

Use a minimal community plugin example to validate OpenDesign marketplace workflows. It serves as a small test case for registry search, installation, and provenance checks that establish where a plugin comes from.

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

• Validating plugin search in OpenDesign
• Checking marketplace installation flows
• Testing how plugin origins are verified

Design new web pages, review existing interfaces, or analyze references from URLs and screenshots. The skill guides page structure, colors, typography, and interaction states while respecting an existing project's design system and implementation boundaries.

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

• Designing a new landing page
• Prioritizing improvements to an existing interface
• Analyzing a reference page or screenshot

Generate a DESIGN.md file for Google Stitch that defines colors, typography, layouts, component states, and motion. Clear descriptions and exact values give the screen-generation agent a shared reference, including explicit rules against generic design patterns.

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

• Defining shared design rules for Google Stitch screens
• Documenting colors, typography, and component behavior
• Specifying mobile layouts and animation rules

Turn a design request into a concrete specification covering colors, fonts, layout, mood, spacing, and constraints. Generate DESIGN.md and an HTML preview, with a clear report of defaults applied to unspecified choices.

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

• Clarifying vague visual requirements before implementation
• Defining colors, fonts, and spacing for a landing page
• Reviewing design choices through an HTML preview

Update Ant Design projects, mainly from v4 to v5, by reviewing changed component APIs, replacing removed features, and migrating theme settings. The skill also guides use of the official tool for automated code changes.

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

• Upgrading an Ant Design project from v4 to v5
• Replacing removed components and deprecated properties
• Migrating Less theme settings to theme tokens

Updates an Ant Design Pro project by comparing it with the latest official template. It merges dependency and configuration changes while preserving custom pages and business logic, then checks for deprecated APIs and build errors.

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

• Update an existing Ant Design Pro project
• Merge template changes while preserving custom code
• Check deprecated APIs during an upgrade

Helps build and maintain Ant Design interfaces by checking component options, examples, and theme settings. It also supports debugging, version migrations, and project scans to identify deprecated code and configuration issues.

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

• Build interfaces using component APIs and working examples
• Investigate component bugs and configuration issues
• Check changes before upgrading Ant Design