UI/UX, 로고, 슬라이드, 이미지 생성 (7.3천건)
Use when you design or change an endpoint's errors, status codes, pagination, idempotency or concurrency behaviour — one error shape, the status-code table, bounded lists, safe retries
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or reusing Flutter UI - organize widgets as atoms, molecules, and organisms in a shared library and never hand-roll a component that already exists
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the repository has no design system yet (no tokens, no component library - a new site/app, an "Apply design system" task, or a task that asks for one), before building any page section - writes the approved design system's generated files from get_design_system (files true) and builds the tokens on them when there is one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when styling any web UI - style with Tailwind utility classes and design tokens, avoid custom CSS, and build on the existing Radix/shadcn primitives instead of hand-rolling
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you are about to hand off any UI change - the four-width check and the screenshot checklist that decide whether the screen is really done.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when modelling a rich domain in Java - SOLID principles, encapsulated entities that enforce their own invariants, and value objects over primitives
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing or building any screen, section or component that a user sees — visual hierarchy, typography, colour, spacing, states, forms and how to avoid the generic AI look.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design efficient early signals to validate assumptions. Find the fastest way to learn if you're right.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design audience-specific framing, drafts, and communication sequence for stakeholder updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Formulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design robust experiments to test product hypotheses. Define metrics, sample size, and success criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Request a design review for all commits on the current branch and present the results
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Request a design review for a commit and present the results
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inspect, stream, and explicitly adjust live Android UI tweak values or invoke app-owned actions through Snap-O. Use when a request mentions Snap-O Tweaks, tweak-enabled Android apps, runtime UI parameters, Compose tweak or action controls, tweak discovery, previously adjusted or currently inactive tweaks, applying all user-made tweak changes, typed values, defaults or resets, tweak batches, explicitly registered actions, the Tweaks REST/SSE API, or selecting between CLI, macOS tool, in-app overlay, and custom tweak interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for the Kimix web frontend (src/app/) — vanilla TypeScript + Vite, SSE-based chat UI mirroring sse_cli.py. Use when modifying the frontend, adding new UI features, changing the API client, or understanding the message rendering pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create comprehensive design systems, brand identities, and UI component libraries. Use when the user says "create design system", "build brand identity", "design UI components", "generate design tokens", "create figma specs", "review my design", "analyze design trends", "audit accessibility", "convert design to code", or "create presentation deck". Covers 10 specialized roles from system architecture to executive presentations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate DESIGN.md files against the official Google specification using the `@google/design.md` CLI linter. Works with local files. Use when the user wants to lint a DESIGN.md, check spec compliance, find broken token references, verify WCAG contrast ratios, diff two versions, export tokens to Tailwind or DTCG format, or audit a design system file for structural correctness. Trigger on mentions of "validate DESIGN.md", "lint DESIGN.md", "check my design.md", "design.md spec compliance", "WCAG contrast check", "broken token references", "design token validation", "export design tokens", "diff design systems", "design.md audit", "@google/design.md", "npx design.md lint", "design system validation", "frontmatter tokens", or any request to verify a DESIGN.md file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Revenue-Centric Design (RCD) — evidence-backed principles for making a SaaS or startup product convert, retain, and monetize. Use when the user works on a landing page or CRO ("my page isn't converting"), onboarding/activation ("users sign up but don't stick"), churn/retention ("customers keep canceling"), pricing/monetization ("how should I price this"), checkout/forms ("dropdowns kill conversion", "annotated checkout"), dashboards/data viz ("cognitive load", "KPI shortlists"), positioning/ICP/go-to-market, feature scope, A/B-test rigor, or AI-era differentiation — or asks for the behavioral-science mechanism behind a design choice. Also use when another skill needs the principle or evidence behind a conversion/retention/pricing/checkout move. Never apply to gambling, betting, or casino products.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate a phased WinForms-to-Avalonia migration: behavior contracts, UI-independent application logic, platform adapters, MVVM shell, parity/cutover, evolution, and hardening. Use when the request explicitly involves moving a WinForms or .NET Framework desktop UI to Avalonia, or continuing that migration. Do not trigger for unrelated migrations, rewrites, ViewModel refactors, settings work, or command-line work without WinForms-to-Avalonia context. Load this orchestrator before one matching phase skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Phase D of a WinForms-to-Avalonia migration: build the Avalonia UI shell with composition, MVVM state and commands, responsive XAML, accessibility, localization boundaries, and behavior-focused unit/Headless tests. Use only when an explicit migration is ready to port Forms or when the orchestrator routes here. Prefer this over control-by-control ports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.