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".
日本語の概要は準備中です。原文の説明を表示しています。
Universal AI design correction rules — SUPERSEDED. The `impeccable` skill now provides 27 deterministic anti-pattern rules plus a 12-rule LLM critique pass, which are more comprehensive and runtime-enforced via the `impeccable` CLI. This file is kept for backward compatibility — the `impeccable` skill's design laws and anti-patterns take precedence.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
impeccable⚠️ This skill is superseded. The
impeccableskill's shared design laws, anti-pattern rules, and deterministic checks (CLI + browser extension) provide more comprehensive, runtime-enforced design quality. Theimpeccableanti-patterns are tied to specific design guidance the skill teaches against, include OKLCH color rules, and are actively maintained (25k+ stars).All design work should use
impeccable's rules. Use/impeccable auditfor scored quality checks.The original rules below are preserved for reference. When
impeccableis active, its rules take precedence over everything below.
When this skill is active and impeccable is installed:
impeccable's shared design laws (color, typography, motion, spatial) take precedence/impeccable audit for deterministic anti-pattern detectionnpx impeccable runs 27 deterministic checks with no LLM or API keyScope: These rules apply to ALL design work — ideation, spec writing, design system creation, and implementation. They correct universal AI tendencies, not project-specific preferences.
Override: The
impeccableskill can override ANY rule below. If the user's confirmed brand direction contradicts a rule here,impeccable's DESIGN.md takes precedence.
AI agents retreat to "safe" patterns from training data. These are forbidden as defaults — you may use them only if the user explicitly requests them or the design direction specifically calls for them.
| # | Forbidden Default | Why It's Banned | Use Only When |
|---|---|---|---|
| 1 | Standard Hero Split (left text / right image) | Most overused layout in AI output. Every SaaS site looks identical. | User explicitly requests split layout |
| 2 | Bento Grids as default landing page layout | Overused since Apple adopted it. Not every page is a dashboard. | Genuinely complex data that benefits from card-based organization |
| 3 | Mesh / Aurora Gradients as background decoration | Floating colored blobs scream "AI-generated." | Used purposefully as part of a confirmed design direction |
| 4 | Glassmorphism as "premium" indicator | Blur + thin border is the AI's go-to for "modern." It's a cliché. | Confirmed Glass design direction in brand-guidelines |
| 5 | Fintech Blue / Deep Cyan default palette | The "safe escape" color for any professional app. Zero personality. | User's industry genuinely warrants trust-signaling blue |
| 6 | Generic Marketing Copy | Buzzwords make every product indistinguishable | Never — always write specific, concrete copy |
Never use these in headlines, hero text, or primary CTAs unless the user's actual product documentation uses them:
Orchestrate · Empower · Elevate · Seamless · Leverage · Synergize · Unlock · Supercharge · Game-changing · Next-generation · Cutting-edge · Revolutionary
Instead: Describe what the product actually does in concrete terms. "Send invoices in 30 seconds" beats "Elevate your billing experience."
Purple, violet, indigo, and magenta are the #1 AI design cliché. They are banned as primary or brand colors unless the user explicitly requests them.
#8B5CF6, #A855F7, #9333EA, #7C3AED, #6D28D9, #A78BFA, #C4B5FD, #DDD6FE, #EDE9FEpurple-*, violet-*, indigo-*, fuchsia-* as primary/brand colorspurple, violet, indigo, fuchsia, magenta, lavender as primary/brand colorsbrand-guidelines has purple in the confirmed color paletteWhen you'd reflexively reach for purple, try: Teal, Emerald, Amber, Rose, Slate — or ask the user what palette fits their brand.
Break the "Standard Split" habit. When designing hero sections or landing pages, choose from these alternative structures:
| Layout | Description | Best For |
|---|---|---|
| Massive Typographic Hero | Headline at 300px+, visual behind or inside the letters | Bold brands, creative agencies |
| Center-Staggered | Each element (H1, P, CTA) has different horizontal alignment | Modern, editorial feel |
| Layered Depth (Z-axis) | Visuals overlap text, creating depth | Immersive, premium products |
| Vertical Narrative | No "above the fold" hero — story starts immediately with flowing fragments | Story-driven, content-first |
| Extreme Asymmetry (90/10) | Everything compressed to one edge, 90% negative space | Luxury, high-end, artistic |
| Full-Bleed Media | Image/video fills the entire viewport, text overlaid | Photography, portfolio, lifestyle |
Rule: If you're about to use "left text / right image," stop. Pick one of the above or invent something new.
Never automatically use a component library without asking the user. These are AI favorites from training data, not the user's choice:
Always ask: "Which UI approach do you prefer?" and offer options:
The "safe boredom zone" of 4px–8px (rounded-md) is the AI default for everything. It produces visually indistinct interfaces.
Rule: Make a deliberate choice. Don't sit in the middle.
| Intent | Radius | Examples |
|---|---|---|
| Sharp / Technical / Luxury | 0px–2px | Brutalist, minimalist, professional |
| Balanced / Modern | 8px–12px | SaaS dashboards, productivity tools |
| Soft / Friendly / Playful | 16px–32px | Social apps, lifestyle, consumer |
| Pill / Expressive | 9999px / full | Tags, badges, feature cards |
The chosen radius should be consistent across the design system — don't mix sharp cards with pill buttons unless the design direction explicitly calls for contrast.
Before delivering any design work (specs, mockups, or implementations), answer these questions internally. If any answer is "yes" to the bad pattern, revise before presenting.
| # | Question | Bad Answer |
|---|---|---|
| 1 | Does this look like something an AI would generate? | Yes → revise |
| 2 | Could I swap the brand name and this would fit any other product? | Yes → not specific enough |
| 3 | Am I using purple/indigo because it "feels modern"? | Yes → Purple Ban violation |
| 4 | Is the layout "left text / right image" or a bento grid? | Yes without explicit request → Safe Harbor violation |
| 5 | Would a designer at a top agency present this to a client? | No → raise the bar |
| 6 | Is every animation serving a purpose, or just decoration? | Decoration → remove it |
Run this scan before committing to any design approach:
🔍 CLICHÉ SCAN:
├── Am I defaulting to "Left Text / Right Visual"? → BETRAY IT
├── Am I using Bento Grids to organize content safely? → BREAK THE GRID
├── Am I using "safe" SaaS fonts and color pairs? → DISRUPT THE PALETTE
├── Am I using purple/indigo because it "feels techy"? → REPLACE IT
├── Am I writing "Empower your team" copy? → WRITE SOMETHING REAL
└── Will I remember this design in a year? → If no, push harder
These rules are universal defaults. They can be overridden by:
brand-guidelines skill — If the confirmed design direction uses a forbidden element (purple brand, glassmorphism direction, etc.), the brand guideline takes precedenceOverride hierarchy: User request > impeccable DESIGN.md > brand-guidelines > design-anti-cliche defaults
When overriding, acknowledge the override:
Using glassmorphism per confirmed "Glass" design direction —
anti-cliché default overridden by brand-guidelines.
</details>まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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).
日本語の概要は準備中です。原文の説明を表示しています。