con un clic
elements
elements contiene 12 skills recopiladas de crafter-station, con cobertura ocupacional por repositorio y páginas de detalle dentro del sitio.
Skills en este repositorio
Browse and install components from the Elements registry (tryelements.dev). Use when user asks about available components, wants to explore providers, says "elements", "component library", "what components", "install from registry", "tryelements", or needs to find the right component category.
Install CC0 sound effects from the Elements registry. Use when user needs UI sounds (click, pop, notification), transition sounds (whoosh, swoosh), cinematic sounds (boom, riser, glitch), or audio for video production. Triggers on "sound effect", "SFX", "audio", "notification sound", "click sound", "whoosh", "UI sound", "sound for video", "play sound", "useSound".
Install Polar monetization components from the Elements registry. Use when user needs pricing cards, sponsor grids, subscription badges, revenue displays, or license key inputs. Triggers on "polar", "monetization", "pricing card", "subscription badge", "sponsor grid", "license key", "revenue card", "sponsorship", "pricing page".
Install theme switcher components from the Elements registry. Use when user needs dark mode toggles, theme switchers, light/dark buttons, or theme dropdowns. Triggers on "theme switcher", "dark mode", "light mode", "theme toggle", "theme button", "switch theme", "dark mode toggle".
Install Upstash serverless components from the Elements registry. Use when user needs rate limit displays, Redis counters, leaderboards, queue status cards, or cache badges. Triggers on "upstash", "rate limit", "redis counter", "leaderboard component", "queue card", "cache badge", "serverless redis".
Install developer tool components from the Elements registry. Use when user needs JSON viewers, API response displays, code diff viewers, CLI output renderers, env editors, error boundaries, webhook testers, or schema viewers. Triggers on "devtools", "json viewer", "API response", "webhook tester", "env editor", "code diff", "schema viewer", "error boundary", "CLI output".
Install GitHub display components from the Elements registry. Use when user needs GitHub repo cards, profile cards, contribution calendars, star counters, language breakdowns, or activity displays. Triggers on "github component", "github card", "repo card", "contributions calendar", "github stars", "github profile", "github activity", "github languages", "star button".
Install UploadThing file upload components from the Elements registry. Use when user needs file uploads, drag-and-drop dropzones, avatar uploads, file cards, image grids, paste-to-upload, or upload progress indicators. Triggers on "upload", "file upload", "dropzone", "uploadthing", "drag and drop upload", "image grid", "paste upload", "avatar upload".
Install AI UI components from the Elements registry. Use when user needs chat interfaces, agentic UIs (tool calls, reasoning, plans), multi-agent dashboards, or AI devtools. Triggers on "AI component", "chat UI", "agent UI", "tool call component", "streaming text", "agentic", "multi-agent", "AI SDK", "chat input", "message bubble", "thinking indicator".
Create new UI elements for tryelements.dev registry. Use when: (1) Adding new UI components (buttons, inputs, cards), (2) Building integration components (Clerk, Stripe, Uploadthing), (3) Creating theme-related elements, (4) Any shadcn-style registry component. IMPORTANT: For logo components with variants (icon/wordmark/logo + dark/light), use the logo-with-variants skill instead. This skill includes scaffolding, registry schema, and component patterns. ALWAYS use Context7 MCP to fetch latest dependency docs before implementing.
Install official tech brand logos from the Elements registry. Use when user needs logos for tech companies (Clerk, Vercel, GitHub, etc.), AI providers (OpenAI, Anthropic, Claude), social platforms, or any brand assets. Triggers on "logo", "brand", "icon for [company]", "add [company] logo", placeholder logo detection, or when building landing pages, auth UIs, or integrations showcases.
Create logo components with multiple variants (icon, wordmark, logo) and light/dark modes. Use when the user provides logo SVG files and wants to create a variant-based logo component following the Clerk pattern in the Elements project.