Assists with writing and maintaining Morphir technical documentation. Use when creating, reviewing, or updating documentation including API docs, user guides, tutorials, and content for the Docusaurus site. Also helps ensure documentation quality through link checking, structure validation, and code review for documentation coverage.
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Search for package-specific usage rules and best practices from Elixir packages. Use when you need coding conventions, patterns, common mistakes, or good/bad examples for packages like Ash, Phoenix, Ecto, etc.
API documentation to be loaded at startup
็ๆๅไธชๆๆกฃ็่ฏฆ็ปๅ ๅฎน๏ผๆ นๆฎๆๆกฃ็ปๆๅ็จๆทๆๅพ็ๆๅ ๅซๅฏผ่ชใไปฃ็ ็คบไพใๆๆฏๅพ่กจ็ๅฎๆดๆๆกฃใ ไฝฟ็จๅบๆฏ๏ผ - doc-smith ไธปๆต็จ่ฐ็จ๏ผๆน้็ๆๅๆๆกฃๅ ๅฎน - ่พๅ ฅๆๆกฃ่ทฏๅพ๏ผไธ document-structure.yaml ไธญ็ path ๅฏนๅบ๏ผ - ่ชๅจ่ฏปๅ workspace ้ ็ฝฎ๏ผdocument-structure.yamlใuser-intent.mdใconfig.yaml๏ผ - ๅๆๆบไปฃ็ ๅนถ็ๆ็ปๆๅๅ ๅฎน - ่ฐ็จ saveDocument ไฟๅญ๏ผ่ฐ็จ checkContent ๆ ก้ช - ่ฟๅๆ่ฆไฟกๆฏ๏ผไธ่ฟๅๅฎๆดๅ ๅฎนไปฅ่็ไธไธๆ๏ผ
ไปๅทฅไฝๅบๆฐๆฎๆบ็ๆๅๆดๆฐๅ จ้ข็ๆๆกฃ๏ผๅ ๆฌไปฃ็ ไปๅบใๆๆฌๆไปถๅๅชไฝ่ตๆบใๅฝ็จๆท่ฏทๆฑไปฅไธๆไฝๆถไฝฟ็จๆญคๆ่ฝ๏ผ(1) ไปไปฃ็ ๆๆไปถๅๅปบๆ็ๆๆๆกฃ๏ผ(2) ๆๅปบๆๆกฃ็ปๆๆๆๆกฃ่ฏฆๆ ๏ผ(3) ๆดๆฐใไฟฎๆนๆๆน่ฟๅทฒๆๆๆกฃ๏ผ(4) ้ๅๆๆกฃ็็นๅฎ็ซ ่ๆๆฎต่ฝ๏ผ(5) ๅค็ changeset ๆไปถๆ PATCH ๆ ่ฎฐ็ไฟฎๆน่ฏทๆฑใๆฏๆๆๆฏๆๆกฃใ็จๆทๆๅใAPI ๅ่ๅไธ่ฌๆๆกฃ้ๆฑ็็ๆไธ็ปดๆคใ
PROACTIVELY search auto-generated documentation when receiving ANY user instruction. Search for function signatures, API documentation, class definitions, and code comments BEFORE implementing anything. Your codebase documentation is valuable - use it first.
Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.
Auto-generate OpenAPI 3 documentation for Spring Boot REST APIs using springdoc-openapi. Use when API endpoints change, controllers are modified, or user mentions API docs, Swagger, or OpenAPI. Triggers on @RestController changes, documentation requests, endpoint additions.
Auto-generate OpenAPI 3 documentation for Spring Boot 4.x REST APIs using springdoc-openapi v3.0. Use when API endpoints change, controllers are modified, or user mentions API docs, Swagger, or OpenAPI. Triggers on @RestController changes, documentation requests, endpoint additions. Requires Spring Boot 4.0+ and Java 17+.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Write Python docstrings following the Google Python Style Guide, using clear sections and examples.
Captures solved problems as categorized documentation with YAML frontmatter for fast lookup. Use when user confirms solution with phrases like 'that worked', 'it's fixed', 'working now', or via /doc-fix command.
Use this when you have finished making code changes and you are ready to update the documentation based on those changes.
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
List all server-side noridocs, optionally filtered by repository and/or path prefix.
Read documentation from the server-side noridocs system by file path.
Write or update documentation in the server-side noridocs system.
Expert at writing high-quality documentation for code, APIs, and projects. Auto-invokes when generating docstrings, creating README files, writing API documentation, adding code comments, or producing any technical documentation. Provides language-specific templates and best practices for effective documentation writing.
Token-efficient library API documentation fetcher using Context7 MCP with 77% token savings. Fetches code examples, API references, and usage patterns for published libraries (React, Next.js, Prisma, etc). Use when users ask "how do I use X library", need code examples, want API syntax, or are learning a framework's official API. Triggers: "Show me React hooks", "Prisma query syntax", "Next.js routing API". NOT for exploring repo internals/source code (use researching-with-deepwiki) or local files.
Expert technical writer for Logseq Template Graph project. Generates comprehensive, accurate, and well-structured documentation for modules, features, guides, and APIs. Activates when asked to "write docs", "document this", "create README", "update documentation", or similar requests. Analyzes code/templates to extract information and writes clear, user-focused documentation following project style.
Deep dive into the Docusaurus configuration, plugins, and custom fields.
Guide for creating comprehensive PR descriptions with proper structure, diagrams, and documentation for code reviews.
