ui-skills_skill

This skill enforces opinionated UI constraints for building accessible, performant interfaces with agents, covering components, animation, layout, and
  • TypeScript

30

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vaayne/agent-kit --skill ui-skills

  • SKILL.md2.9 KB

Overview

This skill provides opinionated constraints and best practices for building consistent, accessible, and performant interfaces for AI agents. It packages a focused UI prescription—layout, components, animation, typography, and performance rules—so teams can ship cohesive agent UIs quickly. The guidance is TypeScript- and Tailwind-first and favors established primitives and motion libraries.

How this skill works

The skill defines a set of MUST/SHOULD/NEVER rules that guide implementation choices: which CSS tokens to use, which component primitives to prefer, how to handle animation and accessibility, and which layout and performance patterns to avoid. It inspects UI decisions and offers concrete prescriptions (e.g., use AlertDialog for destructive actions, prefer Base UI primitives, animate only compositor properties) so code and designs remain predictable.

When to use it

  • Building or auditing agent-facing interfaces where consistency and accessibility are priorities
  • Starting a new UI module that will be reused across multiple agent subagents
  • Integrating animation or motion and needing clear constraints to preserve performance
  • Defining component libraries or design-system rules for agent UIs
  • Enforcing keyboard and focus behavior for interactive surfaces

Best practices

  • Use Tailwind defaults first (spacing, radius, shadows) and extend only when necessary
  • Prefer existing project primitives; default to Base UI for new primitives when compatible
  • Always add aria-labels to icon-only buttons and rely on accessible primitives for focus
  • Animate only transform and opacity, respect prefers-reduced-motion, and cap interactions at 200ms
  • Show errors inline, provide a clear next action for empty states, and respect safe-area-inset for fixed elements

Example use cases

  • Creating a chat pane for an assistant that respects keyboard focus, animation limits, and safe areas
  • Building a reusable AlertDialog pattern for destructive operations across agent tools
  • Designing loading skeletons and small entrance animations using tw-animate-css and motion/react
  • Auditing an existing UI to remove expensive paint animations, arbitrary z-indices, and forbidden effects like primary glows
  • Extending a component library while ensuring consistent typography (text-balance, text-pretty, tabular-nums)

FAQ

Only compositor properties—transform and opacity—should be animated; avoid layout or expensive paint properties.

Which component primitives should I use?

Use the project’s existing primitives first; prefer Base UI for new primitives when compatible, and never mix primitive systems on the same interaction surface.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational