enterprise
Skill0 starsChanged 2 months agoMITView on GitHub
Dark-themed cloud-platform aesthetic with modular grids, glass-like panels, and strong data hierarchy for productivity dashboards.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- jdonohoo/vern-bottheir own version, first seen Nov 15, 2026
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- popup-studio-ai/bkit-claude-codetheir own version, first seen Oct 8, 2026
- andfrancot-alt/claude-skillsword for word, first seen Aug 17, 2026
- ww-w-ai/bkit-claude-codetheir own version, first seen Aug 14, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 7 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.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
kannaka-labsSkillskill-status
Show where you are in the workflow and what to do next — use for progress checks and orientation. Use when: AUTOMATICALLY ACTIVATE when user asks about:. \"status\" or \"progress\" or \"where am I\". \"what's next\" or \"next step\"
Also in 3 projects that use this
dacryptSkillcontrol
Control your Tesla — lock, unlock, climate, trunk, horn, flash, windows, sentry mode, charge port, speed limit. Use when someone says "lock my car", "turn on the AC", "open the trunk", "honk the horn", etc.
Also in 3 projects that use this
launch52-aiSkillskill-create
Create and validate Claude Code skills with proper structure, checklists, and validation scripts. Use when creating a new skill, auditing existing skills, or ensuring skills meet quality standards. Generates complete skill scaffolds with SKILL.md, check scripts, guides, and templates.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
- +2 more from ww-w-ai
Other versions10 projects use a version of this.
Word for word · 2
- bergside/awesome-design-skills★ 2.9k100% same
- andfrancot-alt/claude-skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 8
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-codex★ 69same name
- ww-w-ai/bkit-gemini★ 66same name
- jdonohoo/vern-bot★ 15same name
- anotherben/claude-harness★ 7same name
- anotherben/claude-enterprise-skills★ 1same name
- hemal08ce094/DesignSkillsSwiftUI★ 0same 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 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
- 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
- impeccableSkill
- 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
19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
19
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 14
Create practical, implementation-ready guidance that can be directly used by engineers and designers.
- Distinctive: line 33
prefer semantic tokens over raw values
- Distinctive: line 35
keep interaction states explicit
- Distinctive: line 37
ensure responsive behavior by default
- Distinctive: line 41
avoid low contrast text
- Distinctive: line 42
avoid inconsistent spacing rhythm
- Distinctive: line 43
avoid decorative motion without purpose
- Distinctive: line 45
avoid mixing multiple visual metaphors
- Distinctive: line 46
avoid inaccessible hit areas
- Distinctive: line 49
Follow the foundations first, then component consistency.
- Distinctive: line 50
When uncertain, prioritize accessibility and clarity over novelty.
- Distinctive: line 52
Keep guidance opinionated, concise, and implementation-focused.
- Distinctive: line 59
Add anti-patterns and migration notes for existing inconsistent UI.
- Distinctive: line 63
When generating design-system guidance, use this structure:
- Distinctive: line 79
No rule should depend on ambiguous adjectives alone.
- Distinctive: line 80
Every accessibility statement must be testable in implementation.
- Distinctive: line 81
Prefer system consistency over one-off local optimizations.
- Distinctive: line 85
Use "must" for non-negotiable rules and "should" for recommendations.
- Distinctive: line 87
If introducing a new pattern, include migration guidance for existing components.
“Common” is measured: kept by at least 6 in 10 of the 7 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 -->Enterprise Design System Skill (Universal)
Mission
You are an expert design-system guideline author for Enterprise. Create practical, implementation-ready guidance that can be directly used by engineers and designers.
Brand
Enterprise design emphasizes grids, modular components, and strong visual hierarchy to present complex data in a clear and accessible way. The interface is built for productivity, enabling users to monitor, analyze, and interact with information efficiently.
Style Foundations
- Visual style: modern, clean, cloud-platform aesthetic (Heroku/Vercel/GitHub inspired), dark theme, subtle gradients, soft shadows, glass-like panels, rounded components
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=IBM Plex Sans, display=IBM Plex Sans, mono=IBM Plex Sans | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, neutral, success, warning, danger | Tokens: primary=#0C5CAB, secondary=#0a4a8a, success=#10b981, warning=#f59e0b, danger=#ef4444, surface=#09090b, text=#fafafa
- Spacing scale: 8pt baseline grid
Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets, high-contrast support
Writing Tone
concise, confident, helpful, clear, friendly, professional, action-oriented, low-jargon
Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit
- design for empty/loading/error states
- ensure responsive behavior by default
- document accessibility rationale
Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid decorative motion without purpose
- avoid ambiguous labels
- avoid mixing multiple visual metaphors
- avoid inaccessible hit areas
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.

