enterprise

Generates implementation-ready enterprise design-system guidelines with tokens, component rules, and accessibility criteria.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill enterprise-yashmishra2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise
Source: https://github.com/yashmishra2006/LexWrite-Website/tree/main/.agents/skills/design-system
Command: npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill enterprise-yashmishra2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building data-driven enterprise interfaces often lack consistent, testable design-system guidance, leading to inconsistent spacing, low-contrast text, and inaccessible components. This Skill produces structured, opinionated design-system documentation that engineers and designers can implement directly. ## Core Features & Use Cases - Token-First Foundations: Defines color, typography, and spacing tokens (Ubuntu/Oswald fonts, semantic color palette, comfortable density) before component rules. - Component-Level Rules: Specifies anatomy, variants, states (default, hover, focus-visible, active, disabled, loading, error), and responsive behavior for each component. - Accessibility Acceptance Criteria: Anchors every rule to WCAG 2.2 AA with testable requirements, keyboard-first interactions, and visible focus states. - Use Case: A product team standardizing a drag-and-drop workflow builder uses this Skill to generate a complete design-system document with anti-patterns, migration notes, and a QA checklist for code review. ## Quick Start Ask the AI to generate enterprise design-system guidelines for a specific component set, such as "create design-system rules for data tables and form inputs following the enterprise token palette."

Frequently Asked Questions about enterprise

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a design system for an enterprise web application?

Start by defining foundational tokens for color, typography, and spacing, then specify component anatomy, variants, and states. This Skill generates that structure with accessibility acceptance criteria and a QA checklist for code review.

What should component-level design system documentation include?

Each component should define anatomy, variants, and states including default, hover, focus-visible, active, disabled, loading, and error. It should also cover keyboard, pointer, and touch interaction behavior plus responsive edge cases like long labels and empty states.

Does this design system guidance meet WCAG accessibility standards?

Yes, the guidelines target WCAG 2.2 AA with keyboard-first interactions and visible focus states. Every accessibility statement is required to be testable in implementation, and conflicts between aesthetics and accessibility are resolved in favor of accessibility.

What color palette and typography does the enterprise design system use?

The palette uses primary #072C2C, secondary #FF5F03, success #16A34A, warning #D97706, danger #DC2626, surface #EDEADE, and text #111827. Typography uses Ubuntu as primary, Oswald for display, and Ubuntu Mono for code.

When should I not use a token-based design system approach?

Token-based systems add overhead for one-off prototypes or throwaway pages where consistency does not matter. They are most valuable for products with multiple contributors, long maintenance horizons, and accessibility obligations.