@infinitedusky/indusk-mcp 1.0.0 → 1.0.1

package/lessons/community/community-add-to-sidebar.md

@@ -0,0 +1,7 @@
+# Always add new docs pages to the sidebar
+
+When you create a new documentation page, you must also add it to the VitePress sidebar configuration in `.vitepress/config.ts`. If you don't, the page exists but is invisible — no one can navigate to it.
+
+This is the single most common documentation mistake. The page is written, the content is good, but it's orphaned because the sidebar wasn't updated.
+
+The fix is simple: every time you create a page, immediately open `.vitepress/config.ts` and add the entry to the correct sidebar section. Do it in the same edit, not as a follow-up.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@infinitedusky/indusk-mcp",
-	"version": "1.0.0",
+	"version": "1.0.1",
 	"description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
 	"type": "module",
 	"files": [

package/skills/document.md

@@ -63,6 +63,16 @@ apps/indusk-docs/src/
 └── lessons/         # Distilled from retrospective insights during archival
 ```
 
+**CRITICAL: Every new page must be added to the sidebar.** The sidebar is configured in a single file: `apps/indusk-docs/src/.vitepress/config.ts` under `themeConfig.sidebar`. If you create a page but don't add it to the sidebar, it is invisible — users cannot navigate to it. This is the most common documentation mistake.
+
+When you create or move a page:
+1. Write the page content
+2. **Immediately** open `.vitepress/config.ts`
+3. Add the page to the correct sidebar section
+4. Verify the page appears in navigation
+
+Never consider a documentation item complete until the sidebar entry exists.
+
 **Pipeline:** Document skill writes/updates docs during impl → retrospective skill archives planning artifacts and distills ADRs into decisions/ and insights into lessons/. Don't manually populate decisions/ or lessons/ during impl work — that's the retrospective's job.
 
 ### What Goes Where