enterprise

Generate enterprise UI rules for data workflows with drag-and-drop and WCAG 2.2 AA compliance.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superpollo02/awesome-design-skill --skill enterprise-superpollo02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enterprise
Source: https://github.com/superpollo02/awesome-design-skill/tree/main/skills/enterprise
Command: npx skills add https://github.com/superpollo02/awesome-design-skill --skill enterprise-superpollo02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams build consistent, accessible enterprise interfaces for data-driven workflows without guesswork or ad-hoc styling.

Core Features & Use Cases

  • High-contrast enterprise styling with defined typography, rounded corners, spacing rhythm, and a tokenized color system for primary/semantic states.
  • Workflow-oriented interaction guidance that emphasizes structured layouts and drag-and-drop patterns while keeping accessibility non-negotiable.
  • Implementation-ready rules and quality gates that translate design intent into testable engineering constraints, including WCAG 2.2 AA and keyboard-first behavior.

Quick Start

Use the enterprise skill to generate enterprise UI rules and component guidance for a data workflow interface that supports drag-and-drop interactions while meeting WCAG 2.2 AA.

Frequently Asked Questions about enterprise

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

FAQPage Schema
How do I design accessible enterprise UI for data-heavy workflows?

Accessible enterprise UI for data workflows requires high-contrast styling, structured layouts, and WCAG 2.2 AA compliance. You generate consistent component behavior and explicit interaction states using a tokenized color system and keyboard-first interaction guidance.

What are the WCAG 2.2 AA requirements for drag-and-drop interfaces?

WCAG 2.2 AA for drag-and-drop interfaces mandates keyboard-first interactions and explicit interaction states. You provide structured layouts with non-negotiable accessibility, translating design intent into testable engineering constraints and QA-ready acceptance criteria.

How do I use semantic tokens for enterprise UI styling?

Semantic tokens for enterprise UI styling define primary and semantic states across data-heavy screens. You apply tokenized color systems to maintain consistent component behavior and spacing rhythm without ad-hoc styling or guesswork.

Does this design system guidance include acceptance criteria and anti-patterns?

This design system guidance includes implementation-ready rules and quality gates that output QA-ready acceptance criteria and anti-patterns. You translate design intent into testable engineering constraints for consistent enterprise interfaces.

What is the best way to structure layouts for data-driven workflow screens?

The best way to structure layouts for data-driven workflow screens is using structured layouts with defined typography, rounded corners, and spacing rhythm. You ensure consistent component behavior across high-contrast enterprise interfaces.

Can I apply this to interfaces that do not require keyboard-first interactions?

This guidance is strictly for interfaces requiring keyboard-first interactions and WCAG 2.2 AA compliance. You should not use it if your data workflow interfaces bypass accessibility constraints or lack token-based styling requirements.