impeccable
Design and improve frontend interfaces, including websites, app UI, typography, layout, accessibility, responsive behavior, and interaction.
Skill by gafar123
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/gafar123-impeccable
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: design, frontend, backend
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Node.js package
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/impeccable
What's inside
- Skill name
impeccable- Description
- Design and improve frontend interfaces, including websites, app UI, typography, layout, accessibility, responsive behavior, and interaction. Use for frontend creation, critique, and refinement; not backend-only tasks.
- License
- Apache-2.0
- Instructions
- 169 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Files (84)
- LICENSE
- MODERN-SCREENSHOT-LICENSE
- NOTICE.md
- SKILL.md
- TYPECRAFT-LICENSE
- impeccable-asset-producer.md · agents/
- openai.yaml · agents/
- adapt.md · reference/
- animate.md · reference/
- audit.md · reference/
- bolder.md · reference/
- brand.md · reference/
- clarify.md · reference/
- codex.md · reference/
- cognitive-load.md · reference/
- color-and-contrast.md · reference/
- colorize.md · reference/
- craft.md · reference/
- critique.md · reference/
- delight.md · reference/
- distill.md · reference/
- document.md · reference/
- extract.md · reference/
- harden.md · reference/
- heuristics-scoring.md · reference/
- interaction-design.md · reference/
- layout.md · reference/
- live.md · reference/
- motion-design.md · reference/
- onboard.md · reference/
- optimize.md · reference/
- overdrive.md · reference/
- personas.md · reference/
- polish.md · reference/
- product.md · reference/
- quieter.md · reference/
- responsive-design.md · reference/
- shape.md · reference/
- spatial-design.md · reference/
- teach.md · reference/
- typeset.md · reference/
- typography.md · reference/
- ux-writing.md · reference/
- cleanup-deprecated.mjs · scripts/
- command-metadata.json · scripts/
- critique-storage.mjs · scripts/
- design-parser.mjs · scripts/
- detect-csp.mjs · scripts/
- detect.mjs · scripts/
- index.mjs · scripts/detector/browser/injected/
- main.mjs · scripts/detector/cli/
- detect-antipatterns-browser.js · scripts/detector/
- detect-antipatterns.mjs · scripts/detector/
- detect-url.mjs · scripts/detector/engines/browser/
- detect-text.mjs · scripts/detector/engines/regex/
- css-cascade.mjs · scripts/detector/engines/static-html/
- detect-html.mjs · scripts/detector/engines/static-html/
- screenshot-contrast.mjs · scripts/detector/engines/visual/
- findings.mjs · scripts/detector/
- file-system.mjs · scripts/detector/node/
- …and 24 more
SKILL.md (first lines)
<!-- Modified for The Simple Lazy Developer: resolved Codex template variables, September 2026. -->
Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.
## Portable paths
Before running a script, resolve the absolute `scripts` directory beside this loaded SKILL.md. Set `IMPECCABLE_SCRIPTS` to that path in the shell used for the command. Preserve the project working directory: the scripts inspect the project, not the skill folder. Do not assume a particular user or installation path. Node.js must be available.
If a command needs browser control or image generation, check that the corresponding tool is available. If it is absent, identify that limitation and continue only the portions that do not depend on it.
## Setup
Before any design work or file edits:
1. Load context (PRODUCT.md / DESIGN.md) via the loader script.
2. Identify the register and load the matching register reference (brand.md or product.md).
3. **If the user invoked a sub-command (e.g. `craft`, `shape`, `audit`), load its reference file too.** This is non-negotiable: `craft` without `craft.md` loaded means you'll skip the shape-and-confirm step the user expects.
Skipping these produces generic output that ignores the project.
### 1. Context gathering
Two files, case-insensitive. The loader looks at the project root by default and falls back to `.agents/context/` and `docs/` if the root is clean. Override with `IMPECCABLE_CONTEXT_DIR=path/to/dir` (absolute or relative to cwd).
- **PRODUCT.md**: required. Users, brand, tone, anti-references, strategic principles.
- **DESIGN.md**: optional, strongly recommended. Colors, typography, elevation, components.
Load both in one call:
```bash
node "$IMPECCABLE_SCRIPTS"/load-context.mjs
```
Consume the full JSON output. Never pipe through `head`, `tail`, `grep`, or `jq`. The output's `contextDir` field tells you where the files were resolved from.
If the output is already in this session's conversation history, don't re-run. Exceptions requiring a fresh load: you just ran `$impeccable teach` or `$impeccable document` (they rewrite the files), or the user manually edited one.
`$impeccable live` already warms context via `live.mjs`. If you've run `live.mjs`, don't also run `load-context.mjs` this session.
If PRODUCT.md is missing, empty, or placeholder (`[TODO]` markers, <200 chars): run `$impeccable teach`, then resume the user's original task with the fresh context. If the original task was `$impeccable craft`, resume into `$impeccable shape` before any implementation work.
If DESIGN.md is missing: nudge once per session (*"Run `$impeccable document` for more on-brand output"*), then proceed.
### 2. Register
Every design task is **brand** (marketing, landing, campaign, long-form content, portfolio: design IS the product) or **product** (app UI, admin, dashboard, tool: design SERVES the product).
Identify before designing. Priority: (1) cue in the task itself ("landing page" vs "dashboard"); (2) the surface in focus (the page, file, or route being worked on); (3) `register` field in PRODUCT.md. First match wins.
If PRODUCT.md lacks the `register` field (legacy), infer it once from its "Users" and "Product Purpose" sections, then cache the inferred value for the session. Suggest the user run `$impeccable teach` to add the field explicitly.
Load the matching reference: [reference/brand.md](reference/brand.md) or [reference/product.md](reference/product.md). The shared design laws below apply to both.
## Shared design laws
Apply to every design, both registers. Match implementation complexity to the aesthetic vision: maximalism needs elaborate code, minimalism needs precision. Interpret creatively. Vary across projects; never converge on the same choices. Codex is capable of extraordinary work. Don't hold back.
### Color
- Use OKLCH. Reduce chroma as lightness approaches 0 or 100; high chroma at extremes looks garish.
- Never use `#000` or `#fff`. Tint every neutral toward the brand hue (chroma 0.005–0.01 is enough).
- Pick a **color strategy** before picking colors. Four steps on the commitment axis:
- **Restrained**: tinted neutrals + one accent ≤10%. Product default; brand minimalism.
- **Committed**: one saturated color carries 30–60% of the surface. Brand default for identity-driven pages.
- **Full palette**: 3–4 named roles, each used deliberately. Brand campaigns; product data viz.
- **Drenched**: the surface IS the color. Brand heroes, campaign pages.
- The "one accent ≤10%" rule is Restrained only. Committed / Full palette / Drenched exceed it on purpose. Don't collapse every design to Restrained by reflex.
### Theme
Dark vs. light is never a default. Not dark "because tools look cool dark." Not light "to be safe."
Before choosing, write one sentence of physical scene: who uses this, where, under what ambient light, in what mood. If the sentence doesn't force the answer, it's not concrete enough. Add detail until it does.
"Observability dashboard" does not force an answer. "SRE glancing at incident severity on a 27-inch monitor at 2am in a dim room" does. Run the sentence, not the category.
### Typography
- Cap body line length at 65–75ch.
- Hierarchy through scale + weight contrast (≥1.25 ratio between steps). Avoid flat scales.
### Layout
- Vary spacing for rhythm. Same padding everywhere is monotony.
- Cards are the lazy answer. Use them only when they're truly the best affordance. Nested cards are always wrong.
- Don't wrap everything in a container. Most things don't need one.
### Motion
- Don't animate CSS layout properties.
- Ease out with exponential curves (ease-out-quart / quint / expo). No bounce, no elastic.
### Absolute bans
Match-and-refuse. If you're about to write any of these, rewrite the element with different structure.
- **Side-stripe borders.** `border-left` or `border-right` greater than 1px as a colored accent on cards, list items, callouts, or alerts. Never intentional. Rewrite with full borders, background tints, leading numbers/icons, or nothing.
- **Gradient text.** `background-clip: text` combined with a gradient background. Decorative, never meaningful. Use a single solid color. Emphasis via weight or size.
- **Glassmorphism as default.** Blurs and glass cards used decoratively. Rare and purposeful, or nothing.
- **The hero-metric template.** Big number, small label, supporting stats, gradient accent. SaaS cliché.
- **Identical card grids.** Same-sized cards with icon + heading + text, repeated endlessly.
- **Modal as first thought.** Modals are usually laziness. Exhaust inline / progressive alternatives first.
### Copy
- Every word earns its place. No restated headings, no intros that repeat the title.
- **No em dashes.** Use commas, colons, semicolons, periods, or parentheses. Also not `--`.
### The AI slop test
If someone could look at this interface and say "AI made that" without doubt, it's failed. Cross-register failures are the absolute bans above. Register-specific failures live in each reference.
**Category-reflex check.** Run at two altitudes; the second one catches what the first one misses.
- **First-order:** if someone could guess the theme + palette from the category alone ("observability → dark blue", "healthcare → white + teal", "finance → navy + gold", "crypto → neon on black"), it's the first training-data reflex. Rework the scene sentence and color strategy until the answer isn't obvious from the domain.
- **Second-order:** if someone could guess the aesthetic family from category-plus-anti-references ("AI workflow tool that's not SaaS-cream → editorial-typographic", "fintech that's not navy-and-gold → terminal-native dark mode"), it's the trap one tier deeper. The first reflex was avoided; the second wasn't. Rework until both answers are not obvious. The brand register's [reflex-reject aesthetic lanes](reference/brand.md) list catches the currently-saturated families.
## CommandsFrom gafar123/the-simple-lazy-developer, Apache-2.0.
More from gafar123/the-simple-lazy-developer
- 0.547score
grill-with-docs
gafar123
Interview the user about a plan or design, resolve consequential choices one question at a time, and record domain terminology and durable decisions as they…
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
pragmatic-design
gafar123
Design a feature or refactor with the user and produce a short, evidence-backed implementation guide (Why → What → How) before code is written - which modules…
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
technical-writing
gafar123
Write, revise, or review technical communication using Google developer documentation style.
SkillBFreshness: B★ 1Claude Code +9 - 0.517score
grill-me
gafar123
A relentless interview to sharpen a plan or design.
SkillBFreshness: B★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Sep 7, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from gafar123
- 0.547score
grill-with-docs
gafar123
Interview the user about a plan or design, resolve consequential choices one question at a time, and record domain terminology and durable decisions as they…
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
pragmatic-design
gafar123
Design a feature or refactor with the user and produce a short, evidence-backed implementation guide (Why → What → How) before code is written - which modules…
SkillBFreshness: B★ 1Claude Code +9 - 0.547score
technical-writing
gafar123
Write, revise, or review technical communication using Google developer documentation style.
SkillBFreshness: B★ 1Claude Code +9 - 0.517score
grill-me
gafar123
A relentless interview to sharpen a plan or design.
SkillBFreshness: B★ 1Claude Code +9
Cite this page
impeccable skill. Agent Mart. https://agentmart.dev/skills/gafar123-impeccable (last updated 2026-10-24)