agentsclimarketplace

Building components

Skill jgamaraalv/delivery-loop/.claude/skills/building-components

Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready

Install
npx -y skills add jgamaraalv/delivery-loop --skill building-components

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

One thing to look at

  • 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

Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.

SKILL.md

3.0 KB, as published. Nobody here has run it

Building Components

References

Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).

  • references/definitions.mdx — artifact taxonomy: primitives, components, blocks, templates and when to use each · read when choosing the right abstraction level for a new component.
  • references/principles.mdx — core component design principles: single responsibility, composition over configuration, minimal API surface · read when designing a new component's API.
  • references/accessibility.mdx — ARIA roles/attributes, keyboard navigation, focus management, WCAG compliance patterns · read when implementing interactive or custom-widget components.
  • references/composition.mdx — slot patterns, render props, controlled/uncontrolled state, compound components · read when designing composable component APIs.
  • references/as-child.mdx — the Radix-style asChild pattern for element polymorphism without wrapper divs · read when implementing asChild or polymorphic roots.
  • references/polymorphism.mdx — as prop, generic polymorphic components, TypeScript inference for polymorphic types · read when a component must render as different HTML elements.
  • references/types.mdx — TypeScript typing patterns: discriminated unions, generic props, ComponentPropsWithoutRef, forwardRef · read when typing component props or forwarding refs.
  • references/state.mdx — controlled vs uncontrolled state, useControllableState, default value patterns · read when deciding how a component should own or delegate its state.
  • references/data-attributes.mdx — using data-* attributes for CSS state, testing hooks, and styling variants · read when styling component states or wiring tests.
  • references/design-tokens.mdx — CSS custom property token systems, theming, dark mode, token naming conventions · read when setting up or extending a design token layer.
  • references/styling.mdx — CSS Modules, Tailwind, CSS-in-JS, class variance authority (CVA), style encapsulation · read when choosing or implementing a component styling approach.
  • references/registry.mdx — shadcn/ui-style registry distribution, components.json, CLI-installable components · read when publishing via a component registry.
  • references/npm.mdx — npm package publishing: entry points, bundling, peer deps, package.json fields · read when shipping a component library to npm.
  • references/marketplaces.mdx — component marketplace distribution (Shadcn registry, v0, etc.) · read when distributing components via a marketplace.
  • references/docs.mdx — writing component documentation: prop tables, usage examples, Storybook stories · read when documenting a component for end users.

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.