Chart component kit

Create reusable charts with useful labels, empty states, and data alternatives.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Chart component kit

Create reusable charts with useful labels, empty states, and data alternatives.

## Deliverable
A chart library with mixed datasets, accessible descriptions and state stories.

## Stack and visual direction
- Recommended starting stack: React and TypeScript with semantic CSS variables. Use Storybook when isolated examples serve the deliverable.
- Bento grid: Arrange content in purposeful modules whose sizes communicate priority. Preserve logical reading and keyboard order when modules reflow. Apply this direction to the interface while keeping data and controls easy to read.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [shadcn/ui Skill](https://ui.shadcn.com/docs/skills) (Skill) — Inspect the project's component registry and assemble accessible UI primitives.
  Project with compatible React and styling configuration. Follow the skill's agent-specific setup. Fallback: Reuse established controls in the project, or start with semantic native controls and test keyboard and error states.
- [Recharts](https://github.com/recharts/recharts) (Repository) — Visualize comparisons or time series with a readable textual or tabular alternative.
- [Storybook](https://github.com/storybookjs/storybook) (Repository) — Exercise reusable components and document visual and interactive states in isolation.
- [Web Design Guidelines](https://github.com/vercel-labs/agent-skills/tree/main/skills/web-design-guidelines) (Skill) — Review frontend UI against usability and accessibility guidance.
  Access to the current upstream guidelines for the skill's full review. Fallback: Perform the recipe's keyboard, focus, responsive and feedback checks manually.

## Workflow
1. Build comparison, trend and composition examples around typed datasets. Define axes and labels, add text or table alternatives, and exercise dense, empty and single-point data.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] A reader can access the exact values without hovering over a graphic.
- [ ] Charts handle zero values and incomplete data without implying false trends.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Verify real actions and persisted data where required. Exercise relevant loading, empty, invalid, pending, failure and success states. Provide a clear recovery path.
- [ ] Use fixtures to verify core flows, including a narrow-screen layout and any applicable permission boundaries.

Recipe resources

Source, setup, and compatibility details.