agentsclimarketplace

Component inventory

Skill LuchoC-Dev/agent-kits/skills/component-inventory

AI-first workspace bootstrapper — installs skills, packs, agents, and disciplines into .agents/. Cross-compatible with Claude Code and OpenCode.

Install
npx -y skills add LuchoC-Dev/agent-kits --skill component-inventory

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

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 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

Lista todos los componentes UI necesarios clasificados como atoms, molecules y organisms (Atomic Design). Trigger cuando el usuario quiera "inventariar componentes", "listar componentes", "atomic design", "qué componentes necesito" o esté por arrancar el desarrollo de UI y necesite la lista exhaustiva antes de codear.

SKILL.md

2.7 KB, 612 tokens by cl100k_base, as published. Nobody here has run it

Component Inventory

Rol

Sos un design systems engineer. Tu trabajo es identificar todos los componentes UI necesarios y clasificarlos en niveles de Atomic Design antes de implementar.

Precondición

El user-flows aprobado (los flows revelan qué componentes hacen falta). Identificalo por su artefacto, no por el número de prefijo.

Workflow

  1. Leé los flows y la IA.
  2. Para cada pantalla/estado mencionado, identificá los componentes UI presentes.
  3. Clasificalos:
    • Atoms — Button, Input, Label, Icon, Avatar, Badge, Spinner
    • Molecules — FormField (label+input+error), SearchBar, Card, MenuItem
    • Organisms — Navbar, Sidebar, DataTable, Form, Modal, EmptyState
    • Templates — DashboardLayout, AuthLayout, MarketingLayout
  4. Para cada componente, anotá:
    • Variantes (primary/secondary, sm/md/lg)
    • Estados (default, hover, focus, disabled, loading, error)
    • Reutilización (en cuántas pantallas aparece)
  5. Marcá los que ya existen en shadcn/ui, librería de terceros, o si hay que construirlos desde cero.

Output

docs/design/NN-component-inventory.md (NN = prefijo numérico que asigna el workflow según el orden real de ejecución — tomalo de la tabla del workflow):

# Component Inventory

## Atoms

| Componente | Variantes | Estados | Fuente |
|---|---|---|---|
| Button | primary, secondary, ghost, destructive | default, hover, focus, disabled, loading | shadcn |
| Input | text, email, password | default, focus, error, disabled | shadcn |

## Molecules

| Componente | Composición | Usado en |
|---|---|---|
| FormField | Label + Input + ErrorMessage | login, signup, settings |
| SearchBar | Input + Icon + Clear button | dashboard, lista |

## Organisms

| Componente | Composición | Usado en |
|---|---|---|
| Navbar | Logo + NavItems + UserMenu | layout principal |
| DataTable | Header + Rows + Pagination + Filters | listas, reportes |

## Templates

| Layout | Descripción | Pantallas |
|---|---|---|
| DashboardLayout | Sidebar + topbar + main | /dashboard/* |
| AuthLayout | Centered card | /login, /signup |

Regla

Si dos componentes parecen iguales pero con datos distintos, son el mismo componente. No dupliques.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.