Loading...
Loading...
Found 12 Skills
SolidJS renderer for json-render. Use when building @json-render/solid catalogs/registries, wiring Renderer providers, implementing bindings/actions, or troubleshooting Solid-specific reactivity patterns.
Create a new Tambo generative UI app from scratch. Use for brand-new projects where users describe UI in natural language. For existing apps, use build-with-tambo.
Configures preprocessors, postprocessors, and runners around InferenceModel via manifest specs and ComponentRegistry. Use when editing physicalai.inference.preprocessors or postprocessors, manifest preprocessor/postprocessor lists, instantiate_component, registered type names, or class_path init_args for inference pipeline components.
Vue 3 renderer for json-render. Use when building Vue UIs from JSON specs, working with @json-render/vue, defining Vue component registries, or rendering AI-generated specs in Vue.
Build or modify reusable registry content for board designers. Use when fulfilling a librarian request or when asked to add/fix a registry component, symbol, footprint, STEP model, datasheet, family selector, or datasheet-backed Zener reference circuit. Covers artifact import, symbol/footprint cleanup, package structure, sourceability, and validation.
Integrates Tambo into EXISTING React projects by detecting the tech stack and adapting installation. Use when adding Tambo to an existing app, integrating with current frameworks, or when the user has an existing codebase they want to add AI/generative UI to. For starting a NEW project from scratch, use start-from-scratch skill instead. For registering existing components, use add-components-to-registry skill.
Register components in registry.json for shadcn/ui add command. Apply when adding new 8-bit components to the component library.
Register 8-bit components in registry.json for shadcn/ui add command. Apply when adding new components to the component library distribution.
Version-pinned inventory of the telemetry (spans, metrics, logs, attributes) emitted by OpenTelemetry collector components and SDK instrumentation packages. Use when working with a covered component — what it emits at a given version, or how emission changed across versions — and when upgrading a component or SDK version, to see the telemetry after the change.
Build React UIs with Fluid Functionalism — a shadcn/ui registry (@fluid) of animated components with a shared motion system: three spring speeds, a hover highlight that glides to the item nearest the cursor, labels that change weight without layout shift. Use whenever the user mentions Fluid Functionalism, @fluid, or fluidfunctionalism.com, asks for UI with satisfying/fluid/polished motion in a React, Next.js, shadcn, Radix, or Base UI project, builds any interface (settings dialogs, sidebars, command menus, chat UIs, forms, lists, tables) in a project with @fluid components installed, or asks to review/audit existing UI motion against the system. Also use before hand-writing animation code (hover highlights, icon swaps, weight changes, enter/exit transitions) there, so custom code follows the system instead of inventing timings. Each run, a bundled script reads the stack fresh (deps, Radix vs Base UI flavor, MotionConfig, Inter opsz axis), so the skill leaves no audit file in the project.
Build UI with Cubix, the copy-paste React component registry. Use when the project has a cubix.json, imports from components/cubix, or the user asks to add, compose, theme, or publish Cubix components, blocks, or registry items with the cubix-ui CLI.
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system building blocks.