impeccable
Skill0 starsChanged 2 months agoMITView on GitHub
A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.
165 other projects use a version of this.
Adopted by
Most recently taken up by
- iasiv5/skillstheir own version, first seen Nov 16, 2026
- wolverin0/claude-skillstheir own version, first seen Nov 15, 2026
- annahickman-maker/solo-ostheir own version, first seen Nov 15, 2026
- Binbin-miao/workbuddy-expert-teamtheir own version, first seen Nov 15, 2026
- noverwork/novertermtheir own version, first seen Nov 15, 2026
- sugatoray/aiskillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use cloud-architecture-diagram, shelra-workspace-quality and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcloud-architecture-diagram
Create, edit, or review Azure and Microsoft ecosystem architecture, GitHub CI/CD, and auth/API diagrams as editable draw.io files; resolve Microsoft and GitHub icons. Use for architecture visualization, diagram critique, or missing icons. Azure DevOps only when explicitly requested. Not for competing-cloud architecture, deployment, live discovery, security certification, or unrelated charts.
Also in 3 projects that use this
ShelraSkillshelra-workspace-quality
Audit or refine ShelraCode's main OpenTUI coding workspace when chat activity, live status, plan/context sidebar, agent visibility, or verification UX must match a supplied visual specification. Do not use for onboarding, settings, or unrelated screens.
Also in 3 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
FldicoahkiinSkillcontribute-catalog
Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry` skill.
Also in 3 projects that use this
HK-hubSkilloverdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
Also in 11 projects that use this
HK-hubSkillbolder
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
Also in 12 projects that use this
- +3 more from HK-hub
Other versions165 projects use a version of this.
Word for word · 1
- bergside/awesome-design-skills★ 2.9k100% same
Edited · 0
None found.
Wrote their own version · 164
- pbakaus/impeccable★ 111ksame name
- clidey/whodb★ 5.1ksame name
- guilhermerodz/input-otp★ 3.3ksame name
- bestofjs/bestofjs★ 3.1ksame name
- compozy/compozy★ 2.9ksame name
- Draculabo/AntigravityManager★ 2.5ksame name
- monoscope-tech/monoscope★ 2.1ksame name
- danieleteti/delphimvcframework★ 1.4ksame name
- FidelusAleksander/ghcertified★ 996same name
- Pasta-Devs/Marinara-Engine★ 765same name
154 more not listed
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 repository81 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agenticSkill
- antSkill
- artisticSkill
- basicSkill
- bentoSkill
- boldSkill
- brandkitSkill
- brutalismSkill
- cafeSkill
- claudeSkill
- claymorphismSkill
- cleanSkill
- codexSkill
- colorfulSkill
- contemporarySkill
- corporateSkill
- cosmicSkill
- creativeSkill
- design-taste-frontendSkill
- design-taste-frontend-v1Skill
- ditheredSkill
- doodleSkill
- dramaticSkill
- editorialSkill
- enterpriseSkill
- expressiveSkill
- fantasySkill
- fictionSkill
- flatSkill
- friendlySkill
- full-output-enforcementSkill
- futuristicSkill
- geometricSkill
- glassmorphismSkill
- gpt-tasteSkill
- gradientSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- immersiveSkill
- industrial-brutalist-uiSkill
- levelsSkill
- lingoSkill
- materialSkill
- matrixSkill
- minimalist-uiSkill
- minimalSkill
- modernSkill
- monoSkill
- neobrutalismSkill
- neonSkill
- neumorphismSkill
- pacmanSkill
- paperSkill
- perspectiveSkill
- powerSkill
- premiumSkill
- professionalSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 15 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 163 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
- Distinctive: line 31
prefer semantic tokens over raw values
- Distinctive: line 33
keep interaction states explicit
- Distinctive: line 36
avoid low contrast text
- Distinctive: line 37
avoid inconsistent spacing rhythm
- Distinctive: line 41
Follow the foundations first, then component consistency.
- Distinctive: line 42
When uncertain, prioritize accessibility and clarity over novelty.
- Distinctive: line 44
Keep guidance opinionated, concise, and implementation-focused.
- Distinctive: line 51
Add anti-patterns and migration notes for existing inconsistent UI.
- Distinctive: line 55
When generating design-system guidance, use this structure:
- Distinctive: line 71
No rule should depend on ambiguous adjectives alone.
- Distinctive: line 72
Every accessibility statement must be testable in implementation.
- Distinctive: line 73
Prefer system consistency over one-off local optimizations.
- Distinctive: line 77
Use "must" for non-negotiable rules and "should" for recommendations.
- Distinctive: line 79
If introducing a new pattern, include migration guidance for existing components.
“Common” is measured: kept by at least 6 in 10 of the 163 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- TYPEUI_SH_MANAGED_START -->Impeccable Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Impeccable. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
A modern, graphic, editorial-poster aesthetic — warm and confident — built on alternating cream and burnt orange sections, an amber brand color.
Style Foundations
- Visual style: modern, clean, high-contrast
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=Chakra Petch, display=Chakra Petch, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#CC8800, secondary=#C55221, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states
Writing Tone
concise, confident, helpful
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid ambiguous labels
Expected Behavior
- Follow the foundations first, then component consistency.
- When uncertain, prioritize accessibility and clarity over novelty.
- Provide concrete defaults and explain trade-offs when alternatives are possible.
- Keep guidance opinionated, concise, and implementation-focused.
Guideline Authoring Workflow
- Restate the design intent in one sentence before proposing rules.
- Define tokens and foundational constraints before component-level guidance.
- Specify component anatomy, states, variants, and interaction behavior.
- Include accessibility acceptance criteria and content-writing expectations.
- Add anti-patterns and migration notes for existing inconsistent UI.
- End with a QA checklist that can be executed in code review.
Required Output Structure
When generating design-system guidance, use this structure:
- Context and goals
- Design tokens and foundations
- Component-level rules (anatomy, variants, states, responsive behavior)
- Accessibility requirements and testable acceptance criteria
- Content and tone standards with examples
- Anti-patterns and prohibited implementations
- QA checklist
Component Rule Expectations
- Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
- Describe interaction behavior for keyboard, pointer, and touch.
- State spacing, typography, and color-token usage explicitly.
- Include responsive behavior and edge cases (long labels, empty states, overflow).
Quality Gates
- No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
- Every accessibility statement must be testable in implementation.
- Prefer system consistency over one-off local optimizations.
- Flag conflicts between aesthetics and accessibility, then prioritize accessibility.
Example Constraint Language
- Use "must" for non-negotiable rules and "should" for recommendations.
- Pair every do-rule with at least one concrete don't-example.
- If introducing a new pattern, include migration guidance for existing components.
<!-- TYPEUI_SH_MANAGED_END -->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.

