uiux-design-principles

Provide consistent, accessible UI/UX guidelines for enterprise frontend applications.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/William189189/boss-bidding --skill uiux-design-principles-william189189
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uiux-design-principles
Source: https://github.com/William189189/boss-bidding/tree/main/.claude/skills/23-uiux-design-principles
Command: npx skills add https://github.com/William189189/boss-bidding --skill uiux-design-principles-william189189

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enterprise frontend work often suffers from inconsistent UX, lack of shared standards, accessibility gaps, and design drift across teams. This skill provides framework-agnostic guidelines to align teams on top-down design, information architecture, visual hierarchy, and responsive patterns, ensuring cohesive, accessible interfaces at scale.

Core Features & Use Cases

  • Framework-agnostic principles for layout, information architecture, accessibility, and responsive patterns
  • Top-down design methodology (layout → features → components → details)
  • Real-world use case: starting a new enterprise UI feature with a shared spec and design tokens
  • Enforces consistency through governance of style tokens, components, and interaction patterns

Quick Start

Apply uiux-design-principles before starting any frontend work to align layout, IA, and accessibility.

Frequently Asked Questions about uiux-design-principles

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

FAQPage Schema
How do I maintain consistent UX and accessibility standards across enterprise frontend teams?

Maintain consistent enterprise UX by applying framework-agnostic guidelines for layout, information architecture, and accessibility. This skill governs style tokens and interaction patterns to prevent design drift and ensure cohesive interfaces at scale across multiple teams.

What is the top-down design methodology for building enterprise UI features?

Top-down enterprise UI design progresses sequentially from layout to features, then to components, and finally to details. This methodology ensures shared specifications and design tokens are established before component-level implementation begins in frameworks like React or Flutter.

Can I apply these UI/UX design principles to both React and Flutter applications?

Yes, these UI/UX design principles are framework-agnostic and apply directly to frontend work in React, Flutter, and similar frameworks. They guide layout decisions, information architecture, and responsive patterns regardless of the underlying technology stack.

How do I start a new enterprise UI feature with a shared spec and design tokens?

Start a new enterprise UI feature by applying these design principles before any frontend coding to align layout, information architecture, and accessibility. This establishes shared specifications and design tokens upfront, enforcing consistency through governance of interaction patterns.

What's the best way to prevent design drift in large-scale frontend applications?

Prevent design drift in large-scale frontend applications by enforcing governance over style tokens, components, and interaction patterns. This skill provides shared standards for visual hierarchy and responsive layouts to ensure interfaces remain cohesive across teams.

What accessibility standards do I need to follow for enterprise application interfaces?

Enterprise application interfaces require accessibility standards governed by framework-agnostic principles that cover responsive layouts and visual hierarchy. This skill aligns teams on these standards to ensure accessible interfaces are consistently implemented at scale.