디자인 스킬

Design confirmations, status messages, and notifications that help users understand whether an action registered and what happens next. Choose suitable placement, timing, and feedback channels, with undo options and accessible cues where appropriate.

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

• Design confirmation messages after saving
• Make button and toggle responses clear
• Organize upload and sync status indicators

Write clear interface text for buttons, forms, errors, empty screens, and onboarding. This skill helps explain what happened and what to do next, while keeping language consistent with the product’s voice and appropriate to each situation.

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

• Rewrite button and form labels
• Explain errors and the next action
• Guide users through empty screens

Audit accumulated design inconsistencies across a product, including visual differences, navigation problems, accessibility gaps, and outdated documentation. Classify issues by severity, frequency, and repair effort, then create a prioritized improvement plan and an ongoing issue register.

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

• Inventory inconsistencies before a major redesign
• Prioritize design fixes within limited capacity
• Review navigation after repeated feature additions

Design interfaces for multiple languages and regions by accounting for longer text, right-to-left reading, typography, cultural differences, and local formats. Get practical guidance for flexible layouts and reusable components that accommodate these variations.

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

• Reviewing layouts for longer translated text
• Planning interfaces for right-to-left languages
• Checking regional date and currency formats

Plan how teams will adopt an existing design system, a shared set of design components and guidelines. Develop onboarding materials, migration support, and measures of usage while addressing barriers faced by designers and developers.

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

• Planning adoption of an underused design system
• Preparing getting started guides and workshops
• Supporting migration from older design patterns

Map what people want to accomplish with a product, including practical tasks, desired feelings, and how they want others to see them. Connect these motivations to expected outcomes, current solutions, and opportunities for design improvements.

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

• Understand motivations behind product use
• Reconsider feature decisions around user goals
• Find needs that current solutions do not meet

Turn design results into reports that connect user behavior, product performance, and business value. Organize metrics and qualitative evidence into scorecards, before-and-after cases, or annual summaries, while acknowledging other factors that may have influenced results.

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

• Quarterly reports on design outcomes
• Before-and-after summaries of a redesign
• Reporting results from A/B tests

Create specifications for a consistent icon system. Define grids, sizes, stroke weights, styles, naming, categories, delivery formats, and accessibility requirements, along with maintenance practices for managing icons as the design system grows.

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

• Standardize icon sizes and stroke weights
• Define icon names and categories
• Plan SVG and component delivery

Turn a design project into a portfolio case study for an external audience. Organize the challenge, process, solution, and results into a clear story, supported by evidence of key decisions and your individual contribution.

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

• Writing a portfolio case study
• Explaining your contribution to a team project
• Showing design decisions through process evidence

Design how a product prevents, detects, explains, and recovers from errors across multiple user flows. Plan clear messages, suitable placement, preserved input, retries, and alternative paths that help users understand problems and continue their work.

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

• Designing recovery from network failures
• Rewriting error messages with clear next steps
• Preserving entered data after an error

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

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

• Tune how a modal enters and exits
• Adjust button and toggle animations
• Coordinate the order of related movements

Design a theme system so one component library can support multiple brands, light and dark modes, and spacing densities. Organize reusable design values into layers, define theme overrides, and plan switching behavior and component checks.

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

• Sharing a component library across multiple brands
• Planning light, dark, and high-contrast themes
• Organizing shared and theme-specific design values

Define shared design values for colors, spacing, typography, shadows, borders, and motion. Organize these reusable values into raw, purpose-based, and component-specific layers, with naming conventions and usage documentation to support consistent interface design.

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

• Define shared colors and spacing values
• Separate raw values from purpose-based names
• Document token naming and usage rules

Plan and facilitate a design sprint that moves a team from a defined challenge to a tested prototype in days. Organize daily activities, roles, preparation, user interviews, and follow-up, with shorter and remote variations.

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

• Planning a five-day sprint from challenge to user testing
• Compressing a smaller challenge into a two- or three-day sprint
• Adapting sprint activities for a distributed team

Turn interviews, surveys, and other research into two to four user personas: representative profiles based on behavior patterns. Describe their goals, frustrations, and needs, prioritize a primary persona, and explain implications for product design.

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

• Creating personas from user research
• Sharing a consistent user reference across a team
• Choosing the primary persona for design decisions

Design conversations for voice assistants and text chatbots. Map prompts, responses, confirmations, and recovery from misunderstood or missing input, while defining a consistent tone and clear ways to stop, restart, or reach a person.

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

• Planning dialogue flows for voice assistants
• Improving chatbot recovery from misunderstood input
• Defining an assistant's persona and tone

Define rules for maintaining a shared design system across teams. Clarify ownership, contribution reviews, release numbering, and how to retire components, giving contributors and users a clear process for managing changes.

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

• Clarifying ownership across design teams
• Defining component contribution and review steps
• Planning breaking changes and migration support

Map one target user's experience from start to finish, showing goals, actions, touchpoints, emotions, and difficulties at each stage. Identify critical moments and rank design opportunities by their likely impact and feasibility.

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

• Mapping the current experience for one target user
• Finding stages where users feel frustrated
• Prioritizing improvements by impact and feasibility

Assess perceived interface speed using 400ms as a response-time target. Set timing budgets for common interactions and plan immediate feedback, loading indicators, or progress displays when completion takes longer, helping users understand what is happening.

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

• Investigating delays in search and filtering
• Setting timing targets for screen transitions
• Designing feedback for slow operations

Create consistent naming rules for components, layers, files, and design tokens—named values used in a design system. Use structured patterns and examples to make names easier to predict, search, and maintain as the system grows.

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

• Standardizing component and layer names
• Defining naming patterns for design tokens
• Organizing file and asset names

Design swipe, drag, long-press, and other touch or pointer interactions with clear hints and feedback. Define activation thresholds, resolve conflicting gestures, and provide button or menu alternatives so essential actions remain accessible.

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

• Designing swipe and drag interactions
• Adding hints for unfamiliar gestures
• Resolving scrolling and swiping conflicts

Structure a team design critique with shared context, clear feedback rules, and a guided discussion. Turn observations and suggestions into documented decisions and action items with owners and deadlines, grounded in project goals and user needs.

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

• Planning a structured team design critique
• Setting constructive feedback rules
• Turning review feedback into assigned actions

Create a design handoff document for developers, covering dimensions, interactions, content rules, assets, and exceptional cases. Specify responsive behavior, accessibility needs, and interface states so implementation requirements are clear beyond the main screen.

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

• Preparing design specifications for developers
• Documenting loading, empty, and error states
• Defining responsive behavior and keyboard interactions

Audit how a product uses design tokens, shared settings for visual properties such as color and spacing. Identify hard-coded values, inconsistent usage, and missing tokens, then recommend replacements and prioritize migration work.

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

• Finding hard-coded colors and spacing values
• Checking duplicate or deprecated token usage
• Identifying gaps in existing design tokens