mcpField
I
infographic-structure-creator

infographic-structure-creator

github.com/antvisDesign & UI7.0k135 installsUpdated 1w ago
Repository

About infographic-structure-creator

A skill for generating complete TypeScript Structure components for an infographic framework. It follows the framework’s component, layout, and registration constraints.

Key features

  1. 01Generates full Structure component code
  2. 02Plans layouts using element bounds
  3. 03Supports Item and Items patterns
  4. 04Includes imports, props, and registration
  5. 05Checks component and empty-state constraints

Use cases

  1. 01Creating a structure for a new infographic layout
  2. 02Implementing a hierarchy or directional arrangement
  3. 03Adding registered Structure components to a project

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/antvis/infographic --skill infographic-structure-creator

After installing, type/infographic-structure-creatorin Claude Code to confirm it loaded.

Bundled filesreferences/structure-prompt.md

Details

From the project README

Infographic Structure Creator

Overview

Generate complete Structure component code for the infographic framework, following the project's component rules, layout constraints, and registration requirements.

Workflow

  1. Read references/structure-prompt.md for the full framework rules, allowed components, and output requirements.
  2. Clarify minimal requirements if missing: structure category, layout direction, hierarchy depth, and whether add/remove buttons are needed.
  3. Choose Item vs Items, compute layout from getElementBounds, and plan decor elements under ItemsGroup.
  4. Produce a full TypeScript file: imports, Props extends BaseStructureProps, component implementation, and registerStructure with accurate composites.
  5. Self-check against the constraints in the reference (no unlisted components, no SVG cx/cy/r, correct indexes, empty-state handling).

Notes

  • Prefer scanning src/designs/structures for similar existing structures to match local patterns when appropriate.
  • Keep output concise; avoid React-only features (keys, hooks).

Comments

Markdown supported