@elevasis/sdk 0.5.3 → 0.5.5

package/reference/framework/agent.mdx

@@ -23,7 +23,7 @@ The generated `CLAUDE.md` contains these sections:
 - **Navigation** -- A table mapping concepts to file paths with load conditions (when to load each file). Includes SDK reference docs, credential model, error history, `docs/project-map.mdx`, and `docs/priorities.mdx`.
 - **Rules** -- Points to auto-loaded rule files in `.claude/rules/`. SDK patterns load automatically; project-specific patterns live in `workspace-patterns.md`. Includes error handling protocol.
 - **Interaction Guidance** -- Per-dimension behavior rules derived from `memory/profile/skills.md`. Covers vocabulary, code completeness, explanation depth, and growth logging.
-- **Commands** -- Table of the 4 slash commands with one-line purpose descriptions.
+- **Commands** -- Table of the 4 slash commands (`/meta`, `/docs`, `/work`, `/tutorial`) with one-line purpose descriptions.
 - **Skills** -- Auto-trigger conditions for the `creds` skill.
 - **Maintaining Memory** -- Hierarchical structure, pruning rules, and what belongs in memory vs. `docs/` vs. `.claude/rules/`.
 
@@ -42,11 +42,12 @@ At the start of every session the agent runs these steps silently before respond
 
 Slash commands are short Markdown instruction files in `.claude/commands/`. When you type `/command-name` in a Claude Code session, the agent reads the corresponding file and follows its instructions.
 
-Three commands and one skill are scaffolded by `elevasis init` and committed to version control so collaborators get the same experience:
+Four commands and one skill are scaffolded by `elevasis init` and committed to version control so collaborators get the same experience:
 
 | Command | File | Purpose |
 | --- | --- | --- |
 | `/meta` | `meta.md` | Project lifecycle -- init, status, fix (incl. docs verification), deploy, health |
+| `/docs` | `docs.md` | Browse, create, and verify permanent documentation |
 | `/work` | `work.md` | Task tracking -- list, create, save, resume, complete |
 | `/tutorial` | `tutorial.md` | Progressive learning path -- 3 tracks, menu-driven |
 
@@ -62,6 +63,14 @@ The `/meta` command namespace manages the full project lifecycle. It has five op
 - **`/meta deploy`** -- Full 9-step deploy pipeline: validate, type-check, verify docs, commit, deploy (auto-regenerates `docs/project-map.mdx`), verify platform, update deployment state, and optionally push.
 - **`/meta health`** -- Execution debugging and resource status; shows recent executions, analyzes failures, and checks environment connectivity.
 
+### `/docs` Command
+
+The `/docs` command manages the permanent `docs/` tree -- everything except `docs/in-progress/` (owned by `/work`) and auto-generated files (`project-map.mdx`, `resource-map.mdx`). Three operations:
+
+- **`/docs`** (no arguments) -- Browse. Scans `docs/` recursively and displays a numbered list of user-maintained docs with auto-generated files shown separately as read-only. Pick a number to read and discuss, or say "create" or "verify."
+- **`/docs create [description]`** -- Interview-driven reference doc creation. If the doc is about a specific resource, the agent scans `src/` and pre-populates from code (config, schemas, step names, platform tools). Scaffolds sections appropriate to the doc type (resource guide, integration guide, architecture notes, process doc, or general reference).
+- **`/docs verify [file?]`** -- Interactive standalone version of `/meta fix` step 5. Cross-references resource IDs, schema fields, and platform tools in docs against `src/`. Shows a summary, then guides fixes interactively. Can be scoped to a single file.
+
 ### `/work` Command
 
 The `/work` command manages in-progress task tracking across sessions. It uses `docs/in-progress/` for task documents with standardized frontmatter (`status: planned | in-progress | complete`). Operations:

package/reference/framework/index.mdx

@@ -17,6 +17,7 @@ Running `elevasis init my-project` produces the following agent infrastructure a
 ├── settings.json               # autoCompact: false
 ├── commands/
 │   ├── meta.md                 # Project lifecycle (init, fix, deploy, health)
+│   ├── docs.md                 # Browse, create, and verify permanent docs
 │   ├── tutorial.md             # Progressive learning path (3 tracks)
 │   └── work.md                 # Task tracking
 ├── hooks/
@@ -52,7 +53,7 @@ The agent reads `memory/index.md` at session start and drills into `memory/profi
 
 The `CLAUDE.md` file drives all agent behavior. It contains the session initialization instructions, adaptive guidance tiers, memory maintenance rules, and slash command definitions. No hooks, no code enforcement -- everything is instruction-driven so non-technical users never need to configure anything.
 
-The `/meta` command manages the project lifecycle: `/meta init` for guided setup, `/meta fix` for SDK upgrades, drift repair, and documentation verification, `/meta deploy` for deployments, `/meta health` for debugging executions. `/work` tracks tasks across sessions, and `/tutorial` guides new developers through a menu-driven multi-track learning path. A `creds` skill auto-triggers when credential setup is needed.
+The `/meta` command manages the project lifecycle: `/meta init` for guided setup, `/meta fix` for SDK upgrades, drift repair, and documentation verification, `/meta deploy` for deployments, `/meta health` for debugging executions. `/docs` browses, creates, and verifies permanent documentation in `docs/`. `/work` tracks tasks across sessions, and `/tutorial` guides new developers through a menu-driven multi-track learning path. A `creds` skill auto-triggers when credential setup is needed.
 
 See [Agent System](agent.mdx) for CLAUDE.md sections, slash command reference, developer profile, and adaptive guidance tiers.
 

package/reference/framework/project-structure.mdx

@@ -229,7 +229,7 @@ This directory is gitignored -- it is personal to you and not shared with collab
 
 ## Slash Commands
 
-The `.claude/commands/` directory contains three commands covering the core development loop. Invoke them in Claude Code with `/meta`, `/work`, and `/tutorial`.
+The `.claude/commands/` directory contains four commands covering the core development loop. Invoke them in Claude Code with `/meta`, `/docs`, `/work`, and `/tutorial`.
 
 ### `/meta` -- Project Lifecycle
 
@@ -241,6 +241,14 @@ Manages the full lifecycle of your workspace. Five operations:
 - **`deploy`** -- Full 9-step deploy pipeline: validate, type-check, verify docs, commit, deploy (auto-regenerates `docs/project-map.mdx`), verify platform, update deployment state, and optionally push.
 - **`health`** -- Execution debugging and resource status; shows recent executions, analyzes failures, and checks environment connectivity.
 
+### `/docs` -- Documentation
+
+Manages the permanent `docs/` tree. Three operations:
+
+- **No arguments** -- Browse. Lists user-maintained docs with auto-generated files (`project-map.mdx`, `resource-map.mdx`) shown as read-only. Pick a number to read and discuss.
+- **`create [description]`** -- Interview-driven reference doc creation. If the doc is about a specific resource, the agent reads `src/` and pre-populates from code. Scaffolds sections by doc type (resource guide, integration guide, architecture notes, process doc, general reference).
+- **`verify [file?]`** -- Interactive standalone docs verification. Cross-references resource IDs, schema fields, and platform tools in docs against `src/`. Guides fixes interactively.
+
 ### `/work` -- Task Tracking
 
 Manages in-progress task tracking across sessions using `docs/in-progress/` task documents. Five operations:
@@ -261,7 +269,7 @@ A 7-lesson guided learning path adapted to the user's skill profile. Lessons cov
 
 Not all scaffolded files participate in template updates. Files fall into two categories:
 
-**SCAFFOLD_FILES total: 29**
+**SCAFFOLD_FILES total: 30**
 
 **INIT_ONLY** (15 files) -- Written once during `elevasis init`, never updated by `elevasis update`:
 - `package.json`, `pnpm-workspace.yaml`, `tsconfig.json`
@@ -270,10 +278,10 @@ Not all scaffolded files participate in template updates. Files fall into two ca
 - `docs/index.mdx`, `docs/in-progress/.gitkeep`
 - `.claude/rules/workspace-patterns.md`
 
-**MANAGED** (14 files) -- Written during `elevasis init` and checked/updatable by `elevasis update`:
+**MANAGED** (15 files) -- Written during `elevasis init` and checked/updatable by `elevasis update`:
 - `elevasis.config.ts`, `.gitignore`, `CLAUDE.md`, `.claude/settings.json`
 - One hook: `.claude/hooks/enforce-sdk-boundary.mjs`
-- Three command files: `.claude/commands/meta.md`, `.claude/commands/tutorial.md`, `.claude/commands/work.md`
+- Four command files: `.claude/commands/meta.md`, `.claude/commands/docs.md`, `.claude/commands/tutorial.md`, `.claude/commands/work.md`
 - One skill: `.claude/skills/creds/SKILL.md`
 - Five rule files: `.claude/rules/sdk-patterns.md`, `.claude/rules/docs-authoring.md`, `.claude/rules/memory-conventions.md`, `.claude/rules/project-map.md`, `.claude/rules/task-tracking.md`