docs▌

User can provide specific focus areas or documentation types:

Four slash commands for creating, maintaining, and auditing project documentation with smart templates. \n \n Provides /docs-init to scaffold CLAUDE.md, README.md, and docs/ structure for new projects, with auto-detection of project type (Cloudflare Workers, Next.js, or generic) \n Includes /docs-update for full documentation audits covering date freshness, version accuracy, broken links, redundancy, and orphaned files \n Offers /docs-claude for focused CLAUDE.md maintenance, checking tech stack

Category: test

Complete technical documentation for Hindsight - a biomimetic memory system for AI agents.

ln-610-docs-auditor

Generates comprehensive TypeScript documentation with JSDoc, TypeDoc, and multi-layered patterns for different audiences. \n \n Supports framework-specific documentation for NestJS, Express, React, Angular, and Vue with tailored patterns and examples \n Includes TypeDoc configuration, JSDoc best practices, and automated documentation generation pipelines with GitHub Actions \n Provides architectural decision record (ADR) templates and validation tools to document design decisions alongside code

Query OpenAI's official developer documentation via MCP server for API, SDK, and platform guidance. \n \n Search and fetch docs on OpenAI APIs (Chat Completions, Realtime, Responses), SDKs, ChatGPT Apps, Codex, and migrations using a CLI wrapper around the OpenAI Docs MCP server \n Includes subcommands for discovery ( search , list ), retrieval ( fetch ), and schema inspection ( endpoints , openapi ) \n Supports optional anchors for fetching specific doc sections and code sample generation in mu

Retrieve current documentation and code examples for any library using the Context7 CLI.

Automatically capture solved problems as searchable documentation with category-based organization and YAML validation. \n \n Auto-triggers after confirmation phrases like \"that worked\" or \"it's fixed\"; documents non-trivial problems with investigation history, root cause, and prevention guidance \n Enforces strict YAML frontmatter validation against enum-defined problem types and severity levels before file creation \n Organizes solutions into category directories (e.g., docs/solutions/perf

XML documentation standards and patterns for C# public APIs and members. \n \n Use <summary> for one-sentence descriptions starting with a present-tense verb, and <remarks> for implementation details, usage notes, or additional context \n Employ specific tags for different member types: <param> and <returns> for methods, <value> for properties, <typeparam> for generics, and <exception cref> for thrown exceptions \n Follow prescribed wording patterns for Boolean