Ui component

Skill syniol/llm-software-project/.agent/skills/ui-component

AI Ready Software Template for Enterprise Multi-Model AI Context Architecture

Install

npx -y skills add syniol/llm-software-project --skill ui-component

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Instructions for creating UI components following the design system, accessibility standards, and file structure conventions.

SKILL.md

1.8 KB, as published. Nobody here has run it

UI Component Creation Skill

When creating a new UI component, follow this procedure exactly:

1. File Structure

Every component must produce these files:

components/
└── MyComponent/
    ├── MyComponent.tsx          # Component implementation
    ├── MyComponent.test.tsx     # Unit tests (React Testing Library)
    ├── MyComponent.stories.tsx  # Storybook stories
    └── index.ts                 # Barrel export

2. Props Interface

Define a Props interface with JSDoc on every prop.
Export the interface for consumer use.

/** Props for the MyComponent component. */
export interface MyComponentProps {
  /** The primary label displayed to the user. */
  label: string;
  /** Optional click handler. */
  onClick?: () => void;
  /** Visual variant. Defaults to 'primary'. */
  variant?: 'primary' | 'secondary' | 'ghost';
}

3. Accessibility (WCAG 2.1 AA)

All interactive elements must have aria-label or visible label text.
Colour contrast ratio must be at least 4.5:1 for normal text, 3:1 for large text.
Support keyboard navigation (Tab, Enter, Escape).
Include role attributes where semantic HTML is insufficient.

4. Design System Tokens

Use design tokens for all colours, spacing, typography, and radii. Never hardcode values.
Example: var(--color-primary), var(--spacing-md), var(--radius-lg).

5. Responsive Breakpoints

Breakpoint	Min Width	Target
`sm`	640px	Mobile
`md`	768px	Tablet
`lg`	1024px	Small Desktop
`xl`	1280px	Large Desktop

Gives 0 of the 12 instructions most ui components skills give

Counted across 343 of the 344 authors here whose files we hold, read 2026-08-06

Make touch targets at least 44x44 pixelsin 48 of 343, across 17 files
Use SVG icons instead of emojisin 39 of 343, across 12 files
Ensure minimum color contrast of 4.5:1in 36 of 343, across 9 files
provide visible focus rings on interactive elementsin 26 of 343, across 10 files
Use semantic color tokens instead of raw hex codesin 26 of 343, across 10 files
Generate a design system before codingin 23 of 343, across 6 files
Respect prefers-reduced-motion user settingsin 22 of 343, across 6 files
use semantic html elementsin 21 of 343, across 14 files
use semantic tailwind colorsin 19 of 343, across 6 files
Match style to product type and industryin 18 of 343, across 2 files
use consistent design tokensin 18 of 343, across 6 files
build complex interfaces from composable primitivesin 18 of 343, across 6 files

Said here and by no other author read

follow the procedure exactly
create the component implementation file
create the unit test file
define a Props interface with JSDoc

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.