SDTK-WIKI
SDTK-WIKI is the project memory layer of the SDTK lifecycle: it indexes your repo's own docs in place into a local knowledge graph (atlas), serves a docs + graph viewer, and answers deterministic grounded search/query over the full corpus — no cloud, no LLM in the CLI. (Looking for a personal, cross-project second brain? That job moved to the standalone SDTK-BRAIN tool.)
> YOUR PROJECT REMEMBERS ITSELF
Every other AI dev tool forgets your project the moment you close the tab. SDTK-WIKI is the local memory layer that runs underneath the whole suite — so your AI starts each session already knowing what was decided, what is half-built, and what is shipped. This is the single feature that turns nights and weekends into compounding progress instead of a series of restarts.
Without a memory layer
With SDTK-WIKI
Every doc you write, every decision you log, every spec the suite produces gets ingested into the wiki + graph.
sdtk-wiki init --no-open # index your project docs into the atlas graphYou sit back down. Open the project. Forgot what 'order-tracking-v2' was about.
sdtk-wiki query "order tracking v2 acceptance"Wiki returns the relevant BA spec, the design decisions, the open tasks, and what was already shipped.
→ BA_SPEC + ARCH_DESIGN + REVIEW_PACKET + open backlogYour AI now starts the session knowing the context, not asking you to re-explain it.
No 45-minute re-orientation. Straight to the next decision.When a solo founder reaches for this
Next Friday night. Two weeks since you touched this project. Normally you'd spend 45 minutes re-reading your own code and decisions. Instead: open the repo, sdtk-wiki query 'where did I leave order tracking', read the indexed BA spec + open backlog + last review packet, and start the next decision within 5 minutes. This is what 'progress compounds' actually means.
Product truth
These cards summarize the current shipped or internal surface exactly as it exists in the local source tree.
Builds index your repo's docs in place and write generated pages into .sdtk/wiki (graph data, provenance, reports, raw registry). A <project>/wiki directory is yours to hand-write: nothing generates it, and search/query read it alongside the generated pages, labelling each hit store: wiki or store: atlas.
The intended flow is init (builds the atlas graph over your project docs), then query/search/ask over the full corpus — with the docs + graph viewer one command away. The old ingest/compile pipeline is deprecated in favor of the standalone SDTK-BRAIN tool.
Report-first linting (orphans, broken links, stale claims, contradictions) keeps the memory honest, and the viewer's multi-workspace switcher (atlas build --workspace name=path) can show your project wiki and a standalone SDTK-BRAIN vault side by side.
The wiki viewer ships a 4th Design tab alongside Dashboard, Docs, and Graph. Open it to browse style presets, prompt the sdtk-design pipeline, watch it stream live, and annotate prototype elements — all in the viewer. The resulting DESIGN_FEEDBACK file lands in docs/design/feedback/, same as the standalone Preview Studio. Requires sdtk-design-kit installed.
Beginner workflow
Knowledge operations
Starting over
Viewer
Storage contract
| Runtime | Project | User | Notes |
|---|---|---|---|
| CLI | Yes | Package install | Runs locally inside the target project and writes project-local wiki output and .sdtk/wiki state. |
| Claude | Yes | Guide-aware | Generated AGENTS.md and CLAUDE.md are intended to help agent sessions read the local wiki contract before working. |
| Codex | Yes | Guide-aware | Generated AGENTS.md anchors Codex sessions to the project memory layer and safety rules. |
Canonical usage guide
products/sdtk-wiki/governance/SDTK_WIKI_USAGE_GUIDE.md
Install, initialize, search/query/ask, lint, and maintain the project memory layer.
Package README
products/sdtk-wiki/distribution/sdtk-wiki-kit/README.md
npm-facing package truth for sdtk-wiki-kit and the current public command surface.
Internal state
.sdtk/wiki
Project-local reports, provenance, raw registry, graph output, and maintenance evidence.
Position in the SDTK control plane
SDTK-WIKI is the memory layer that wraps every owner. It is the only product that reads across all packs so context, decisions, and lookups survive between work sessions.
Highlighted owners actively use SDTK-WIKI as their execution pack.
Family links
These product pages map the current suite boundaries so users can move from specification to coding to operations deliberately.
Use SDTK-SPEC for formal requirements, architecture, traceability, and downstream handoffs.
Open page ->DesignUse SDTK-DESIGN to turn requirements and project context into reviewable screen briefs, prototypes, and design handoff evidence.
Open page ->ImplementationUse SDTK-CODE after handoff when implementation, debugging, verification, and ship readiness become active.
Open page ->OperationsUse SDTK-OPS when deployment, CI/CD, monitoring, incidents, and operational verification become active.
Open page ->