keel-design
Skill0 starsChanged 28 days agoMITView on GitHub
Design lane router. Routes visual/UI work to the right vendored design engine (impeccable, frontend-design) or to the local fused-landing skill for landing/marketing pages. Kills generic "AI slop" UI. Defers to keel-v2. Use when styling, polishing, critiquing, or building any user-facing UI, component, or page and you want it to look deliberate, not defaulted.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- roselis-lab/keeltheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- roselis-lab/keel★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- skills/keel-v2/CLAUDE.mdCLAUDE.md
- doc-syncSkill
- fused-landingSkill
- keel-contentSkill
- keel-devSkill
- keel-financeSkill
- keel-legalSkill
- keel-marketingSkill
- keel-opsSkill
- keel-qaSkill
- keel-researchSkill
- keel-secureSkill
- keel-setupSkill
- keel-v2Skill
- keel-verifySkill
- lazy-loopSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Run the keel-v2 scan first (most design work is FAST.
- Very specific: line 33
Default impeccable as the primary taste engine (richer command vocabulary: polish, audit, critique, distill, animate).
- Very specific: line 35
Use frontend-design when you want the official Anthropic baseline or it's already the house standard.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Keel Design — design lane router
Index, not an implementation. Picks the design engine; the engine does the work. Design conformance and a11y here are keel-v2 tripwires — never cut.
Deference — keel-v2 is the arbiter
Run the keel-v2 scan first (most design work is FAST; a form posting to an auth'd/PII endpoint flips HEAVY — keel-v2 §0). Design-conformance and a11y tripwires always run, at any laziness level.
Dispatch table
| When the task is… | Dispatch to | Type | Source |
| Landing / marketing / hero / pricing / CTA page, DESIGN.md-token-disciplined | fused-landing | local skill | this repo |
| Give the whole harness design taste: polish, audit, critique, animate, bolder/quieter | impeccable | skill | pbakaus/impeccable |
| Official Anthropic design-system baseline (frontends, "make it not look AI-generated") | frontend-design | plugin | anthropics/claude-code |
Collision rule (read this — the two engines overlap)
impeccable and frontend-design both fight AI-slop UI. Pick one per
project, don't run both — two design skills firing on the same task just
flip a coin.
- Default
impeccableas the primary taste engine (richer command vocabulary:polish,audit,critique,distill,animate). - Use
frontend-designwhen you want the official Anthropic baseline or it's already the house standard. - For a landing/marketing page,
fused-landingwins outright — it carries the DESIGN.md token discipline and anti-pattern blocklist. It in turn defers to keel-v2 the same way this router does.
If the target isn't installed
Fall back to fused-landing (local, always present) for pages; otherwise base
Claude Code under keel-v2 design tripwires. Never claim a design engine ran
when it isn't installed. Install: ./install.sh design.
Sources: pbakaus/impeccable · anthropics/claude-code (frontend-design plugin) · local fused-landing. Upstreams unmodified.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.