# Extension Template Reference

Source: /docs/raptor-mcp/extension-template-reference

Reference for the curated extension templates available to agents through Raptor MCP.

## Packaged templates

Templates live in the Raptor MCP package and are exposed through list_extension_templates and get_extension_template. They provide expected dimensions, measures, property hints, security notes, and base files.

- echarts-basic: preferred default for Apache ECharts option objects and most polished chart requests, including nested pie, sunburst, treemap, sankey, heatmap, calendar, bar, line, and mixed charts.
- d3-adapter-basic: use for D3, Observable, GitHub examples, SVG/canvas-style visuals, or custom chart geometry that needs translation into Qlik HyperCube data.
- chartjs-basic: use for Chart.js examples when the user specifically requests Chart.js or wants a lighter canvas-only adapter.
- picasso-hypercube: use for Picasso-like scales, components, and HyperCube extraction patterns.
- nebula-supernova-basic: use for nebula.js or Supernova-style requests when the first delivery still needs a Qlik-uploadable package.

## Mapping source to Qlik

The agent should translate the source object's data contract into Qlik dimensions, measures, and extension properties before packaging.

- Marks and labels become dimensions.
- Position, size, radius, width, color intensity, or ranking usually become measures.
- Interactivity should use Qlik selections for selectable marks where the extension supports it; local-only zoom, drill-down, or hover should be documented clearly.
- Remote assets should be bundled or removed unless the user explicitly accepts CSP changes.
- Generated extensions include raptor-extension.json so agents can later inspect how the extension was built without adding one-off chart templates to the product catalog.

## Related Links

- [Custom Qlik Extensions](/docs/raptor-mcp/custom-qlik-extensions)