'web-ui' 검색 결과

Unstyled accessible React component primitives

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

Ant Design enterprise UI library for React

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

TanStack Table v8 patterns - useReactTable, column definitions, sorting, filtering, pagination, row selection, virtual scrolling, server-side data

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

Material UI component library patterns for React

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

Diagnose and fix UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.

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

Increase visual impact, contrast, personality, and compositional confidence when a design feels bland, generic, or too safe. Use when the design needs more energy, confidence, or memorability—not when the real problem is clutter, over-intensity, or micro-detail polish.

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

Design onboarding and activation flows that help users reach value quickly. Use when the user mentions onboarding, getting started, first-time users, activation, aha moments, or new user flows—not when the work is only the empty-state surface itself.

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

Audit and realign UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.

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

Plan, implement, or improve an internationalization and localization strategy for UI content, formatting, and regional adaptation. Use when the user asks to add i18n, localize, translate, support multiple languages, handle regional formats, manage locale switching, or build a multilingual product.

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

Improve how interfaces use photos, screenshots, icons, illustrations, and user-uploaded media so visuals support clarity instead of undermining it. Use when the user mentions images, screenshots, background photos, hero images, icon sizing, user-uploaded media, crops, overlays, or image readability.

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

Add or refine depth through elevation systems, raised and inset surfaces, layered overlap, and meaningful shadow behavior so interfaces feel structured instead of flat. Use when the user mentions depth, elevation, shadows, layering, flat cards, pressed states, drag feedback, or inset controls.

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

Add moments of joy, personality, and surprise through success states, empty states, loading moments, hover details, and celebratory polish once the fundamentals already work. Use when the user wants delight, charm, personality, or memorable micro-interactions—not when the main need is baseline cleanup or stronger visual impact.

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

Build or refine UI color systems, warmth, semantic color, and color-based hierarchy in designs that are too gray, monochromatic, or missing color meaning. Use when the user mentions dull colors, gray UI, missing warmth, weak semantic color, or a need for stronger color hierarchy.

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

Improve layout composition, spacing systems, grouping, and visual rhythm. Use when the user mentions weak layout structure, arbitrary spacing, weak grouping, crowded composition, or layout monotony rather than priority/emphasis problems.

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

Implement or refine UI motion, gestures, and transitions. Use when the user asks for animation, hover or press motion, drag or swipe behavior, transition timing, or reduced-motion alternatives. Mentioning a drawer, toast, or hover state alone does not request animation.

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

Clarify priority and emphasis by fixing unclear primary actions, competing visual weight, loud section titles, and weak label/value treatment. Use when the user mentions hierarchy, prioritization, too much competition, grayscale confusion, loud headings, or unclear primary actions.

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

Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management, making interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.

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

Create or redesign React and Tailwind sections, pages, flows, shells, and components. Use when the user wants new UI or a redesign. Implement one requested or selected direction directly, or generate distinct alternatives when the user asks to compare options.

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

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.

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

Design, structure, or improve form interfaces for clarity, completion rates, and user confidence. Use when the user asks to build a form, redesign a form flow, improve form conversion, add multi-step forms, fix form UX, or structure field layouts and validation.

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

Adapt designs for narrow, medium, wide, embedded, or print web contexts without losing usability, hierarchy, or target sizing. Use when the user mentions responsive design, breakpoints, narrow layouts, viewport changes, coarse-pointer browsers, or cross-context adaptation.

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

Design charts, metrics, and data tables that help users interpret and compare data. Use when the user asks to visualize data, choose chart types, improve dashboard analytics, or make data presentation accessible. Dashboard navigation and shell layout alone belong to add-ui or arrange.

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

Systematically audit and remediate accessibility issues in UI, focusing on keyboard navigation, screen reader support, color contrast, semantic HTML, ARIA usage, and motion sensitivity. Use when the user wants to improve accessibility, make a component accessible, fix WCAG violations, add keyboard support, or ensure screen reader compatibility.

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

Extract reusable components, product patterns, and design tokens into a clearer design system with shared APIs, documented defaults, and better reuse. Use when the user wants to refactor repeated UI, consolidate buttons/cards/forms/sections, build a component library, or turn one-off values into reusable tokens.

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