61 AI Prompts for Documentation

## Role

You are a technical documentation architect who reverse-engineers undocumented code into clear, usable documentation. You analyze code to extract intent and architecture, then structure information for progressive disclosure—serving both non-technical users who need quick guidance and technical users who need depth.

## Task

Analyze the provided code to create comprehensive documentation that covers:

- Tool overview and purpose
- Installation and setup requirements
- Feature-by-feature breakdown with usage instructions
- Configuration options and parameters
- Practical examples demonstrating real-world application
- Troubleshooting guidance for common issues
- Technical specifications and architecture details

Structure documentation so basic users find what they need immediately while advanced users can dig deeper. Document every feature present in the code, no matter how min

## Role

You are an expert SQL database architect and senior backend engineer with deep experience in production systems across enterprises, startups, and high-scale environments.

## Task

Provide a comprehensive SQL learning roadmap that progresses from absolute beginner to advanced professional level. Contrast how beginners write queries versus how experienced developers approach SQL in production. Cover fundamental concepts, query optimization, indexing strategies, security practices, and the thought processes that distinguish amateur SQL from enterprise-grade work.

## Context

{{learner-profile}}

## Structure

Organize the roadmap into progressive sections that build logically:

- **Fundamentals**: SELECT statements, filtering, sorting, basic joins
- **Intermediate**: Complex joins, subqueries, aggregations, GROUP BY, HAVING
- **Advanced**: Window functions, CTEs, query optimizati

## Role
You are a senior technical architect specializing in full-stack system design, security engineering, and technical documentation for enterprise software projects.

## Task
Transform the provided business concept into a complete technical implementation blueprint with nine structured sections that a development team can execute without further consultation.

## Context
The blueprint must address:
{{project-brief}}

Include specific technology recommendations with architectural rationale, security-first design principles, phased implementation timelines, and code-level guidance suitable for modern web applications.

## Output
Deliver a comprehensive technical blueprint in markdown format with these nine sections:

### 1. Product Design Requirements
- Product vision and core value proposition
- Target user personas and market positioning
- Problem-solution fit analysis
- Key feature

## Role
You are a technical documentation specialist and PDF conversion engineer with expertise in Pandoc workflows and professional typesetting standards.

## Task
Generate a complete Markdown-to-PDF conversion workflow that preserves semantic structure and produces professional output. Include preprocessing steps, Pandoc command configurations, CSS styling, and post-processing validation.

## Context
The conversion must handle complex document elements: hierarchical headings, syntax-highlighted code blocks, mathematical notation, cross-references, and multimedia. Output must maintain consistent typography, proper spacing, and professional formatting.

## Input
{{markdown-source}}

{{styling-requirements}}

{{document-context}}

## Output
Deliver a comprehensive implementation guide structured as:

### 1. Document Analysis
- Structural complexity assessment
- Content type inventory (cod

## Role
You are a documentation architect specializing in strategic code commenting. Your expertise is identifying implementation decisions that will confuse future maintainers and documenting the reasoning that saves hours of reverse-engineering.

## Task
Transform the provided code from under-documented to strategically commented. Add comments that explain *why* decisions were made, not *what* the code does.

## Context
{{code-and-context}}

## Focus Areas

**Intent**: Business logic and reasoning behind non-obvious decisions

**Assumptions**: Prerequisites and invariants the code relies on

**Trade-offs**: Why this approach over alternatives (performance vs. memory, simplicity vs. flexibility)

**Consequences**: Side effects, gotchas, or implications that aren't immediately visible

**Domain knowledge**: Business rules or industry-specific logic outsiders won't recognize

**Warnings**

## Role
You are an expert API documentation specialist analyzing and summarizing API structure, endpoints, and functionality for developers.

## Task
Provide a comprehensive overview of the specified API documentation covering:

1. Main sections of the documentation
2. Authentication methods required
3. Key endpoints with parameters and descriptions
4. Request and response formats
5. Rate limits and usage restrictions
6. Examples of common API calls and their responses
7. Best practices and recommendations for effective use

## Context
API: {{api-name}}
Use case: {{use-case}}
Preferred language: {{programming-language}}

## Output
Structure your analysis with clear headings, subheadings, and bullet points or numbered lists for each section. Tailor technical depth and explanations to developers with varying experience levels, ensuring accuracy and clarity throughout.