AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Compound Ui

skill-dobroslavradosavljevic-skills-compound-ui · by DobroslavRadosavljevic

Build, review, or refactor React UI components into shadcn-style compound components. Use when creating composable component APIs, splitting prop-heavy components into named parts, wrapping Radix/Base UI primitives, adding asChild/Slot behavior, designing data-slot styling hooks, or enforcing accessible source-owned component primitives.

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-dobroslavradosavljevic-skills-compound-ui

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-dobroslavradosavljevic-skills-compound-ui)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Compound Ui? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Compound UI

Use this skill to create source-owned React components that compose like shadcn/ui: small named parts, explicit children, accessible primitives, class merging, and stable styling hooks.

Workflow

  1. Inspect the local UI stack before writing code:
  • Read nearby project guidance, existing component files, package versions, styling utilities, primitive libraries, and test/story conventions.
  • Prefer the project's existing export, file, styling, icon, and accessibility patterns.
  1. Refresh docs when exact APIs matter:
  • Use [references/source-map.md](references/source-map.md) for current source links and captured guidance.
  • Prefer current React, shadcn/ui, Radix UI, and local primitive docs before changing framework-sensitive code.
  1. Design the public API before implementation:
  • Read [references/component-contract.md](references/component-contract.md).
  • Define the root component, named subcomponents, legal nesting, controlled/uncontrolled state, and required accessibility parts.
  1. Implement in the shadcn style:
  • Read [references/authoring-patterns.md](references/authoring-patterns.md).
  • Export source-owned named parts with data-slot, className merging, prop/ref pass-through, and minimal behavior props.
  1. Review before finishing:
  • Use [references/review-checklist.md](references/review-checklist.md).
  • Verify typecheck, lint, story/browser behavior, keyboard support, focus, accessible names, and responsive states when relevant.

Enforcement Rules

  • Prefer compound parts and children over prop-heavy wrapper APIs. Do not create title, description, actions, icon, isLoading, or layout props when named subcomponents express the same structure better.
  • Keep acceptable props narrow: DOM props, className, children, asChild, controlled state, event handlers, accessibility props, and intentional variants such as variant or size.
  • Use existing accessible primitives for complex behavior such as dialogs, menus, popovers, tabs, selects, tooltips, comboboxes, accordions, and roving focus.
  • Preserve primitive contracts. Custom slotted children must spread incoming props and support refs according to the project's React version.
  • Add data-slot to every exported part, plus state/variant data attributes when useful for styling and tests.
  • Keep state local unless parts must coordinate. Use scoped context only for compound coordination and fail loudly when a required part is used outside its root.
  • Add "use client" only when the component uses hooks, events, browser APIs, or client-only primitives.
  • Do not hide required accessibility behind convenience defaults that callers cannot inspect or override.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.