51 tagged component library, measured the same way as everything else here.
Browse within: accessibility 26frontend-platform 16monorepo 16ui-architecture 16workspace 16components 5library 5reactjs 5
Agent Claude Code
Use this agent when you need to review, improve, or curate documentation files in the /apps/docs/content directory. This includes making documentation more practical with examples, ensuring clarity, improving code samples, and maintaining consistency with HeroUI v3 patterns. Context: User wants to improve…
Agent Claude Code
Use this agent when you need to create or update technical documentation for HeroUI v3 components, features, or guides. This includes component API documentation, usage examples, installation guides, migration guides, and conceptual explanations. The agent follows HeroUI's specific documentation style guide…
Agent Claude Code
Use this agent when you need to migrate HeroUI components from TypeScript-based styles (.styles.ts files using tailwind-variants) to CSS-based styles (.css files) following the BEM naming convention. This includes converting tv() configurations to CSS classes, maintaining variant mappings, and ensuring all visual…
Agent Claude Code
Adversarial senior design critic. Renders the work, looks at it, and argues for rejection. Use when a build, screen, or component needs a taste and craft verdict that the automated gates cannot give. Runs after the gates are green, never instead of them.
Agent
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
Agent
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
Agent
Issues and PRDs for this repo live as markdown files in .scratch/.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Agent Claude Code
Data architect owning schema design, migrations, and data-flow boundaries — what crosses process, network, and persistence boundaries. For rea, owns the audit-log shape, last-review.json schema, policy.yaml field evolution, and audit hash-chain semantics. Designs the model that backend-engineer builds against.
Agent Claude Code
Developer-experience architect owning the consumer install topology, doctor diagnostics, error-message shape, and idempotency invariants. For rea, owns rea init / rea upgrade install behavior, rea doctor output, hook error strings consumers see when a gate refuses, and the "rea init twice produces byte-identical…
Agent Claude Code
Platform architect owning build, CI, packaging, and publish pipeline integrity. For rea, owns GitHub Actions workflows, npm publish provenance, tarball-smoke gate, Changesets VP flow, the pnpm test script chain, and vitest pool/IPC config. Designs the pipeline that release-captain ships through.
brianmontanaweb/agentic-design-system
Agent
Agent "CHANGELOG" from brianmontanaweb/agentic-design-system, covering @agentic-ds/agents, 0.2.0 and patch changes.
Agent Claude Code
Each file here defines the prompt for one isolated sub-agent. The orchestrator (/component-create) invokes them via the Task tool, one phase at a time. A sub-agent sees only the prompt the orchestrator hands it — no conversation history, no other sub-agent's output, no chat memory. This is the structural guarantee…
Agent Claude Code
Isolated sub-agent that writes the component .vue files + updates packages/webkit/package.json#exports. Strictly spec-bound; every prop/event/slot must come from the spec.
Agent
Runs and explains the @aziontech/webkit adoption flow — npx @aziontech/webkit init. Sets up deps, lint configs, pre-commit, the webkit MCP, and the Claude Code bundle in this project, idempotently.