AI Prompts for Gemini for Technical Writing
20 tested prompts across 4 stages. Works with ChatGPT, Claude, and Gemini.
Most people try to use AI for Gemini for Technical Writing with a single vague prompt and get generic results. This guide takes a different approach: 4 targeted stages, from Plan your document through Specific document types, each with a prompt that gives the AI exactly the context it needs. Write technical documentation, guides, and communications that are clear, accurate, and actually useful. Works with ChatGPT, Claude, and Gemini.
Stage 1
Plan your document
Start here to define your audience, scope, and document structure.
Identify the audience
I need to write [TYPE OF DOCUMENT] about [TOPIC]. My audience is [DESCRIBE: DEVELOPERS / EXECUTIVES / END USERS]. What level of technical detail is appropriate and what background can I assume?
Create an outline
Create an outline for [TYPE OF DOCUMENT: API REFERENCE / HOW-TO GUIDE / TECHNICAL SPEC / README]. Topic: [TOPIC]. Include all major sections a reader needs in logical order.
Choose the format
What format works best for this content: [DESCRIBE WHAT YOU NEED TO DOCUMENT]? Should I write a README, a runbook, a wiki page, step-by-step instructions, or a reference document?
Set the writing goal
The goal of this technical document is [DESCRIBE GOAL: ENABLE USERS TO COMPLETE A TASK / EXPLAIN AN ARCHITECTURE DECISION / DOCUMENT AN API]. What is the single most important thing readers should take away?
Research the content
What should I cover in a technical document about [TOPIC]? List the key concepts, terms, and processes I need to include, and note what questions readers are most likely to have.
Stage 2
Write the content
These prompts help you write each section clearly and engagingly.
Write an introduction
Write an introduction for a technical document on [TOPIC]. State the purpose, define the scope, identify the target audience, and tell readers what they will be able to do after reading.
Write step-by-step instructions
Write step-by-step instructions for [TASK]. Target: someone who has [DESCRIBE THEIR EXPERIENCE LEVEL]. Use numbered steps, include code blocks where needed, and list prerequisites upfront.
Explain a technical concept
Explain [TECHNICAL CONCEPT] for [DESCRIBE AUDIENCE]. Use a concrete analogy, a real-world example, and avoid unnecessary jargon. Make it accessible without oversimplifying.
Write a README
Write a README for [PROJECT / TOOL / LIBRARY]. Include: what it does, installation instructions, a quick start example, configuration options, and how to contribute.
Document an API endpoint
Document this API endpoint: [DESCRIBE OR PASTE THE ENDPOINT]. Cover: HTTP method, URL, description, request parameters, request body, response schema, error codes, and a complete example.
Stage 3
Edit and improve
Use these prompts to review, tighten, and polish your technical writing.
Simplify technical text
Simplify this technical text without losing accuracy: [PASTE TEXT]. Replace jargon with plain language, shorten sentences, and make it accessible to [DESCRIBE AUDIENCE].
Make it more scannable
Reformat this technical document for better scannability: [PASTE TEXT]. Add headers, bullet points, numbered steps, code blocks, and remove walls of text.
Improve clarity
Improve the clarity of this technical explanation: [PASTE TEXT]. Identify ambiguous statements, missing context, and places where the logic is hard to follow.
Add examples
Add concrete examples to make this technical content more understandable: [PASTE TEXT]. Examples should be minimal, realistic, and directly illustrate the concept.
Check accuracy
Review this technical content for potential inaccuracies or outdated information: [PASTE TEXT]. Flag anything that might be wrong or needs verification.
Stage 4
Specific document types
These prompts help you write specific document types like READMEs, runbooks, and specs.
Write a runbook
Write a runbook for [OPERATIONAL PROCEDURE]. Include: when to use it, prerequisites, step-by-step instructions, what to do if each step fails, and expected outcomes.
Write a post-mortem
Write a blameless post-mortem for this incident: [DESCRIBE WHAT HAPPENED]. Cover: timeline, root cause, impact, what went well, what did not, and action items.
Write a technical proposal
Write a technical proposal for [INITIATIVE]. Cover: problem statement, proposed solution, alternatives considered, implementation plan, risks, and success metrics.
Write release notes
Write user-facing release notes for this version: [DESCRIBE CHANGES]. Write from the user's perspective and group by: new features, improvements, bug fixes, and breaking changes.
Write an architecture overview
Write an architecture overview for [SYSTEM / APPLICATION]. Cover: the main components, how they interact, key design decisions, and data flow. Target: [TECHNICAL TEAM / NEW ENGINEERS].
Frequently asked questions
What is the most important principle of technical writing?+
Clarity over cleverness. Technical documentation exists to help readers accomplish something. Every sentence should either inform, instruct, or orient the reader. If a sentence does not do one of those things, cut it.
How do I write technical documentation that is actually read?+
Lead with the most important information, use headings so readers can scan, show code examples early, and make the quick start path obvious. Most readers skim first and only read deeply if the scan looks promising.
Can Gemini write technical documentation about my specific code?+
Yes. Paste your code, API definitions, or system descriptions into Gemini and ask it to generate documentation. It can write README sections, API references, function documentation, and step-by-step guides from code.
How do I maintain documentation accuracy as code changes?+
Build documentation updates into your code review process. When a PR changes a public API or user-facing feature, require a docs update as part of the review. Gemini can quickly update existing docs when you paste changed code alongside them.
What is the difference between a how-to guide and a reference document?+
A how-to guide walks through completing a task step by step (goal-oriented). A reference document describes all available options exhaustively (information-oriented). Both are needed: the how-to gets people started, the reference helps them go deeper.
Other prompt packages you might like
AI Prompts for ChatGPT for Technical Writing
Write clearer, more effective technical documentation, reports, and communications using ChatGPT..
See prompts
AI Prompts for Claude for SEO
SEO content that reads like it was written for search engines rather than humans ranks poorly and converts worse.
See promptsAI Prompts for Cursor for Documentation
Write clear, comprehensive documentation for your code — from inline comments to full API docs — using Cursor..
See prompts