ui-style

Enforces consistent frontend styling rules for building and reviewing UI components.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/Angael/veles --skill ui-style-angael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-style
Source: https://github.com/Angael/veles/tree/main/.agents/skills/ui-style
Command: npx skills add https://github.com/Angael/veles --skill ui-style-angael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend codebases drift visually when developers introduce ad-hoc patterns, inconsistent animations, or off-brand components. This Skill keeps every UI change aligned with the existing design system by enforcing concrete styling rules before and during implementation. ## Core Features & Use Cases - Design System Enforcement: Requires reusing theme tokens, breakpoints, and primitives from apps/web/src/components/ instead of inventing new controls or surfaces. - Motion and Interaction Rules: Defines allowed hover/press expressions, transition durations, easing curves, and prefers-reduced-motion handling so animations stay consistent and accessible. - Structured UI Reviews: Produces focused review feedback in a Before | After | Why markdown table verified against real rendered surfaces, viewport sizes, keyboard focus, and reduced motion. - Use Case: When adding a new settings panel to the TanStack Start web app, the Skill ensures you reuse existing primitives, CSS modules, and breakpoint variables rather than introducing raw media queries or new button styles. ## Quick Start Review my new profile page component and make its styling consistent with the existing design system.

Frequently Asked Questions about ui-style

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

FAQPage Schema
How do I keep UI styling consistent across a frontend codebase?

Reuse theme tokens, spacing, typography, and radii from the existing theme.css and CSS modules instead of introducing new values. Import primitives from the components directory and use shared breakpoint variables rather than raw media queries.

How should hover and press states be styled in CSS modules?

Express hover and press with background-color, border-color, color, underline, or opacity only. Never translate, scale, or animate shadows on interactive elements, and gate hover-only behavior with @media (hover: hover) and (pointer: fine).

What transition and animation rules should frontend UI follow?

Never use transition: all; name only changed properties for 100-250ms. Use ease-out for entrances, ease-in-out for movement, avoid scale(0) starts, and honor prefers-reduced-motion by removing positional motion while keeping color feedback.

Does this styling approach support accessibility requirements?

Yes. It mandates at least 40x40px hit areas (ideally 44x44px), stable visible keyboard focus, preserved semantic labels and live-region behavior, and reduced-motion support that retains useful color or opacity feedback.

How should UI review feedback be reported?

Report focused changes in a Before | After | Why markdown table. Verify the actual rendered surface at relevant viewport sizes, interaction states, keyboard focus, and reduced motion rather than reviewing code alone.