本文へ移動
cccskills
無料GitHub で公開

design-anti-cliche

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md9.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Design Anti-Cliché Rules — SUPERSEDED by impeccable

⚠️ This skill is superseded. The impeccable skill's shared design laws, anti-pattern rules, and deterministic checks (CLI + browser extension) provide more comprehensive, runtime-enforced design quality. The impeccable anti-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 audit for scored quality checks.

The original rules below are preserved for reference. When impeccable is active, its rules take precedence over everything below.

Delegation

When this skill is active and impeccable is installed:

  1. impeccable's shared design laws (color, typography, motion, spatial) take precedence
  2. Run /impeccable audit for deterministic anti-pattern detection
  3. The CLI npx impeccable runs 27 deterministic checks with no LLM or API key
<details> <summary>Original anti-cliché rules (superseded — reference only)</summary>

Scope: 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 impeccable skill can override ANY rule below. If the user's confirmed brand direction contradicts a rule here, impeccable's DESIGN.md takes precedence.


1. Safe Harbor Forbidden Defaults

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 DefaultWhy It's BannedUse Only When
1Standard Hero Split (left text / right image)Most overused layout in AI output. Every SaaS site looks identical.User explicitly requests split layout
2Bento Grids as default landing page layoutOverused since Apple adopted it. Not every page is a dashboard.Genuinely complex data that benefits from card-based organization
3Mesh / Aurora Gradients as background decorationFloating colored blobs scream "AI-generated."Used purposefully as part of a confirmed design direction
4Glassmorphism as "premium" indicatorBlur + thin border is the AI's go-to for "modern." It's a cliché.Confirmed Glass design direction in brand-guidelines
5Fintech Blue / Deep Cyan default paletteThe "safe escape" color for any professional app. Zero personality.User's industry genuinely warrants trust-signaling blue
6Generic Marketing CopyBuzzwords make every product indistinguishableNever — always write specific, concrete copy

Banned Copy Words

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."


2. Purple Ban

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.

Banned Values

  • Hex codes: #8B5CF6, #A855F7, #9333EA, #7C3AED, #6D28D9, #A78BFA, #C4B5FD, #DDD6FE, #EDE9FE
  • Tailwind classes: purple-*, violet-*, indigo-*, fuchsia-* as primary/brand colors
  • CSS keywords: purple, violet, indigo, fuchsia, magenta, lavender as primary/brand colors
  • Purple gradients of any kind as hero or background treatment

When Purple IS Allowed

  • User explicitly says "I want purple" or "our brand is purple"
  • brand-guidelines has purple in the confirmed color palette
  • Used as a minor accent (not primary, not brand-defining)
  • Data visualization where purple is part of a sequential/categorical scale

Recommended Alternatives

When you'd reflexively reach for purple, try: Teal, Emerald, Amber, Rose, Slate — or ask the user what palette fits their brand.


3. Layout Diversification

Break the "Standard Split" habit. When designing hero sections or landing pages, choose from these alternative structures:

LayoutDescriptionBest For
Massive Typographic HeroHeadline at 300px+, visual behind or inside the lettersBold brands, creative agencies
Center-StaggeredEach element (H1, P, CTA) has different horizontal alignmentModern, editorial feel
Layered Depth (Z-axis)Visuals overlap text, creating depthImmersive, premium products
Vertical NarrativeNo "above the fold" hero — story starts immediately with flowing fragmentsStory-driven, content-first
Extreme Asymmetry (90/10)Everything compressed to one edge, 90% negative spaceLuxury, high-end, artistic
Full-Bleed MediaImage/video fills the entire viewport, text overlaidPhotography, portfolio, lifestyle

Rule: If you're about to use "left text / right image," stop. Pick one of the above or invent something new.


4. UI Library Default Ban

Never automatically use a component library without asking the user. These are AI favorites from training data, not the user's choice:

  • ❌ shadcn/ui (overused AI default)
  • ❌ Radix UI (AI favorite for "accessible" claim)
  • ❌ Chakra UI (common AI fallback)
  • ❌ Material UI / MUI (generic corporate look)

Always ask: "Which UI approach do you prefer?" and offer options:

  1. Pure CSS / Tailwind — custom components, no library
  2. shadcn/ui — if the user explicitly wants it
  3. Headless UI — unstyled, accessible primitives
  4. Radix — if the user explicitly wants it
  5. Custom components — maximum control
  6. Other — the user's choice

5. Corner Radius Rule

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.

IntentRadiusExamples
Sharp / Technical / Luxury0px–2pxBrutalist, minimalist, professional
Balanced / Modern8px–12pxSaaS dashboards, productivity tools
Soft / Friendly / Playful16px–32pxSocial apps, lifestyle, consumer
Pill / Expressive9999px / fullTags, 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.


6. Maestro Self-Check

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.

#QuestionBad Answer
1Does this look like something an AI would generate?Yes → revise
2Could I swap the brand name and this would fit any other product?Yes → not specific enough
3Am I using purple/indigo because it "feels modern"?Yes → Purple Ban violation
4Is the layout "left text / right image" or a bento grid?Yes without explicit request → Safe Harbor violation
5Would a designer at a top agency present this to a client?No → raise the bar
6Is every animation serving a purpose, or just decoration?Decoration → remove it

7. Modern Cliché Scan

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

8. Override Protocol

These rules are universal defaults. They can be overridden by:

  1. brand-guidelines skill — If the confirmed design direction uses a forbidden element (purple brand, glassmorphism direction, etc.), the brand guideline takes precedence
  2. Explicit user request — If the user says "I want a bento grid layout," use it
  3. Design reference data — If the searchable design database returns a style that uses a forbidden element and the user confirms it, use it

Override 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".

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

Analyzes codebase structure, data flow, module relationships, and key patterns to generate and maintain a living architecture document (ARCHITECTURE.md).

日本語の概要は準備中です。原文の説明を表示しています。

RepairYourTech/cfsa-antigravity62026年8月16日 更新

RepairYourTech のスキルをすべて見る

このスキルの問題を報告する