ui-review

Audit UI code for StyleSeed Toss design-system compliance and accessibility.

25|6|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-review-krishna0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-review
Source: https://github.com/KRISHNA0R/PORTFOLIOv2/tree/main/.agents/skills/ui-review
Command: npx skills add https://github.com/KRISHNA0R/PORTFOLIOv2 --skill ui-review-krishna0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits UI code for StyleSeed Toss adoption, ensuring design-token discipline, component ergonomics, accessibility, mobile readiness, typography, and spacing consistency.

Core Features & Use Cases

  • Design-token discipline checks and consistency
  • Accessibility audits including keyboard focus, color contrast, and screen-reader hints
  • Mobile readiness guidance and typography/spacing alignment

Quick Start

Inspect a UI PR against StyleSeed Toss guidelines and request concrete fixes to align with the seed.

Frequently Asked Questions about ui-review

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

FAQPage Schema
How do I audit UI code for design-system compliance and accessibility?

This Skill audits UI code for design-system compliance by analyzing frontend against StyleSeed Toss guidelines, evaluating design tokens, spacing, typography, keyboard focus, and color contrast to return a prioritized list of fixes.

What does a design-token consistency check cover for component libraries?

A design-token consistency check ensures component libraries adhere to StyleSeed Toss guidelines by evaluating token discipline, spacing alignment, and typography to identify and prioritize necessary corrections.

Can I use this to check mobile readiness and keyboard accessibility in a PR review?

Yes, you can use this Skill for PR reviews to check mobile readiness and keyboard accessibility, as it evaluates mobile ergonomics, keyboard focus, and screen-reader hints across web apps adopting StyleSeed guidelines.

What is the best way to fix color contrast and screen-reader issues in frontend code?

The best way to fix color contrast and screen-reader issues is to run a UI audit that analyzes frontend code and returns a prioritized list of concrete accessibility fixes aligned with your design system.

Do I need existing design tokens to run a UI audit on my web app?

You need existing frontend code utilizing design tokens, as this Skill evaluates design-token discipline and consistency against the StyleSeed Toss guidelines to generate its prioritized fixes.