'design-system' 검색 결과

Review meter elements for accessible names, the labels screen readers use to explain what a value measures. Identify missing labels, add aria-label or aria-labelledby, and describe checks using browser accessibility tools or assistive technology.

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

• Check labels for battery and storage meters
• Add accessible names to meter elements
• Review meters in shared UI components

Review dialogs to check whether screen readers can announce their purpose when they open. Identify missing or unclear labels, suggest title or label associations, and explain how to verify the changes with accessibility tools.

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

• Checking names on modal dialogs
• Reviewing labels on alert dialogs
• Auditing shared dialog components

Inspect web pages for automatically playing audio and video, then remove autoplay or adjust required playback with muted defaults and accessible pause controls. Review keyboard access so users can stop media promptly.

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

• Review audio and video autoplay on page load
• Add muted playback and pause controls
• Check keyboard access to media controls

Review tooltips so their extra information is available to screen reader users. Check accessible names, meaning labels available to assistive technology, and links to the elements that trigger them, then suggest fixes and verification steps.

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

• Checking whether tooltip information can be read aloud
• Reviewing links between tooltips and their triggers
• Auditing shared tooltip components

Review HTML for deprecated ARIA roles, which describe elements to assistive technology, and abstract roles that should not appear in markup. Suggest recommended replacements or native HTML elements and explain potential browser and screen reader compatibility issues.

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

• Find deprecated ARIA roles in existing code
• Review whether native HTML can replace custom roles
• Inspect role usage in shared UI components

Review same-page links for accessible scrolling. Check that reduced-motion preferences disable animated scrolling, provide guidance for instant navigation, and verify that keyboard focus moves to the destination so users can continue navigating there.

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

• Reviewing same-page navigation links
• Checking scrolling with reduced motion enabled
• Fixing keyboard focus at anchor destinations

Review rendered HTML for links, buttons, or inputs inside role="text" containers. Identify controls hidden from screen readers, suggest markup changes, and explain how to check keyboard access and screen reader output after fixing them.

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

• Reviewing links and buttons inside text containers
• Investigating controls missing from screen reader output
• Checking accessibility in design system components

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

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

• Reviewing tables for screen reader accessibility
• Checking header relationships in tables with merged cells
• Reviewing table patterns in a design system

Inspect hidden page regions for links, buttons, or inputs that still receive keyboard focus. Identify elements that screen readers cannot announce, suggest focus handling changes, and explain how to verify the resulting keyboard behavior.

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

• Checking hidden regions for focusable controls
• Investigating silent focus during keyboard navigation
• Reviewing accessibility in shared UI components

Apply shared visual and writing rules to course pages, figures, and manuals. Check colors, fonts, labels, layouts, plain technical English, dark themes, keyboard focus, touch targets, and reduced-motion behavior against defined reference values.

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

• Applying consistent colors and fonts to course pages
• Checking dark theme colors and text readability
• Standardizing figure labels and card layouts

Build reusable interface components with Tailwind CSS v4, using shared design values for colors, corners, and themes. Covers buttons, forms, responsive layouts, accessibility, and dark mode to help standardize interfaces across a project.

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

• Build a reusable UI component library
• Standardize colors and component styles
• Add responsive layouts and dark mode

Build and revise a design system from brand materials or code. Organize colors, typography, spacing, components, and assets into structured files, with usage guidelines and previews, using the supported Design System artifact format.

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

• Organizing design rules from existing code and brand materials
• Documenting colors, typography, and spacing
• Collecting logos, icons, and component previews

Inspect Figma screens to gather details for implementation, including component variants, spacing, shared design settings, and image assets. It helps an agent understand layouts and design libraries before turning a design into code.

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

• Gathering implementation details from a Figma screen
• Checking component variants and spacing
• Extracting image assets for implementation

Build a design system from product code, Figma designs, and brand materials. Organize colors, typography, assets, and writing guidelines, then create reusable React components and interactive screen examples that follow the source designs.

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

• Organize brand assets and design guidelines
• Create reusable React components from existing designs
• Recreate product screens as an interactive UI kit

Create charts and dashboards with a consistent approach to chart selection, color validation, labels, and interaction. Includes a palette checker and accessibility rules for readable visualizations in both light and dark modes.

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

• Choose a chart type that fits the data
• Validate chart colors for color vision differences
• Build charts for light and dark modes

Refine AI-generated web interfaces by improving colors, spacing, typography, and action priorities while preserving existing behavior. Uses four visual styles and a seven-part review to check usability, interaction feedback, accessibility, and mobile layouts.

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

• Polish an AI-generated prototype
• Simplify dashboard controls and repeated metrics
• Restyle a page using a reference screenshot

Build consistent interface foundations with design tokens, named values for colors, spacing, and typography. Covers light and dark themes, multiple brands, reusable components, and workflows that keep design definitions aligned with application code.

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

• Organizing shared colors, typography, and spacing
• Implementing light and dark theme switching
• Sharing interface components across multiple brands

Build a consistent interface foundation with Tailwind CSS v4 using shared design values and reusable components. Covers responsive layouts, dark mode, accessibility, and component variations to help standardize UI patterns across a codebase.

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

• Building a reusable UI component library
• Standardizing colors, corner radii, and themes
• Creating responsive and accessible components

Design, refine, or review web and iOS interfaces using the product’s existing components and visual style. Consult relevant screen examples when useful, then inspect the result for layout problems, inaccessible controls, and broken interactions.

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

• Designing screens that fit an existing product
• Refining a dashboard or simplifying an interface
• Reviewing layouts and interactions before release

Create a consistent UI design system from brand colors. Generate design tokens, reusable values for colors, typography, and spacing, and support component documentation, responsive layout calculations, accessibility considerations, and clear handoff materials for developers.

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

• Generate shared design values from brand colors
• Standardize typography and spacing across screens
• Plan layouts for different screen widths

Create shared UI design values from a brand color, including palettes, typography, and spacing. Export them as CSS, SCSS, or JSON, document component behavior, plan layouts for different screens, and prepare developer handoff materials.

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

• Generate shared design values from a brand color
• Document component variants and states
• Plan typography and spacing for different screens

Turn a Markdown code review into a single HTML file with code changes beside severity-labeled comments. Readers can jump to findings, inspect line numbers, and identify the named human reviewer.

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

• Turning a lengthy Markdown code review into HTML
• Reading code changes beside review comments
• Jumping directly to findings by severity

Turn small game changes into concise specifications with clear reasons, rules, and acceptance criteria. Check existing design documents and earlier specifications, then document tuning adjustments, minor behavior changes, or small features before implementation.

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

• Documenting game balance adjustments
• Specifying minor behavior changes
• Defining a small mechanic for an existing system

Break a game concept into the systems it needs, including supporting systems that are easy to overlook. Map dependencies, assign priorities by development stage, and create an index showing the recommended order for detailed design.

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

• Identifying the systems a game concept requires
• Finding dependency cycles and bottleneck systems
• Choosing systems for the minimum playable version