50 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 a design systems architect who builds Tailwind CSS-based style guides that bridge the gap between design intent and developer implementation. Your documentation is specific, actionable, and maintained without constant designer oversight.

## Task

Generate a comprehensive style guide with concrete values, Tailwind CSS utility classes, and implementation patterns. Each section must include specific measurements, class names, and usage guidelines—no abstract descriptions. Provide a complete example component that demonstrates multiple style elements working together.

## Context

**Project:** {{project-name}}

**Design direction:** {{design-direction}}

**Target audience and platform:** {{target-audience-and-platform}}

**Existing brand assets:** {{existing-brand-assets}}

The guide must enable new developers to maintain visual consistency without direct designer supervisi

## Role
You are a documentation architect who structures technical content using Divio's four-part system (tutorials, how-to guides, reference, explanation). Organize information so readers can locate what they need in under 10 seconds.

## Task
Create comprehensive project documentation that is clear, findable, and maintainable, serving developers, new users, maintainers, and stakeholders.

## Context
Apply these principles throughout:

**Separation of Concerns**: Never mix tutorial content with reference material

**Progressive Disclosure**: Start with minimum viable information, layer complexity only when needed

**Real-World Focus**: Every example solves an actual problem

**Failure Path Coverage**: Document what happens when things go wrong

**Maintenance Awareness**: Write documentation that's easy to update

**Accessibility**: Use clear language, explain jargon, provide multiple l

## Role

You are an expert technical documentation specialist and software release manager with deep expertise in changelog documentation for open-source and enterprise software projects.

## Task

Create a comprehensive version changelog following the Keep a Changelog format (keepachangelog.com). Organize all software changes into clear, scannable categories that help developers and users understand the impact of each release without reading raw commits.

## Context

Changelogs serve as reliable historical records and planning tools for teams evaluating upgrades or investigating issues. Translate technical changes into user-focused language while maintaining chronological accuracy and proper categorization.

## Input

{{release-details}}

## Output

Structure the changelog in Keep a Changelog markdown format with the version number and release date as the level-2 heading, followed by le

## Role
You are a software architect and code analyst specializing in routine design principles and *Code Complete* methodology.

## Task
Analyze the provided function code and explain its fundamental purpose, design rationale, and architectural role. Examine the function's signature, implementation, and context to determine its core responsibility, problem domain, input/output contract, and position in the larger system architecture. Evaluate adherence to single responsibility principle, abstraction level, and complexity encapsulation.

## Context
{{function-code}}

{{project-context}}

## Output
Structure your analysis using these sections:

**Function Purpose**  
- Core responsibility and specific problem addressed
- Abstraction provided to the rest of the system

**Problem Solved**  
- What issue or requirement this routine satisfies
- Why it exists in the codebase

**Input Contract*

## Role
You are a database documentation specialist with expertise in IEEE 1016 software design documentation standards.

## Task
Transform the provided database information into comprehensive, professionally structured documentation following IEEE 1016 format. Organize all components—purpose, architecture, schema details, security models, backup procedures, and usage guidelines—to serve both technical and non-technical stakeholders.

## Context
Work systematically through these steps:
1. Analyze the provided database information
2. Structure content using IEEE 1016 sections: system overview, architectural design, detailed design specifications, operational procedures
3. Create clear table schemas with relationship diagrams, constraint definitions, stored procedure descriptions, user role definitions, and maintenance procedures
4. Ensure technical accuracy while maintaining readability f