bklit-studio
bklit-ui monorepo contributors only. Use automatically when building or editing charts, tuning props/animation, or prototyping in Studio (/studio). Replaces the deprecated local /playground route.
- Installs
- 624
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/bklit/bklit-ui --skill bklit-studio- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads bklit-studio automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Bklit Studio Skill (chart development)
Monorepo contributors only. Use this skill automatically whenever you build, edit, or prototype a chart — before shipping via bklit-ship.
Studio at /studio is the single development surface: full editor shell, component tree, properties, motion, codegen, and registry previews. Do not scaffold apps/web/app/playground/.
When to use (auto-trigger)
- Build, prototype, or edit a chart (new or existing)
- Tune props, layers, data, styling, or animation
- Mentions Studio,
/studio, registry preview, or chart controls - Work continues from a prior playground task → use Studio instead
Quick start
pnpm dev # repo root
Open http://localhost:3000/studio (optional query: ?chart=line-chart).
| Task | URL |
|---|---|
| Edit existing chart | /studio?chart=<slug> — slugs in packages/studio/src/chart-slugs.ts |
| Profit/loss line mode | /studio?chart=line-chart&lineChartMode=profitLoss |
Editor layout
| Region | Purpose |
|---|---|
| Left | Chart type (in full Studio), layer list, data controls, animation |
| Center | Canvas, rulers, resizable frame, replay/scramble |
| Right | Properties for the selected layer |
Pane rules: animation → left (motionPanel on chart config); per-layer props → right; visibility → eye icon on layer (uses hiddenComponents in URL state).
Where to implement (existing charts)
Edit the chart in packages/studio and packages/ui — not apps/web/components/playground/.
| Concern | Path |
|---|---|
| Chart preview + codegen | packages/studio/src/lib/registry.tsx (render, generateCode) |
| Layer tree (components panel) | packages/studio/src/lib/studio-components.ts (resolve*Components) |
| Control groups (properties) | packages/studio/src/lib/registry-control-groups.ts |
| URL / default state | packages/studio/src/lib/studio-parsers.ts |
| Chart UI | packages/ui/src/charts/ |
| Slugs | packages/studio/src/chart-slugs.ts + studioRegistry in registry.tsx |
| Studio-only previews | packages/studio/src/components/charts/*-studio-preview.tsx |
Patterns in registry.tsx render
Reuse committed helpers (do not reimplement):
StudioChartShell+studioCartesianLegendItems— legend grid +showLegendStudioVisibleLayer+componentId— ties render to layer visibility (line.grid,line.series.0, …)getStudioCssRevealPropsForPreview— motion / revealisStudioComponentVisible(state, componentId)— conditional childrenseriesStrokePropsFromState,fadeEdgesPropValue,chartTooltipPropsFromState
Reference implementation: lineConfig.render in registry.tsx.
New chart (not in registry yet)
- Implement component(s) in
packages/ui/src/charts/(minimal API first). - Add slug to
packages/studio/src/chart-slugs.ts. - Add
StudioChartConfigtostudioRegistryinregistry.tsx:render(state, ctx)— preview insideEditorChartFrameviaStudioShellresolveComponentsinstudio-components.tscontrolGroups/resolveControlGroupsgenerateCodefor the code sheet
- Open
/studio?chart=<new-slug>and iterate. - When stable, follow bklit-ship for docs, gallery, shadcn registry.
Adding a prop or layer
- Add key to
StudioUrlState/defaultStudioStateinstudio-parsers.tsif missing. - Add control(s) on the right layer in
registry-control-groups.tsor per-componentcontrolGroupsinstudio-components.ts. - Wire prop in
registry.tsxrender(and inpackages/uichart code). - If the prop affects animation → ensure
motionPanel: trueon chart config. - Verify in Studio: layer list, visibility toggle, properties, replay.
Shipping
When the API is stable, read .agents/skills/bklit-ship/SKILL.md — prototype code should already live in packages/ui + packages/studio; no playground route to migrate.
Deprecated: /playground
The local /playground route and bklit-playground skill are deprecated. /playground redirects to /studio. Do not copy playground-editor-shell or apps/web/components/playground/ for new work.
File reference
| Item | Path |
|---|---|
| Studio app route | apps/web/app/studio/page.tsx (StudioShell) |
| Studio package | packages/studio/ |
| Studio skill | .agents/skills/bklit-studio/SKILL.md |
| Ship checklist | .agents/skills/bklit-ship/SKILL.md |
| Performance audit | .agents/skills/bklit-studio-chart-performance/SKILL.md |
FAQ
What does the bklit-studio skill do?
bklit-ui monorepo contributors only. Use automatically when building or editing charts, tuning props/animation, or prototyping in Studio (/studio). Replaces the deprecated local /playground route.
How do I install bklit-studio?
Run npx skills add https://github.com/bklit/bklit-ui --skill bklit-studio in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/bklit-studio/ (personal) or .claude/skills/bklit-studio/ (project).
Which AI agents can use bklit-studio?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is bklit-studio safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains bklit-studio?
It is published by bklit in bklit/bklit-ui. It has 624 recorded installs.
More from bklit/bklit-ui
bklit-ui
bklit/bklit-ui
Install, compose, theme, and animate Bklit UI charts (the @bklit shadcn registry) in a React / Next.js app. Use when the user wants a chart, graph, or data visualization: line, area, bar, live/streaming line, composed, scatter, candlestick/OHLC, pie, ring/donut, radar, gauge, heatmap, funnel, sankey, sunburst, or choropleth/world map; a sparkline or tiny inline chart (LineSparkline, AreaSparkline, BarSparkline, useSparklineHover) for tables, KPI cards, or dense dashboards; a dashboard, analytics page, KPI or stat card; chart tooltips, crosshairs, legends, markers, reference bands, projections, trend lines, axes, or grids; or when code imports from components/charts/ or mentions @bklit/ or bklit.com. For styling vocabulary (patterns, squircle/rounded/3D bars, fades, loading looks, matching the app theme) also use bklit-ui-design. For moving from Recharts, shadcn ChartContainer, or TanStack Charts to Bklit, use bklit-ui-migrate.
unit-tests
bklit/bklit-ui
Guardrails for adding unit tests in bklit-ui without over-testing. Use when the user mentions unit test, unit tests, tests, test coverage, add tests, write tests, vitest, jest, or asks whether something should be tested.
bklit-studio-chart-performance
bklit/bklit-ui
Reusable Studio chart performance audit and fix workflow. Use when a chart feels sluggish in /studio (pan, slider ticks, legend hover) but siblings like pie-chart feel fine.
turborepo
bklit/bklit-ui
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
bklit-ship
bklit/bklit-ui
bklit-ui monorepo contributors only — ship a chart or component from Studio prototype to production in packages/ui with docs and registry.
bklit-playground
bklit/bklit-ui
DEPRECATED — use bklit-studio instead. Local /playground is no longer the chart development workflow for bklit-ui contributors.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.