스킬 찾기

Critique a rendered screen against mood.md, voice.md, and tokens.md. Use when those brand files exist and you are checking compliance. For defining the visual language itself, use `illustration-style` (ui-design).

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

Critique a rendered screen's density — cognitive load, content prioritisation, scanning patterns, and progressive disclosure. Use when a screen feels overwhelming. For the underlying choice-count principle, use `hicks-law` (interaction-design).

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

Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design).

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

Critique a rendered screen's affordances — what looks clickable, state visibility, CTA clarity, and action discoverability. Use when reviewing an existing screen. For sizing and positioning targets in new work, use `fitts-law` (interaction-design).

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

Identify, score, and prioritise design opportunities against impact and effort. Use when there are more ideas than capacity. For framing the one you choose, use `design-brief`.

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

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).

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

Build alignment artifacts — responsibility matrices, decision rights, and communication plans. Use when unclear ownership stalls decisions. For persuading in the moment, use `design-negotiation` (designer-toolkit).

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

Articulate a long-horizon product vision that aligns teams and anchors strategy. Use when direction is contested or absent. For near-term project scope, use `design-brief`.

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

Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`.

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

Critique a rendered screen's colour — contrast ratios, palette coherence, and semantic meaning. Use when reviewing one screen. For a product-wide WCAG audit use `accessibility-audit` (design-systems); for building the palette use `color-system` (ui-design).

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

Critique a rendered screen's composition — balance, whitespace, rhythm, and gestalt grouping. Use when a layout feels off but hierarchy is fine. For emphasis and eye flow specifically, use `critique-visual-hierarchy`.

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

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

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

Select chart types and design data encodings — marks, axes, labels, and accessible chart styling. Use when presenting data graphically. Owns chart selection and encoding only; the categorical colour ramp itself belongs to `color-system`.

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

Define a responsive grid — columns, gutters, margins, and breakpoint behaviour. Use when establishing page structure. For the spacing scale inside components use `spacing-system`; for cross-device behaviour use `responsive-design`.

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

Choose between competing concepts against criteria fixed in advance, and record what each rejected concept was testing. Use when several directions are alive and one has to win. For picking which problem to work on, use `opportunity-framework` (ux-strategy); for deciding by production traffic, use `a-b-test-design`.

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

Run an expert review against Nielsen's heuristics and domain criteria, with severity ratings. Use when you need findings without recruiting participants. For a facilitated team feedback session, use `design-critique` (design-ops).

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

Write realistic usability task scenarios with success criteria and facilitation notes. Use when you have a study and need the tasks. For the surrounding study design, use `usability-test-plan` (design-research).

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

Apply the Law of Closure — the eye completes implied shapes from partial forms. Use when reducing visual weight by dropping borders or letting negative space suggest structure. For explicit containers, use `law-of-common-region`.

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

Build a product colour system — tonal scales, semantic roles, and contrast compliance. Use when defining or rebuilding colour from scratch. For dark-mode adaptation use `dark-mode-design`; for chart palettes use `data-visualization`; for multi-brand token architecture use `theming-system` (design-systems).

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

Create a spacing scale from a base unit with rules for when each step applies. Use when standardising padding and margins. For page-level columns and gutters, use `layout-grid`.

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

Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use `zeigarnik-effect`.

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

Apply an emotional resonance lens to a UI that is technically correct but flat, prescribing changes at the copy, motion, and interaction layer. Use when a design tests fine but lands cold. For the polish-perception argument, use `aesthetic-usability` (ui-design).

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

Define UX metrics and KPIs that connect design decisions to measurable outcomes. Use when choosing what to measure. For presenting the results afterwards, use `design-impact-reporting` (design-ops).

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

Choose prototype fidelity and method to match the design question and the decision at stake. Use before building a prototype. For what to test once it exists, use `test-scenario`.

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