⚠
High Risk:This skill has significant security concerns. Review the findings below before installing.
building-components
⚠Caution·Scanned 2/18/2026
High-risk skill: Documentation for building UI components that includes explicit CLI install commands such as npx shadcn@latest and npm install which download and execute external packages. It also references external endpoints like https://21st.dev/r/haydenbleasel/dialog-stack and https://your-project-name.vercel.app/metric-card.json.
Scanned from main at f97206c · Transparency log ↗
$ vett add vercel/components.build/building-componentsReview security findings before installing
Building Components
When to use this skill
Use when the user is:
- Building new UI components (primitives, components, blocks, templates)
- Implementing accessibility features (ARIA, keyboard navigation, focus management)
- Creating composable component APIs (slots, render props, controlled/uncontrolled state)
- Setting up design tokens and theming systems
- Publishing components to npm or a registry
- Writing component documentation
- Implementing polymorphism or as-child patterns
- Working with data attributes for styling/state
References
- definitions.mdx - Artifact taxonomy (primitives, components, blocks, templates)
- principles.mdx - Core principles for component design
- accessibility.mdx - ARIA, keyboard navigation, WCAG compliance
- composition.mdx - Composable component patterns
- as-child.mdx - The as-child pattern for element polymorphism
- polymorphism.mdx - Polymorphic component patterns
- types.mdx - TypeScript typing patterns for components
- state.mdx - Controlled vs uncontrolled state management
- data-attributes.mdx - Using data attributes for styling and state
- design-tokens.mdx - Design token systems and theming
- styling.mdx - Component styling approaches
- registry.mdx - shadcn-style registry distribution
- npm.mdx - Publishing components to npm
- marketplaces.mdx - Component marketplace distribution
- docs.mdx - Writing component documentation