mirror of https://github.com/pbakaus/impeccable.git synced 2026-09-11 21:57:14 +03:00

Files

T

2f9dc05978 Give GitHub Copilot equal prominence in harness listings (#280 )

Audit of every user-facing surface that enumerates supported harnesses
found GitHub Copilot missing or buried in several. Bring it to parity with
Claude Code, Codex, Cursor, and Gemini.

Missing -> added:
- site/content/reference/hooks.md: the public /docs/hooks page (tagline,
  the post-edit list, and the manifest table) now covers GitHub Copilot,
  including the `.github/hooks/impeccable.json` surface and the
  default-branch/trust note. (Only skill/reference/hooks.md was updated in
  the feature PR; this is the website doc.)
- README.md Design hook section + the manifest surface list.
- site/content/tutorials/getting-started.md hook note.
- site/pages/faq.astro tool-specific setup list and the docs-links list.
- PRODUCT.md audience line and README.npm.md suite description.

Prominence + naming:
- README "Supported Tools" and the homepage hero logo row: move GitHub
  Copilot up to third (after Claude Code) instead of trailing.
- site/pages/designing: list GitHub Copilot earlier, full name.
- README "Supported Tools": the harness link now points at GitHub Copilot
  (github.com/features/copilot) instead of the unrelated VS Code entry.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-20 03:27:06 -07:00

3.3 KiB

Raw Blame History

Product

Register

brand

Users

Designers, product managers, and engineers who use AI coding tools (Cursor, Claude Code, GitHub Copilot, Gemini CLI, Codex CLI, and others) and want better design output from their AI. They land on the site from GitHub, social media, or word of mouth, already aware that AI-generated UIs have quality problems. They're looking for a practical solution, not education about the problem.

Product Purpose

Impeccable gives builders a shared design vocabulary with their AI, delivered as a plug-and-play skill that works in every major AI coding harness. Success is measured in two ways: (1) the user can steer AI output with design precision instead of vague prose, and (2) the AI produces interfaces that pass professional design review, not "looks like an AI made it" output.

Brand Personality

Expert, opinionated, refined. Impeccable speaks with an authoritative design voice: confident taste, editorial quality, zero hedging. It's the design director in the room who knows exactly what's wrong and how to fix it. The tone is direct (no "maybe consider"), specific (no "improve the vibe"), and rooted in craft (no hype, no hedging).

Three-word personality: expert, decisive, editorial.

Anti-references

The site and brand must be the antithesis of everything Impeccable critiques. Specifically, avoid:

Generic AI tool marketing: dark mode with purple gradients, neon accents, glassmorphism, glowing particles, cyan-on-black.
SaaS landing-page clichés: hero-metric layouts, identical-card feature grids, sparkline decorations, "boost your productivity" copy.
Hedging language: "might", "could", "consider", "perhaps". Impeccable is opinionated — it picks a direction and commits.
Educational framing: this product is for people who already know they have a problem; we solve it, we don't teach it.
Over-decoration: every visual element must earn its place. No ornament for ornament's sake.

Design Principles

Practice what you preach. The site must pass its own anti-pattern tests with flying colors. If we ship anything we'd flag in an audit, we've lost.
Show, don't tell. Demonstrate design quality through execution, not through words about design quality. The site IS the demo.
Expert confidence. Direct, opinionated, decisive. No hedging. Every assertion should sound like it comes from someone who has seen a thousand interfaces and knows what works.
Editorial over marketing. Feels like a design publication (Eye Magazine, It's Nice That, A List Apart) rather than a SaaS landing page. Long-form reading, considered typography, breathing room.
Purposeful restraint. Every element earns its place. Nothing decorative without function. Nothing included because "landing pages usually have that".

Accessibility & Inclusion

Baseline: WCAG 2.1 AA on all pages. Key commitments:

Color contrast ratios verified with actual contrast checks, not eyeballing.
All interactive elements keyboard-navigable with visible focus states.
prefers-reduced-motion respected for every animation.
Semantic HTML first, ARIA as a supplement, never as a workaround.
Copy readable at an 8th-grade level; jargon only when precisely needed (design terms like "OKLCH", "chroma" are acceptable because they're the actual vocabulary users are here to learn).

3.3 KiB Raw Blame History