ux_template

Generates structured UX documentation for UI screens covering layout, states, accessibility, and mobile behavior.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill ux-template-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux_template
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/ux_template
Command: npx skills add https://github.com/Vimurai/ai-os --skill ux-template-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing or reviewing a UI screen often produces inconsistent, incomplete documentation that misses interaction states, accessibility requirements, or mobile behavior. This Skill provides a repeatable template that captures every critical dimension of a screen in one structured pass. ## Core Features & Use Cases - Structured Screen Documentation: Captures purpose, entry points, layout regions, primary and secondary actions, and keyboard shortcuts for any screen or view. - State & Accessibility Coverage: Documents loading, empty, error, and success states plus ARIA landmarks, focus order, and screen reader announcements. - Dynamic Context Injection: Automatically scans the project for existing React or Vue screens (.tsx, .jsx, .vue) to ground the documentation in the actual codebase. - Use Case: When reviewing a new checkout page, invoke this Skill to produce a complete UX spec covering its layout, error recovery flow, and mobile layout differences before handoff to engineering. ## Quick Start Use the ux_template skill to document the UX of the dashboard screen, including its states, accessibility, and mobile behavior.

Frequently Asked Questions about ux_template

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

FAQPage Schema
How do I document a UI screen's UX systematically?▼

Use a structured template covering purpose, entry points, layout regions, primary and secondary actions, and keyboard shortcuts. This Skill generates that documentation automatically and also captures loading, empty, error, and success states for each screen.

What should a UX screen specification include?▼

A complete UX screen spec includes purpose, entry points, layout regions, interaction states (loading, empty, error, success), keyboard shortcuts, accessibility details like ARIA landmarks and focus order, and mobile layout behavior.

Does this UX template work with React and Vue projects?▼

Yes, the Skill scans the project for .tsx, .jsx, and .vue files matching page, screen, view, or layout naming patterns. This dynamic context injection grounds the generated documentation in the screens that actually exist in the codebase.

How do I document accessibility requirements for a screen?▼

Document ARIA landmark roles, focus order, and screen reader announcements for each screen. This Skill includes a dedicated accessibility section in its template so these requirements are captured consistently during design or review.

When should I not use a UX documentation template?▼

Avoid template-based documentation for non-visual logic such as APIs, background jobs, or data pipelines, since the template assumes screens with layout regions and interaction states. It is designed specifically for user-facing views.