What is i-teach-impeccable?

A one-time setup guide that gathers a project's design context and saves it in the AI configuration for future sessions. The context includes users, purpose, brand personality, visual references, and existing design choices.

Use it at the start of a project to document who the product serves, what it should feel like, and which design patterns already exist. It helps guide later interface work.

It prevents the same design questions from being asked repeatedly and gives future work a shared baseline. It also separates facts found in the codebase from details that require user clarification.

How boussadjra/vuestrata configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to boussadjra/vuestrata. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/boussadjra/vuestrata/main/.github/skills/i-teach-impeccable/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/boussadjra/vuestrata

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-teach-impeccable/github.svg)](https://agentmods.dev/skills/boussadjra/vuestrata/i-teach-impeccable)

Your own site

<a href="https://agentmods.dev/skills/boussadjra/vuestrata/i-teach-impeccable"><img src="https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-teach-impeccable/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/boussadjra/vuestrata/i-teach-impeccable"><img src="https://agentmods.dev/badge/skills/boussadjra/vuestrata/i-teach-impeccable.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 566 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 89% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.00566
Opus 5.5	$0.00014	$0.00226
Sonnet 5.5	$0.00007	$0.00113
Haiku 4.5	$0.00003	$0.00057

Measured 2mo ago against content hash 0920da59814e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

i-teach-impeccable 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 2mo ago.

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.

Origin

This is a copy

89% identical to teach-impeccable — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/i-teach-impeccable/SKILL.md · 78 lines

How it starts

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

Gather design context for this project, then persist it for all future sessions.

Step 1: Explore the Codebase

Before asking questions, thoroughly scan the project to discover what you can:

README and docs: Project purpose, target audience, any stated goals
Package.json / config files: Tech stack, dependencies, existing design libraries
Existing components: Current design patterns, spacing, typography in use
Brand assets: Logos, favicons, color values already defined
Design tokens / CSS variables: Existing color palettes, font stacks, spacing scales
Any style guides or brand documentation

Note what you've learned and what remains unclear.

Step 2: Ask UX-Focused Questions

ask the user directly to clarify what you cannot infer. Focus only on what you couldn't infer from the codebase:

Users & Purpose

Who uses this? What's their context when using it?
What job are they trying to get done?
What emotions should the interface evoke? (confidence, delight, calm, urgency, etc.)

Brand & Personality

How would you describe the brand personality in 3 words?
Any reference sites or apps that capture the right feel? What specifically about them?
What should this explicitly NOT look like? Any anti-references?

Aesthetic Preferences

Any strong preferences for visual direction? (minimal, bold, elegant, playful, technical, organic, etc.)
Light mode, dark mode, or both?
Any colors that must be used or avoided?

Accessibility & Inclusion

Specific accessibility requirements? (WCAG level, known user needs)
Considerations for reduced motion, color blindness, or other accommodations?

Skip questions where the answer is already clear from the codebase exploration.

Step 3: Write Design Context

Synthesize your findings and the user's answers into a ## Design Context section:

## Design Context

### Users

[Who they are, their context, the job to be done]

### Brand Personality

[Voice, tone, 3-word personality, emotional goals]

### Aesthetic Direction

[Visual tone, references, anti-references, theme]

### Design Principles

[3-5 principles derived from the conversation that should guide all design decisions]

Read the full file on GitHub · 78 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.

2mo ago First seen · 78 lines · 35 tokens per session scan A 0920da59814e

Subscribe to this mod's changes

i-teach-impeccable is a skill published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 566 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to teach-impeccable, differing in 18 lines, and is treated as a copy.

Design and UX TypeScript tailwindcss vite vitejs vuejs vuejs3

i-teach-impeccable next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
i-teach-impeccableboussadjra/vuestrata	Skill	111	11d ago	MIT	A	35	Claude Code, Codex
magic-uimagicuidesign/magicui	Skill	23k	yesterday	MIT	A	56	Claude Code, Codex
tuturuuu-satellite-app-uxtutur3u/platform	Skill	54	today	Apache-2.0	A	25	Codex
frontend-engineerbuiphucminhtam/forgewright	Skill	49	6d ago	none	A	55	Claude Code
frontend-designbartstc/vite-ts-react-template	Skill	123	13d ago	MIT	A	43	Claude Code, Codex
beuistarc007/ui-components	Skill	1.9k	yesterday	MIT	A	81	Claude Code, Codex
beui-prostarc007/ui-components	Skill	1.9k	yesterday	MIT	A	85	Claude Code, Codex

vuestrata: Skill for Claude Code