313건 · 관련도순
Design web interfaces, build prototypes, and integrate changes into existing apps while respecting their visual rules and components. Choose direct code generation or Claude Code design commands, with an experimental browser canvas option for visual review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review OpenClaw frontend code and rendered screens for departures from Carapace design rules, accessibility issues, responsive defects, and inconsistent copy. Produce evidence-based JSON and Markdown reports that distinguish documented violations from judgment-based suggestions and guide narrowly scoped fixes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Read frontend source code to document colors, typography, spacing, components, and layout rules in DESIGN.md. Use it to understand an existing interface or prepare design guidance for Stitch without building or running the app.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and refine screen designs in Stitch from text descriptions or images. The skill clarifies layout requirements, edits existing screens, explores alternative designs, and saves HTML and screenshots for review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create and update shared design rules in Stitch, including colors, fonts, and corner shapes, then apply them to existing screens. Keep a DESIGN.md file and project metadata alongside the design system.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create reusable iPolloWork templates for designs, editable presentations, and HyperFrames videos through conversation. Define replaceable content and visual settings, maintain the template package, and validate editing and theme changes before saving.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn reference UI screenshots into documented design rules, product requirements, and prompts for building React interfaces. Extract colors, typography, spacing, and component styles, then use them to create consistent screen variations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use `icon-system` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use `design-qa-checklist`; for reusable library components use `component-spec` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use `design-token` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clone websites to React/HTML code and customize Anima output with AI. Use when converting live websites to code, customizing generated components, or building design-system-aware code from URL screenshots. Trigger with: "anima website to code", "anima URL clone", "anima AI customization", "website to react", "clone website to code".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Universal UI/UX design principles covering visual hierarchy, interaction laws, typography foundations, and WCAG accessibility requirements. Use when making design decisions not covered by a specific design system, validating principle compliance, or resolving conflicts between aesthetics and accessibility. Design-system-agnostic and applies to every surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build scalable design systems with Tailwind CSS, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Batch-generate and compare visual design directions so a user can choose the style they actually want. Use when the user says they cannot describe an abstract visual style, asks for many style options, wants to choose from generated UI/design-system images, rejects outputs as too colorful/too dead/too generic, or needs an existing UI/design system evolved without discarding current assets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check that the UI you actually rendered uses the design system, by reading computed styles in the running app against the project's design tokens. Catches hardcoded hex colors, off-palette backgrounds, invisible or unusable controls, and animations that never ran. Use after building or restyling a component, when a design review is wanted, when a UI looks slightly off but nobody can say why, or when a design system exists and nothing checks whether the code follows it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract a complete design system from an existing website or screenshot into a DESIGN.md file. Analyses colours, typography, component styles, spacing, and atmosphere through browser automation and HTML inspection. Produces a semantic design system document optimised for consistent page generation. Triggers: 'extract design system', 'design system', 'create DESIGN.md', 'analyse the design', 'what design does this site use', 'extract styles from', 'reverse engineer the design'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.