スキルを探す

Write clear design rationale connecting decisions to user needs, business goals, and principles.

日本語の概要は準備中です。原文の説明を表示しています。

Define a set of actionable design principles that guide decision-making and resolve trade-offs.

日本語の概要は準備中です。原文の説明を表示しています。

Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.

日本語の概要は準備中です。原文の説明を表示しています。

Critique a screen's typography — scale usage, readability, consistency, and token compliance.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct a structured competitive analysis comparing UX patterns, features, strengths, and gaps across rival products.

日本語の概要は準備中です。原文の説明を表示しています。

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Balance visual design with ATS compatibility for creative roles

日本語の概要は準備中です。原文の説明を表示しています。

Facilitate structured design critiques with clear feedback frameworks and actionable outcomes.

日本語の概要は準備中です。原文の説明を表示しています。

Design effective dark mode interfaces with proper color adaptation, contrast, and elevation.

日本語の概要は準備中です。原文の説明を表示しています。

A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.

日本語の概要は準備中です。原文の説明を表示しています。

Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

日本語の概要は準備中です。原文の説明を表示しています。

Apply animation principles to UI motion for purposeful, polished interactions.

日本語の概要は準備中です。原文の説明を表示しています。

Use when asked about harness9 architecture, module design, or how components interact — explains the system design

日本語の概要は準備中です。原文の説明を表示しています。

Use when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.

日本語の概要は準備中です。原文の説明を表示しています。

Use when assessing the architectural health of a codebase — before a major refactor, when onboarding to an unfamiliar repo, after rapid growth, when planning a redesign, or to surface structural strengths and risks before they become expensive. Not for fixing what it finds, and not for reviewing a branch diff.

日本語の概要は準備中です。原文の説明を表示しています。

TRIGGER when: user asks to draw, illustrate, or visualize any process, structure, or concept — "画个流程图", "draw an architecture diagram", "帮我画个对比图", "visualize this process", "make a diagram for this doc", or mentions 流程图/架构图/示意图/对比图/时序图/泳道图/时间线. Also trigger when user provides a document/article and asks for illustrations or diagrams. DO NOT trigger for: chart/plot requests (bar charts, line graphs — those need a charting library, not draw.io), or artistic image requests (logos, mascots, drawings of objects/people — those need an image tool).

日本語の概要は準備中です。原文の説明を表示しています。

Migrates Vendure Admin UI extensions (legacy Angular-based) to the new React Dashboard.

日本語の概要は準備中です。原文の説明を表示しています。

Decision guide for antd 6.x, Ant Design Pro 5/ProComponents, Ant Design X v2, and the offline `@ant-design/cli`. Use for component selection, theming/tokens, SSR, a11y, performance, routing/access/CRUD, AI/chat UI patterns, local API lookup, debugging, migration, and usage analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.

日本語の概要は準備中です。原文の説明を表示しています。

Derive a full UI palette from one or two brand colours — state variants, brand-tinted greys, semantic colours. Use when building or expanding a colour system.

日本語の概要は準備中です。原文の説明を表示しています。

Size, colour, weight and position mark what matters most. Use when designing button groups, CTAs, cards, dashboards or any layout with a primary action.

日本語の概要は準備中です。原文の説明を表示しています。

Guided multi-step paths and wizards. Use when designing onboarding, checkout, setup sequences or any multi-step journey.

日本語の概要は準備中です。原文の説明を表示しています。

Modals, drawers, bottom sheets and popovers, each with its scope and blocking level. Use when designing dialogs, confirmations, side panels or action sheets.

日本語の概要は準備中です。原文の説明を表示しています。