mcpField
U
ui-skills

ui-skills

github.com/sickn33Design & UI48.7k605 installsUpdated 1d ago
Repository

About ui-skills

ui-skills is a skill for agents building or reviewing interfaces, using selected UI guidance to assess layout, interaction, and accessibility while preserving the project’s design language.

Key features

  1. 01Guidance for interface-building agents
  2. 02Select relevant UI procedures
  3. 03Review layout and interactions
  4. 04Check accessibility concerns
  5. 05Verify changes with project checks

Use cases

  1. 01Review an interface for high-impact design issues
  2. 02Plan implementation-ready UI improvements
  3. 03Validate changes against project design language

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill ui-skills

After installing, type/ui-skillsin Claude Code to confirm it loaded.

Details

From the project README

Ui Skills

Overview

Opinionated, evolving constraints to guide agents when building interfaces

When to Use This Skill

Use this skill when you need to work with opinionated, evolving constraints to guide agents when building interfaces.

Procedure

This entrypoint links to an external UI guidance collection; it does not contain the complete upstream rules. Inspect the requested interface, existing design system, target devices and accessibility requirements. Select the relevant installed procedure or read the complete chosen upstream guide before applying it. Report observed layout, interaction and accessibility problems with locations and suggested corrections. Preserve the project design language and verify changes with the actual renderer and project checks. Do not claim an unavailable guide or visual inspection ran.

Source: UI Skills.

Example

User request:

Review this interface with @ui-skills, identify the highest-impact design problems, and propose an implementation-ready improvement.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported