Agent Skills: Infographic Structure Creator

Generate or update infographic Structure components for this repo (TypeScript/TSX in src/designs/structures). Use when asked to design, implement, or modify structure layouts (list/compare/sequence/hierarchy/relation/geo/chart), including layout logic, component composition, and registration.

UncategorizedID: antvis/Infographic/infographic-structure-creator

Install this agent skill to your local

pnpm dlx add-skill https://github.com/antvis/Infographic/tree/HEAD/.skills/infographic-structure-creator

Skill Files

Browse the full folder contents for infographic-structure-creator.

Download Skill

Loading file tree…

.skills/infographic-structure-creator/SKILL.md

Skill Metadata

Name
infographic-structure-creator
Description
Generate or update infographic Structure components for this repo (TypeScript/TSX in src/designs/structures). Use when asked to design, implement, or modify structure layouts (list/compare/sequence/hierarchy/relation/geo/chart), including layout logic, component composition, and registration.

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).