tf-doc-vault

Pre-publish release-readiness check for the @techfides/tf-doc-vault package. Confirms the external API / CLI surface is unchanged since the last release, runs the full quality gate (lint, typecheck, format, build, unit) plus the Playwright smoke suite, and does VISUAL BROWSER checks of the playground, the ana (create-ana) site and the tech-docs (init-tech-docs) site — verifying base-path correctness and a clean browser console. Use this whenever the user is about to publish or release a new version, cut a release, bump the version, run `pnpm release`/`npm publish`, or asks for a "prerelease check", "sanity check before publishing", "release readiness", or "is it safe to publish" — even if they don't spell out every step. Run it BEFORE the release.

Generates diagrams (Mermaid primary, PlantUML fallback) for already-generated documentation pages. Attaches diagrams at the `<!-- diagram-anchor: <name> -->` markers placed by the technical and functional phases — it does NOT invent diagrams for pages without anchors. Covers the common diagram types (component, C4, domain-model class, ERD, sequence, use-case, state, flowchart / decision, BPMN where applicable). Runs AFTER textual content is confirmed stable. Uses code and existing docs as evidence sources, and performs a consistency check between each diagram and the host page text. Invoked by the docs-from-code orchestrator or by /docs-diagrams. DO NOT trigger for text generation, wireframes, sales, or pre-code design. Always inherits rules from CLAUDE.md.

Orchestrator skill for generating project documentation from an existing codebase. Drives the full workflow — preflight, phase selection, delegation to phase skills (technical, functional, diagrams, wireframes), TODO resolution, and the small in-run review. Trigger when the user asks to generate documentation from code or from an existing codebase, or invokes /docs-generate-from-code. DO NOT trigger for pre-code design docs, sales or marketing documentation, or documentation/analysis review — those scopes have their own skills. Always inherits rules from CLAUDE.md.

Generates functional documentation from an existing codebase AND from any already-generated technical documentation in the current version folder. Covers the full functional menu (overview, product structure, glossary, actors, personas, screens, scenarios list, business rules, notifications, reports, and scenario details with wireframe anchors). Code is the ultimate source of truth; the technical section, when available, is used as a faster, already-digested lookup for APIs, roles, components, data model, feature toggles, and metrics. Works file-by-file (text only — no diagrams, no wireframes), pausing after each generated page for user review. Invoked by the docs-from-code orchestrator or by /docs-functional. DO NOT trigger for technical docs, diagrams, wireframes, sales, or pre-code design. Always inherits rules from CLAUDE.md.

Applies user feedback captured in `.claude/session-notes/*.md` to the documentation skill files themselves. Reads the notes produced by the session-notes collection step of `/docs-generate-from-code`, proposes a concrete edit per entry to the targeted `SKILL.md` or resource, waits for per-entry user approval, applies it, and marks the note processed. Trigger when the user asks to "apply session notes", "learn from session feedback", "process session notes", "update the docs skills from the last run", "improve the docs skills from session feedback", mentions `.claude/session-notes/` as the input, or asks to turn session notes into skill edits. DO NOT trigger for generating documentation pages, resolving in-content TODOs, editing `CLAUDE.md`, or editing files outside `.claude/skills/` and `.claude/commands/`. Always inherits rules from CLAUDE.md.

Generates technical documentation from an existing codebase — covering the full technical menu (tech stack, infrastructure, CI/CD, architecture, security, integrations, roles, jobs, testing, SLA, monitoring, scaling, feature toggles, caching, localization, disaster recovery, accessibility, audit, guides, and any project-specific technical concerns). Works file-by-file (text only — no diagrams, no wireframes), pausing after each generated page for user review. Invoked by the docs-from-code orchestrator or by /docs-technical. DO NOT trigger for functional docs, diagrams, wireframes, sales, or pre-code design. Always inherits rules from CLAUDE.md.

Generates SVG wireframes for already-generated documentation pages. Attaches wireframes at the `<!-- wireframe-anchor: <id> -->` markers placed by the functional phase (typically inside scenario files) — it does NOT invent wireframes for pages without anchors. Inputs include the codebase, already-generated docs, shared SVG fragments from `wf-fragments/`, and optional user-provided screenshots used as layout reference. ALWAYS runs as the last phase, AFTER text and diagrams are confirmed stable. Invoked by the docs-from-code orchestrator or by /docs-wireframes. DO NOT trigger for text generation, diagrams, sales, or pre-code design. Always inherits rules from CLAUDE.md.