Components

Build composable UI with a small public props contract, loading/error/empty states, Reicon icons by default, and mobile-first layout. Use when implementing or refactoring pages, screens, components, dialogs, tables, navigation, “buat component”, “prop terlalu banyak”, “API component”, or “bikin form”. Report Conventions check before done.

9 stars 1 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sukirman1901/frontend-expert

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sukirman1901/frontend-expert --skill components
Manual install
git clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/components ~/.claude/skills/components

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Components

## Overview

A component’s public props are a contract. Prefer composition and project primitives over boolean soup, style knobs, and one-off APIs.

## When to use

- Building or modifying components, pages, interactive controls
- Refactoring overgrown or prop-heavy APIs
- Wiring states, icons, selects, or composition

## When to skip

- Validation mechanics only → `forms`
- Async list/detail fetching only → `data-fetching`
- Grid/spacing of the page → `design-foundations`
- Radius/elevation language → `design-surfaces`
- Generated-hook soup / empty wrappers without an API ask → `anti-slop-code`

## MUST

| Rule | Detail |
|------|--------|
| **Small contract** | Public props are required data, events, and exclusive modes — not a grab-bag of style flags |
| **Compose, don’t configure** | Slots/`children`/subcomponents for optional regions; do not add `showHeader` / `showFooter` / `hasIcon` |
| **Tokens own visuals** | No `color` / `radius` / `shadow` / `padding` props that duplicate tokens |
| **States in the contract** | Loading, error, empty, disabled, invalid are designed, not leftover booleans that collapse the UI |
| **Native-capable controls** | Buttons/inputs forward useful native attributes; icon-only needs an accessible name |
Read the full skill on GitHub

Details

Skill name
components
Path
skills/components/SKILL.md
License
MIT
Repo updated
5 November 2026

FAQ

What does the Components skill do?

Build composable UI with a small public props contract, loading/error/empty states, Reicon icons by default, and mobile-first layout. Use when implementing or refactoring pages, screens, components, dialogs, tables, navigation, “buat component”, “prop terlalu banyak”, “API component”, or “bikin form”. Report Conventions check before done.

How do I install the Components skill?

Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Components popular?

It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.

Related skills

Accessibility

9

sukirman1901/frontend-expert

Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.

Frontend & Design

Anti Slop Code

9

sukirman1901/frontend-expert

Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.

Software Development

Anti Slop Design

9

sukirman1901/frontend-expert

Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.

Frontend & Design

Data Fetching

9

sukirman1901/frontend-expert

Async UI for remote data — loading, error, retry, empty, stale, cache boundaries. Use when building lists, detail pages, dashboards fed by API, React Query/SWR, fetch/loaders, or "ambil data", "loading state API", "retry".

Frontend & Design

App Shell

9

sukirman1901/frontend-expert

App shell, navigation, layouts, breadcrumbs, deep links, 404/empty routes. Use when building dashboard shells, side nav, top nav, multi-page flows, "routing", "layout app", "404", or information architecture for web apps. Requires modern chrome: logo, topbar theme icon, avatar→account menu, custom filter selects — not a bare settings page or native OS selects.

Frontend & Design

Design Color

9

sukirman1901/frontend-expert

Use when creating or repairing a palette, semantic color roles, OKLCH scales, dark mode, contrast pairs, gamut fallbacks, “buat palet”, “warna brand”, “dark theme”, or color that must measurably pass accessibility requirements.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.