ariadne

Design or modify Markdown knowledge-vault navigation: folder hubs, agent navigation, routing matrices, workstream graphs, optional Bases/view layers, templates, health-check rules, and long-term traversability.

Use when creating, promoting, importing, nesting, or reorganizing scopes inside an existing Markdown knowledge vault with inherited parent and child scope rules.

Validate the structure of an agent-maintained Markdown knowledge vault with deterministic CLI checks for YAML/frontmatter, broken wikilinks, Markdown orphans, scope wiring, and optional Obsidian-compatible view files.

Bootstrap an agentic Markdown knowledge vault for projects, research, learning, life systems, and other long-running knowledge work. Use when creating a new vault, installing the base folder structure, templates, AGENTS.md, CLAUDE.md, Agent navigation files, and optional Obsidian-compatible Bases.

Create or update workspace-level instruction files for code repositories or ordinary project folders, including AGENTS.md, CLAUDE.md, GEMINI.md, local override files, and Ariadne vault-link blocks. Use when a user wants to initialize, repair, or refresh workspace instructions, connect a workspace to a registered Ariadne vault or scope, or make instructions portable across Codex, Claude Code, Gemini CLI, and other agent runtimes without duplicating global discovery.

Run maintenance and health checks for agent-maintained Markdown knowledge vaults: broken links, orphan notes, stale hubs, invalid frontmatter, uncompiled raw sources, stale queues, unresolved questions, optional Base coverage, and health reports.

Close or checkpoint meaningful completed work in an agent-maintained Markdown knowledge vault. Use when the user asks to run Ariadne closeout, make work durable, close the loop, checkpoint this work, capture the outcome, decide whether a chat can close, draft a handoff, or update vault memory after incidents, releases, evaluations, feature work, architecture/product decisions, research sprints, or substantial planning sessions.

Register existing Markdown knowledge vaults for machine-level discovery so cold agents can find long-term knowledge from any workspace. Use when checking, adding, updating, repairing, or removing global vault discovery.

Use when links, documents, PDFs, transcripts, screenshots, meeting notes, observations, brain dumps, or other material must be compiled into an explicitly selected Markdown knowledge-vault destination.

Use when routing a new article, paper, repository, dataset, transcript, chat, observation, generated analysis, or other research input into a named Markdown knowledge-vault scope, especially when pipeline readiness or conditional synthesis must be decided.

Use when recurring research inside an existing Markdown knowledge-vault scope needs a boundary descriptor, raw and compiled routes, inquiry and synthesis hubs, local templates, optional Bases, or routing.

Use when auditing or repairing provenance, compilation coverage, stale synthesis, unresolved questions, circular corroboration, nested-boundary isolation, or legacy research drift within one named Markdown knowledge-vault research boundary.

Use when multiple compiled research sources may change, confirm, contradict, supersede, or leave unchanged an inquiry, synthesis, evidence map, thread hub, or promotion candidate inside a Markdown knowledge vault.

Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.