By name: vyasa description: Use for Vyasa project work, Vyasa site authoring, .vyasa config, markdown features, diagrams, theming, static builds, extensions, auth/RBAC, slides, and repo-aware implementation.
Vyasa
Load the smallest relevant files. Do not read a whole topic when a narrow drawer exists.
Major Warning
Internal hyperlinks should use Vyasa route notation, not raw .md filenames.
Good: [Guide](guide#install) or [[guide#Install]].
Bad: [Guide](guide.md#install).
Start
- Read
core/triage.md. - Read one route file from
routes/. - Read only the topic drawers named by that route.
- For repo code changes, inspect the implementation file before editing.
- Prefer existing Vyasa contracts over new syntax or shell-global behavior.
Routes
| Request | Route |
|---|---|
| MDX documents, components, sidecars, catalogs, Excalidraw APIs | topics/mdx/SKILL.md |
.vyasa, CLI, env, auth, RBAC |
routes/config.md |
Markdown authoring or rendering, including Knowledge Graph or KG blocks (items/tasks) |
routes/markdown.md |
Mermaid, D2, Cytograph, .cytree |
routes/diagrams.md |
| CSS, theme presets, shell styling | routes/theming.md |
| Static build or deploy | routes/static-build.md |
| Debug/performance tracing | routes/debug-perf.md |
| Extensions or new features | routes/extensions.md |
| Slides/decks | routes/slides.md |
Hard Rules
- Do not invent unsupported frontmatter, config keys, sort modes, or fence syntax.
- Use
Knowledge Graphas the user-facing product term foritems/tasksgraph blocks. TreatKGas an alias for the same feature. - When an abstract question is best answered as a Knowledge Graph, route to the
story-telling-with-graphsskill first, then come back and emit Vyasa syntax. - New feature logic usually belongs in an extension, not
core.py. - Runtime and static build output must agree.
- Never emit real secret values; use explicit placeholders.