القائمة
Which Trellis components and structured blocks to use, with Storybook paths and anti-patterns
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | component-library-usage |
| description | Which Trellis components and structured blocks to use, with Storybook paths and anti-patterns |
| triggers | ["use Trellis components","choose report blocks","component library"] |
Use standard blocks first. Add custom blocks only when the report needs an interaction or visualization the schema cannot express.
Default choices:
conceptIntro for the first explanation of an idea.stepByStep when order matters.callout for real cautions, notes, asides, or quotes.keyTakeaways after a dense section.comparisonTable for compact option-by-criterion comparisons.codeBlock only when a source excerpt helps the reader inspect implementation.Avoid ornamental cards, duplicate explanations across blocks, or custom components that only restyle prose.
Source of truth:
packages/engine/src/schemas/block.tspackages/engine/src/schemas/custom-manifest.tspackages/storybook/stories/blocks/ConceptIntro.stories.tsx, Callout.stories.tsx, StepByStep.stories.tsx, KeyTakeaways.stories.tsx, BlockRenderer.stories.tsxpackages/storybook/stories/shell/ReaderShell.stories.tsx, packages/storybook/stories/views/OrientationView.stories.tsx, packages/storybook/stories/views/ReferenceView.stories.tsx, packages/storybook/stories/views/SynthesisView.stories.tsxEntity 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
Calm, precise, explanatory voice for Trellis reports