new-chart-type

Create new chart scaffolding with builder, options, and renderer integration for restructured-charts.

38|15|Updated Jul 26, 2023
One-click install
npx skills add https://github.com/sisense/compose-sdk-monorepo --skill new-chart-type
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-chart-type
Source: https://github.com/sisense/compose-sdk-monorepo/tree/main/.claude/skills/new-chart-type
Command: npx skills add https://github.com/sisense/compose-sdk-monorepo --skill new-chart-type

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of introducing a new chart type into the restructured charts architecture by scaffolding a ChartBuilder, wiring up the chart renderer, and aligning with design-time options.

Core Features & Use Cases

  • Scaffold a new chart type architecture under restructured-charts including a builder, data, and options files.
  • Support both custom renderers and Highcharts-based implementations with a guided path.
  • Use when expanding the chart library to cover a new family or chart type and ensure consistency with existing design options and tests.

Quick Start

Follow the Path A or Path B templates to scaffold a new chart type and begin implementing the builder, data, and renderer.

Frequently Asked Questions about new-chart-type

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new chart type to the restructured-charts architecture?

To add a new chart type, scaffold a ChartBuilder along with data and options files, wire up the chart renderer, and register the builder in the factory to align with design-time options.

Can I build a custom chart renderer or do I need to use Highcharts?

You can use both custom renderers and Highcharts-based implementations, as the scaffolding provides a guided path to integrate either rendering method for your new chart type.

What TypeScript typings do I need to maintain when creating a new chart type?

You must maintain TypeScript typings for chart data, options, and rendering to ensure type safety and consistency when extending the SDK with new chart families.

When do I need to scaffold a new chart family in the SDK?

You scaffold a new chart family when expanding the chart library to cover a new chart type, ensuring the new builder and renderer align consistently with existing design options and tests.

What is the best way to scaffold chart type architecture for the SDK?

The best way is following the Path A or Path B templates to scaffold the new chart type and begin implementing the required builder, data, and renderer files.

Why does my new chart type need to be registered in the builder factory?

Registering the builder in the factory is required to integrate the new chart type into the restructured-charts architecture so it can be recognized and rendered by the SDK.