1.3천건 · 관련도순
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch. Reports only new violations introduced, violations fixed, and pre-existing count. Use `scan` for a full audit with no diffing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing UI code for interface-guideline compliance (accessibility, forms, animation, images, performance, UX copy) and/or validating a deployed page against Lighthouse 95+ targets. Produces evidence-based findings (file:line + Lighthouse JSON) and turns confirmed pendencies into Draft SPECs via write-specs. Do NOT use to design/build UI from scratch (use design) or to fix findings inline — fixes go through the SPEC pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Design] Use when a workflow step or the user asks for UI creation, exploration or description from briefs, screenshots or videos for product/marketing interfaces. --mode=review checks layout, styling, accessibility and async states.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. 7 phases: interaction, responsiveness, accessibility. Inventory via existing-ui-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review a written plan or design doc through a designer's lens before implementation - seven passes over information architecture, interaction states, emotional arc, AI-slop risk, design-system alignment, responsive and accessibility coverage, and unresolved decisions. Each dimension is rated 0-10 with an explicit statement of what would make it a 10, then the plan is edited to get there. Use when a plan has a UI surface and you want the design gaps closed before code is written. Not for auditing a live site.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive QA of a SwiftUI app on a real iPhone over USB - screenshot, read the accessibility tree, inspect @Observable state, tap, swipe, and type through an HTTP bridge embedded in the app under test. Use when asked to test an iOS app on a physical device, find bugs on the device, or expose a connected iPhone to a remote agent over Tailscale. Requires the ios-agent-qa runtime; not for simulator or XCTest work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance and UX best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[Project Management] Use when a workflow step or the user asks for UI/UX specs for views, flows, states and accessibility. --mode=wireframe converts sketches or wireframes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI, React Aria, Radix), or review agent-generated interface code for quality, accessibility, and performance. Also trigger for "make the UI better", "review my interface", "clean up this component", or any frontend work in React, Next.js, or plain HTML/CSS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sync reusable frontend decisions into persistent project documentation after UI work. Use when frontend changes introduce or modify component APIs, variants, design-system tokens, styling conventions, layout behavior, accessibility rules, interaction patterns, responsive behavior, or agent operating instructions; when the user asks to reflect decisions in components.md, design system docs, AGENTS.md, CLAUDE.md, GEMINI.md, or similar project memory files; or before finalizing frontend work where future consistency depends on decisions made during implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform comprehensive exploratory testing on a website using browser automation, covering user journeys, forms, errors, accessibility, responsiveness, performance, and security basics. Use when asked to QA a site, explore an app, find bugs, or produce a browser testing report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink components, Textual widgets, Bubbletea views, terminal color palette, keybinding design, panel layout, split panes, terminal dashboard, box-drawing characters, sparklines, progress bars, modal dialogs, focus management, or terminal accessibility.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Crie e evolua sistemas de design com design tokens, arquitetura de componentes, diretrizes de acessibilidade e templates de documentação. Garante UI consistente, escalável e acessível em todos os produtos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inteligência de design UI/UX. 50 estilos, 21 paletas, 50 combinações de fontes, 20 gráficos, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Ações: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projetos: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elementos: button, modal, navbar, sidebar, card, table, form, chart. Estilos: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Tópicos: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrações: shadcn/ui MCP para busca de componentes e exemplos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Auditar e melhorar a acessibilidade web seguindo as diretrizes WCAG 2.1. Use quando solicitado para "melhorar acessibilidade", "auditoria a11y", "conformidade WCAG", "suporte a leitor de tela", "navegação por teclado" ou "tornar acessível".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, naming conventions, or CLI tooling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the Opquast Digital Quality Framework (245 rules, 14 categories) when building, reviewing, or auditing websites and web applications. Use for web development quality assurance, accessibility compliance, security hardening, privacy implementation, e-commerce best practices, and holistic digital quality checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill when configuring axe-core scans, reviewing automated accessibility test results, or writing tests that use @axe-core/playwright, @axe-core/react, or similar integrations. Provides a quick reference to axe 4.x rule IDs, their WCAG mapping, and default severity levels.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load this skill whenever you are planning, executing, or reviewing manual accessibility testing. Manual testing with real assistive technologies is essential — automated tools catch only ~30–40 % of WCAG issues. Absolutely always include keyboard-only testing and at least one screen reader test before marking a feature accessible. Under no circumstances skip forced colors mode testing for UI components.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.