Design direction interview methodology — SUPERSEDED. The `impeccable` skill's `/impeccable teach` command now handles design direction discovery with a more comprehensive, multi-round interview that writes PRODUCT.md and DESIGN.md. This file is kept for pipeline backward compatibility — all new design work should use `/impeccable teach` instead.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
/impeccable teach⚠️ This skill is superseded. The pipeline now uses the
impeccableskill for all frontend design work. The/impeccable teachcommand provides a more comprehensive design discovery process: it runs a multi-round interview covering users, brand, tone, strategic principles, and visual identity, then writes PRODUCT.md and DESIGN.md files that all otherimpeccablecommands consume.This file is retained for pipeline backward compatibility. When the pipeline triggers design direction discovery, delegate to
/impeccable teach.
When this skill is invoked (e.g., during /create-prd-stack):
/impeccable teach to gather design contextDESIGN_DIRECTION, PRIMARY_COLOR, HEADING_FONT, etc.The original design direction interview methodology is preserved below for reference. Do not use it — use /impeccable teach instead.
| Direction | What It Is | Pros | Cons | Best For |
|---|---|---|---|---|
| Minimal/Functional | Clean, whitespace-heavy, typography-led | Timeless, fast, accessible | Can feel cold or generic | SaaS tools, developer products |
| Editorial/Magazine | Strong typographic hierarchy, content-first | Distinctive | Complex to maintain | Media, blogs, knowledge platforms |
| Luxury/Refined | Restrained palette, premium materials feel | High perceived value | Can feel inaccessible | Premium SaaS, fintech |
| Playful/Expressive | Bold color, personality, illustration | Memorable | Can age quickly | Consumer apps, gaming, social |
| Technical/Brutalist | Raw, grid-exposed, monospace, data-dense | Authentic for technical audiences | Polarizing | Dev tools, dashboards |
| Hybrid | Combine elements from two directions | Best of both | Requires design discipline | When constraints pull two ways |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
日本語の概要は準備中です。原文の説明を表示しています。
Structured methodology for adversarial thinking — generating attack scenarios, abuse cases, race conditions, and security edge cases against specs and implementations. Produces spec-level gap items, not code-level fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
日本語の概要は準備中です。原文の説明を表示しています。
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
日本語の概要は準備中です。原文の説明を表示しています。
Manage API versioning and evolution with URL/header/query strategies, deprecation workflows, breaking change classification, sunset headers, and consumer-driven contract testing. Use when designing versioning strategy, deprecating endpoints, or evolving API contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes codebase structure, data flow, module relationships, and key patterns to generate and maintain a living architecture document (ARCHITECTURE.md).
日本語の概要は準備中です。原文の説明を表示しています。