swarmvault

Topics in the source

• SwarmVault
• Quick checks
• Core loop
• Working rules
• Files and artifacts
• Agent integration
• Defaults to preserve

Use this skill when the user wants a local-first knowledge vault built on the LLM Wiki pattern — three layers (raw sources, wiki, schema) where the LLM maintains a durable wiki between you and raw sources. Also use it when the project already contains swarmvault.config.json or swarmvault.schema.md. For onboarding, examples, command references, or troubleshooting, read the bundled README.md, examples/, references/, and TROUBLESHOOTING.md before improvising workflow advice. Work from the vault root. If the vault does not exist yet, run swarmvault init. Use swarmvault demo --no-serve when the user wants the fastest zero-config walkthrough before pointing SwarmVault at their own sources. Use swarmvault scan --no-serve when the user wants the fastest scratch pass over a local repo or docs tree without manually stepping through init + ingest + compile first. Read swarmvault.schema.md before compile or query work. It is the vault's operating contract. If wiki/graph/report.md exists, use it before broad repo search. 1. Initialize a vault with swarmvault init when needed. 2. Update swarmvault.schema.md before a serious compile. Use it for naming rules, categories, grounding, freshness expec

This is an excerpt. Refer to the complete source and its current requirements.