impeccable-design

impeccable-design is a cursor rule for Cursor from kok-o/koko-contextos-agents. It costs 0 tokens per session (2,760 once invoked), scanned A, original, MIT.

A design review checklist for detecting common patterns that make AI-generated websites look generic. It covers choices such as fonts, text sizing, spacing, and visual contrast.

In plain words
What is it for?
Use it during a design review to check typography and other frontend design rules against the listed recommendations.
Why use it?
It helps find predictable interface problems before a website change is merged.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it during a design review to check typography and other frontend design rules against the listed recommendations.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/kok-o/koko-contextos-agents/impeccable-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/kok-o/koko-contextos-agents

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for impeccable-design

README.md
[![agentmods](https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/impeccable-design.svg)](https://agentmods.dev/rules/kok-o/koko-contextos-agents/impeccable-design)
Your own site
<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/impeccable-design"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/impeccable-design.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02760
Opus 5 $0.00000 $0.01380
Sonnet 5 $0.00000 $0.00552
Haiku 4.5 $0.00000 $0.00276

Measured yesterday against content hash 1061ff7772d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

impeccable-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/impeccable-design.mdc · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: impeccable-design

impeccable-design

Overview

A brief summary of what the skill does and its core philosophy.

When to Use

Context for when this skill is applicable.

Rules & Patterns

Based on pbakaus/impeccable — deterministic detector rules for AI-generated frontend design.

Core Principle

Every model is trained on the same SaaS templates. Skip this guidance and you get the same handful of tells on every project. Impeccable eliminates them.

Role in the Pipeline

This skill acts as a QA-designer at the /review phase. ui-ux-pro is the planning guideline; impeccable-design is the hard checklist that runs before merge.


Anti-Pattern Rules

Typography (Rules T1–T10)

Rule Anti-Pattern Correct Approach
T1 Using Inter for all text Use Inter for UI body, pair with a distinct display font for headings OR with JetBrains Mono for technical/number accents (premium SaaS pattern)
T2 Using Arial or Helvetica Use a curated Google Font pairing
T3 All text same weight Use weight contrast: 700 headings, 400 body, 500 labels
T4 Line height = 1 (tight) Body: 1.6–1.8, Headings: 1.1–1.3
T5 No letter-spacing on caps Uppercase labels: letter-spacing: 0.08em (Tailwind: tracking-widest)
T6 Text too wide Max line length: 60–75 characters — use max-w-prose or max-w-[65ch]
T7 Monospace only for code Use tabular-nums Tailwind class for number tables and data grids
T8 Random font sizing Use a consistent modular scale (1.25× or 1.333×) — use Tailwind's text-* scale
T9 Body text too small Minimum text-sm (14px) for body, never smaller than 12px
T10 Bold everywhere Bold is for emphasis. Diluted if overused.

Tailwind typography utilities:

  • text-balance — for headlines (prevents orphan words)
  • text-pretty — for body paragraphs (smart line-breaks)
  • tabular-nums — for numerical data tables

Read the full file on GitHub · 203 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday Changed · +2 lines 1061ff7772d3
  2. 7d ago First seen · 201 lines · 0 tokens per session scan A d6e073569c33

Subscribe to this mod's changes

impeccable-design is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,760 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other cursor rules, from other repositories

align-grid

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid…

danielvm-git/bigpowers · 157 tokens

extract-design

Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose. Use when the user has an HTML prototype and wants a DESIGN.md to anchor their project's visual identity, or when seed-conventions has just scaffolded a…

danielvm-git/bigpowers · 66 tokens

hatch3r-design-system-detection

Mandatory detection of existing design tokens, theme primitives, and component library before AI agents author new UI components.

hatch3r/hatch3r · 0 tokens

hatch3r-ux-states-and-flows

Four-state surface contract (loading/empty/error/partial), user-flow decomposition before implementation, and microcopy + tone discipline for end-user UIs.

hatch3r/hatch3r · 0 tokens

hatch3r-ai-ux-patterns

2026 AI/agentic UX patterns for end-user projects shipping AI features — streaming, tool-call UI, human-approval gates, cancel/abort/undo, citations.

hatch3r/hatch3r · 0 tokens

hatch3r-accessibility-standards

Accessibility standards covering WCAG 2.2 AA compliance, keyboard navigation, screen readers, and ARIA patterns.

hatch3r/hatch3r · 0 tokens