bklit-ui-design
Turns plain-language chart design requests into exact Bklit UI (@bklit shadcn registry) components and props, styled to fit the host app. Use when someone describes how a chart should look rather than naming props, e.g. "diagonal pattern background that fades out", "squircle bars", "3D glass bars", "hatched area", "dot grid", "skeleton loading state", "dashed forecast", "half donut", "make the charts match my brand / dark mode / border radius". Detects the project's Tailwind version, colour format, dark-mode strategy, radius and existing chart tokens, then picks a proven recipe, installs the right @bklit/ , adapts colours to theme tokens and states honestly when Bklit has no prop for the request. Also use when theming or restyling Bklit charts.
- Installs
- 88
- Last 24h
- +12
- Trending rank
- #8076
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/bklit/bklit-ui --skill bklit-ui-design- 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-ui-design 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 UI design
Map what people say ("a hatched backdrop that fades at the edges") to what
Bklit has (<Background />), then make it look native to the app it lands in.
Bklit charts are installed as source with npx shadcn@latest add @bklit/<item>
(use the project's runner: pnpm dlx, bunx --bun, …) and imported from the
project's alias, e.g. @/components/charts/background. Never import from
@bklitui/ui/charts — that is the private monorepo package.
Workflow
1. Detect the host design
Run the bundled detector from the user's project root. <skill-dir> is the
folder containing this SKILL.md (commonly .claude/skills/bklit-ui-design,
.agents/skills/bklit-ui-design or ~/.claude/skills/bklit-ui-design):
node <skill-dir>/scripts/detect-design.mjs
Zero dependencies, Node ≥ 18, never throws. It prints JSON: tailwindVersion,
cssPath, colorFormat, darkMode, tokens (--primary, --radius, …),
chartVars (light/dark --chart-*), themeInline, components (from
components.json), primitives, chartLibs, bklit.installed and
warnings. Agents without shell access: read components.json, the global CSS
file it names, and package.json, and collect the same facts by hand.
Read warnings first — they flag the problems that make charts look broken
(gray default palette, Tailwind v3 bare-HSL tokens, missing @theme mappings).
2. Parse the request into design intents
Split the sentence into intents (background, fade, shape, fill, line, markers, tooltip, grid, legend, loading, motion, annotation) and look each up in references/vocabulary.md. Example:
"squircle bars with a ghost track and a ring on hover" → shape:
BarSquares squareRadius={0.5}+BarChart squareSnap· track:BarColumnTrack· tooltip:ChartTooltip dotVariant="ring" dotRadiusFraction={0.5}
"diagonal pattern background that fades out on all sides" →
<Background />(diagonal and 4-side fade are the defaults)
3. Pick a recipe and adapt it
Start from the closest composition in references/recipes.md rather than assembling from scratch — those are the gallery's proven looks. Then adapt to the detection output:
- colours →
var(--chart-1..5)/chartCssVars, never literals; - corner style → host
--radius(rules/taste.md §4); - density → fewer grid rows / no background in small dashboard cards;
- palette, dark mode, Tailwind v3 quirks → rules/theming.md.
4. Install the registry items
Install every item the composition touches (the vocabulary's import table lists which slug provides each export), e.g.:
npx shadcn@latest add @bklit/bar-chart @bklit/bar-depth @bklit/chart-tooltip
shadcn adds missing CSS variables without overwriting the host's existing ones.
If @bklit does not resolve, see the bklit-ui skill's installation notes.
5. Confirm props against the installed source
Open the installed files (components/charts/<file>.tsx) and check every prop
you plan to use exists with the expected type. The registry source is the
contract; this skill can lag behind it.
6. Apply the taste rules
Run through rules/taste.md: one decorative layer, subtle
backgrounds, no stacked effects, corners matching --radius, rings with
squares, tokens only, dark mode verified, unique pattern ids.
7. Be honest about gaps
If the request needs something Bklit lacks (see "Not supported" in the
vocabulary — e.g. hexagon Background preset, glow on lines, stacked areas,
labels on bars), say so plainly, then offer the nearest supported look or a
small custom composition (recipe 15 shows the pattern). Never invent props such
as pattern="hexagons" or glow.
Output checklist
- Install command(s) with the exact
@bklit/<item>slugs. - Complete JSX with imports from the project alias.
- Any CSS token changes, in the host's colour format, for light and dark.
- One line per honest gap or trade-off.
- Links when useful:
https://bklit.com/docs/components/<slug>,https://bklit.com/charts/<slug>,https://bklit.com/studio?chart=<slug>.
Files
| File | Use |
|---|---|
| references/vocabulary.md | Phrase → JSX/props → registry slug; import map; unsupported list |
| references/recipes.md | 15 complete compositions for named looks |
| rules/taste.md | Design rules with incorrect/correct pairs |
| rules/theming.md | Host signals → chart token overrides (v4, v3, dark mode) |
| scripts/detect-design.mjs | Design detection (JSON) |
| evals/evals.json | Behaviour checks for this skill |
FAQ
What does the bklit-ui-design skill do?
Turns plain-language chart design requests into exact Bklit UI (@bklit shadcn registry) components and props, styled to fit the host app. Use when someone describes how a chart should look rather than naming props, e.g. "diagonal pattern background that fades out", "squircle bars", "3D glass bars", "hatched area", "dot grid", "skeleton loading state", "dashed forecast", "half donut", "make the charts match my brand / dark mode / border radius". Detects the project's Tailwind version, colour format, dark-mode strategy, radius and existing chart tokens, then picks a proven recipe, installs the right @bklit/ , adapts colours to theme tokens and states honestly when Bklit has no prop for the request. Also use when theming or restyling Bklit charts.
How do I install bklit-ui-design?
Run npx skills add https://github.com/bklit/bklit-ui --skill bklit-ui-design 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-ui-design/ (personal) or .claude/skills/bklit-ui-design/ (project).
Which AI agents can use bklit-ui-design?
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-ui-design 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-ui-design?
It is published by bklit in bklit/bklit-ui. It has 88 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.