impeccable

Generates production-grade frontend interfaces with distinctive design direction and anti-generic aesthetic rules.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Gito125/gideon_portfolio --skill impeccable-gito125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/Gito125/gideon_portfolio/tree/main/.github/skills/impeccable
Command: npx skills add https://github.com/Gito125/gideon_portfolio --skill impeccable-gito125

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI-generated frontend code tends to converge on generic, recognizable aesthetics—default fonts, gradient text, side-stripe cards, and templated layouts. This Skill enforces a disciplined design process that produces distinctive, intentional interfaces grounded in real project context instead of reflexive defaults. ## Core Features & Use Cases - Context-First Design Protocol: Requires confirmed design context (audience, use cases, brand personality) via a teach mode that interviews the user and writes a persistent .impeccable.md Design Context file before any design work begins. - Opinionated Aesthetic Rules: Ships strict guidelines for typography (font selection procedure with a banned reflex-font list), color (OKLCH palettes, tinted neutrals, theme derived from audience), spatial design, motion, interaction, and UX writing, plus absolute bans on AI-tell CSS patterns like gradient text and side-stripe borders. - Three Invocation Modes: craft runs a shape-then-build flow with visual iteration, teach sets up project design context, and extract consolidates repeated components and tokens into a design system. - Use Case: A developer asks for a new landing page; the Skill first loads the project's Design Context, commits to a bold aesthetic direction, then implements the page while avoiding every documented AI-slop pattern. ## Quick Start Ask the assistant to run /impeccable teach to set up design context, then use /impeccable craft followed by a feature description to build the interface.

Frequently Asked Questions about impeccable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use the impeccable skill to build a frontend page?▼

Invoke it with the craft argument followed by a feature description, such as /impeccable craft pricing page. It first shapes a design brief, loads the relevant reference files, builds the interface, then iterates visually against the brief until the result passes its quality checks.

What is the teach mode in impeccable and when do I need it?▼

Teach mode is a one-time setup that explores your codebase, asks UX-focused questions about audience and brand, and writes a Design Context section to .impeccable.md. It is required before any design work if no design context exists in your instructions or project files.

Which fonts and CSS patterns does impeccable ban?▼

It bans reflex default fonts including Inter, Roboto, Fraunces, Playfair Display, Space Grotesk, and similar overused families. It also absolutely bans gradient text via background-clip and side-stripe borders wider than 1px on cards, callouts, or alerts.

Does impeccable work with existing design systems?▼

Yes, the extract mode identifies repeated components, hard-coded values, and patterns used three or more times, then consolidates them into reusable components and design tokens following your existing conventions. It asks before creating a design system if none exists.

Why does impeccable refuse to start design work immediately?▼

It requires confirmed design context—target audience, use cases, and brand personality—because code alone cannot reveal who a product is for or how it should feel. Without this context it runs the teach flow instead of guessing from the codebase.