메뉴
When to use graph, chart, timeline, diagram, comparison, or no visualization in Trellis reports
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
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
SOC 직업 분류 기준
| 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