Menu
When to use graph, chart, timeline, diagram, comparison, or no visualization in Trellis reports
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Which Trellis components and structured blocks to use, with Storybook paths and anti-patterns
Entity selection, aliases, primary sections, relationship types, and edge strength
How to compose a Trellis report: choose template, plan sections, orientation, synthesis, KG scope
Source gathering, code tracing, fact versus inference separation, and evidence discipline
Common structure, contrast, takeaways, open questions, and references for Trellis synthesis
Foundations before mechanisms, examples before abstractions, progressive detail
| name | visualization-guidelines |
| description | When to use graph, chart, timeline, diagram, comparison, or no visualization in Trellis reports |
| triggers | ["choose visualization","add a diagram","visualize a report"] |
Use a visualization only when it reduces cognitive load.
Choose:
Do not add decorative diagrams, duplicate the KG as a static image, or introduce a custom chart without evidence that the standard blocks cannot carry the explanation.
Source of truth:
packages/engine/src/schemas/block.tspackages/engine/src/schemas/kg.ts, packages/engine/src/kg/graph-data.tspackages/storybook/stories/graph/EntityNode.stories.tsx, packages/storybook/stories/graph/RelationshipEdge.stories.tsx, packages/storybook/stories/graph/MiniGraph.stories.tsx, packages/storybook/stories/graph/GraphToolbar.stories.tsx, packages/storybook/stories/blocks/BlockRenderer.stories.tsx