Skip to content
cccskills
FreePublished on GitHub

shadcn-ui

Build app interfaces with the UI controls already provided by the project. Choose and compose form fields, menus, dialogs, and other components, following local variants, theme tokens, accessibility patterns, and wrapper APIs.

OriginalShow the original description

Using the app's local UI adapter and Toolkit or shadcn primitives. Use when choosing or composing standard controls, implementing dialogs, menus, or forms, or changing component variants and theme tokens.

BuilderIO/agent-native7,525 stars(GitHub 7,525 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Choose controls for a new form or setting
  • Add an accessible dialog or menu using existing components
  • Adjust component variants and semantic theme tokens
  • Compose tabs, cards, and fields from the app's UI primitives

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

shadcn/ui and Local UI Adapters

Use the components already provided by the app. Read the app's design-system configuration, Toolkit provider, and local UI components before adding or changing a control. Their exports, variants, and props are the contract; do not guess from upstream examples.

Keep imports behind the local adapter

Product pages and domain components should import standard controls through the app's configured local UI alias. In the Chat starter, that is @/components/ui/*; its app/components/ui/button.tsx is a one-line re-export of @agent-native/toolkit/ui/button. Follow an adjacent local shim when the app needs another Toolkit primitive that is already exported there.

Use the app's configured design system and provider mapping for controls passed to shared Toolkit surfaces. For shared Toolkit feature presentation, use the semantic components exposed by @agent-native/toolkit/design-system; keep the feature behavior in its existing controller and customize only its supported presentation seam.

Compose existing controls

  • Prefer a primitive's built-in variant and size. Put page layout on a parent instead of overriding shared component appearance for one screen.
  • Use the app's semantic theme tokens for reusable UI, such as bg-background, text-muted-foreground, border-border, and bg-primary. Keep theme values in the app's existing CSS theme file.
  • Use the control that matches the choice: Switch for a binary setting, Checkbox for independent multi-select, RadioGroup for one choice from a short set, and Select or the app's combobox for a longer predefined list.
  • Compose cards and form fields from the primitives already available. Avoid adding explanatory copy that repeats a visible title or label; see frontend-design for the app's surface-density rules.
  • Put selectable items inside their menu or list group primitives. Keep tab triggers inside the tab list. Supply an accessible title to dialog, sheet, drawer, and alert-dialog content.
  • Match the trigger API to the actual local component. Toolkit wrappers may expose a different API from the upstream primitive; inspect its props before using options such as asChild or render.

Keep controls operable

Use the app's existing field components and validation pattern. Associate errors with their inputs and expose invalid state to assistive technology. Icon-only actions need an accessible name and a usable focus target. Use the icon package already installed by the app.

Do not recreate menus, popovers, dialogs, or confirmations with absolute positioning and custom click-outside handlers. Never use browser alert, confirm, or prompt; use the app's dialog primitives. Keep overlay focus, keyboard, dismissal, and stacking behavior from the existing primitive.

For small visual refinements, use layout classes and semantic tokens. Avoid raw palette overrides, arbitrary one-off values, and manual overlay z-index unless you are fixing a reproduced bug. Use gap-* for layout spacing and the app's class-merging helper when it has one.

Related skill

  • frontend-design — Product UX, density, visual direction, and responsive behavior.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a2a-assets

FreeSummary

Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.

  • Generate brand images for slides or another app
  • Refine an existing asset after feedback
  • Create and export a video asset
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

account-health

FreeSummary

Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.

  • Preparing a named customer's account health review
  • Comparing contracted seats or capacity with usage
  • Gathering adoption signals before a renewal or QBR
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

actions

FreeSummary

Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.

  • Adding a new app operation
  • Connecting an external provider API
  • Fetching data for a frontend view
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

adding-a-feature

FreeSummary

Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.

  • Planning a new feature across UI and agent actions
  • Checking that agent changes appear in the UI
  • Documenting actions and feature state for the agent
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

adhoc-analysis

FreeSummary

Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.

  • Comparing CRM deals with call records
  • Investigating customer health across systems
  • Saving a repeatable performance analysis
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

admin-surfaces

FreeSummary

Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.

  • Review dashboard owners, views, and edits
  • Change a workspace feature flag for an app
  • Browse or edit a connected app database
BuilderIO/agent-native7.5KUpdated Oct 26, 2026

See all skills by BuilderIO

Report a problem with this skill