documentation▌

Organize technical documentation into four distinct types—tutorials, how-to guides, reference, and explanations—each serving different user needs. \n \n Applies the Diátaxis framework to structure documentation by learning context: tutorials for beginners learning by doing, how-to guides for solving specific problems, reference for technical facts, and explanations for conceptual understanding \n Provides type-specific patterns including title conventions, structural templates, and validation ch

Turn the current conversation context into a PRD and submit it as a GitHub issue.

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation inline as decisions crystallise.

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.

Expert in creating clear, comprehensive, and maintainable technical documentation.

Templates and structure guidelines for common documentation types.

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.

Automated OpenAPI 3.0 documentation generation for Spring Boot 3.x REST APIs with Swagger UI. \n \n Integrates SpringDoc to auto-generate OpenAPI specs from annotated controllers, models, and validation rules without manual configuration \n Supports JWT Bearer, OAuth2, and Basic Auth security documentation with global scheme configuration and per-endpoint security requirements \n Includes comprehensive annotation patterns for documenting endpoints, request/response bodies, parameters, error resp

Write clear, maintainable technical documentation for different audiences and purposes.

Expert technical writer for Diátaxis-framework documentation creation across tutorials, how-to guides, reference, and explanation formats. \n \n Structures documentation into four distinct types: tutorials for learning, how-to guides for problem-solving, reference for technical specifications, and explanations for conceptual understanding \n Follows a three-step workflow: clarify document type and audience, propose a detailed outline for approval, then generate full markdown content \n Maintains