ui-skills

Enforce accessible UI design constraints across Tailwind-based web app components.

55|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/wraps-team/wraps --skill ui-skills-wraps-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-skills
Source: https://github.com/wraps-team/wraps/tree/main/.cursor/skills/ui-skills
Command: npx skills add https://github.com/wraps-team/wraps --skill ui-skills-wraps-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines UI development by codifying constraints into a reusable policy, reducing design drift and inconsistent UX.

Core Features & Use Cases

  • Enforces accessible, keyboard-friendly primitives and consistent interaction patterns across components.
  • Guides animation, layout, and typography decisions to align with Tailwind-based design systems.
  • Use Case: A design team wants consistent, accessible UI surfaces across a multi-page app without reinventing the wheel each time.

Quick Start

Apply these constraints to your UI work by invoking /ui-skills and reviewing results for violations.

Frequently Asked Questions about ui-skills

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

FAQPage Schema
How do I enforce accessible UI design constraints across multiple web app components?

To enforce accessible UI design constraints, apply a reusable policy that codifies keyboard-friendly primitives, ARIA usage, and consistent interaction patterns across components. This reduces design drift and ensures consistent UX without reinventing the wheel each time.

What's the best way to maintain consistent Tailwind defaults and typography across a design system?

Maintaining consistent Tailwind defaults and typography requires codifying constraints into a reusable policy. This guides layout and typography decisions to align with Tailwind-based design systems, streamlining UI development and reducing visual inconsistencies.

How does codifying UI constraints improve component development workflows?

Codifying UI constraints improves component development workflows by reducing design drift and inconsistent UX. It enforces accessible, keyboard-friendly primitives and consistent interaction patterns, allowing teams to build reliable interfaces without reinventing the wheel.

Can I use these UI design constraints for web app prototyping?

Yes, you can use these UI design constraints for web app prototyping. The constraints are applicable to interface design, prototyping, and component development workflows across web apps, enforcing rules for motion usage and accessibility primitives.

Why does my UI design drift across different pages in a multi-page app?

UI design drifts across different pages in a multi-page app due to inconsistent application of design rules. Streamlining UI development by codifying constraints into a reusable policy ensures consistent, accessible UI surfaces across the entire application.

How do I check web app components for accessibility and motion usage violations?

Check web app components for accessibility and motion usage violations by invoking the UI constraints policy and reviewing the results. This process identifies violations against Tailwind defaults, accessible primitives, and consistent layout rules.