Claude Prompts for Documentation
Copy, adapt, and reuse these prompts to write, update, reorganize, translate, and audit documentation with Claude connected to OpenDocs.
The prompt library
Write
- “Draft a getting-started page for [product] in the [space] space.”
- “Write an FAQ page answering these five questions: [list].”
- “Turn these meeting notes into a how-to article and leave it unpublished for review.”
- “Write a release notes entry for this change: [description].”
- “Draft an onboarding checklist for new [role] hires.”
- “Summarize this long page into a short quick-reference version and publish it alongside the original.”
Update
- “Find pages that mention [old term] and update them to [new term].”
- “Update the Setup page with these new steps: [steps].”
- “Rewrite the introduction of [page] to be clearer and shorter.”
- “Check the Pricing page against our current plans and fix anything out of date.”
Reorganize
- “Move the Billing page under Account Settings and reorder it above Security.”
- “Split the Onboarding page into three separate pages: Setup, Configuration, and Go-Live.”
- “Merge these two pages about API keys into one page and archive the duplicate.”
- “Reorganize the Troubleshooting section by product area instead of by date.”
Translate
- “Translate the Setup page into Spanish and Portuguese and publish both.”
- “Check which pages in [space] are missing a Spanish translation.”
- “Re-translate [page] into all its existing languages now that the source changed.”
- “Publish this page in Spanish, Portuguese, and German, keeping the same structure.”
Audit
- “What did readers search for this month that found nothing?”
- “Find pages that haven’t been updated in over a year.”
- “List every page that still mentions [deprecated feature].”
- “Check the [space] page tree for broken internal links.”
SOPs
- “Interview me about how we handle [process] and draft an SOP from my answers.”
- “Add an exceptions and escalation section to the [SOP name] page.”
- “Publish this SOP for the Operations team, unpublished until it’s approved.”
- “Compare the published [SOP name] page to what I just described and flag anything that’s changed.”
API docs
- “Draft a reference page for the [endpoint] endpoint with request and response examples.”
- “Update the authentication page to describe the new API key format.”
- “Write a quickstart that gets a new developer from signup to their first API call.”
- “Find every API reference page that still shows the old base URL and fix it.”
Frequently asked questions
Do these prompts work in claude.ai, Claude Desktop, and Claude Code?
Yes. Once OpenDocs is connected, the same prompts work in claude.ai, Claude Desktop, and Claude Code. claude.ai and Claude Desktop connect over OAuth on every plan; Claude Code connects with an OpenDocs API key, which needs the Enterprise or Compliance plan.
Why does Claude sometimes ask before finishing a prompt?
Claude asks before actions that remove or replace content, such as deleting a page or overwriting its text, so you can confirm before anything is lost. Every change it does make is still saved in page history.
Can I combine several of these prompts into one request?
Yes. Claude can chain steps in a single prompt, for example searching for outdated pages and updating each one it finds, though breaking a large change into a few prompts makes it easier to review as you go.
Do I need to know the exact space or page name for these prompts to work?
It helps, but it is not required. Claude can search across your spaces and pages first, and ask you to confirm which one you meant before making a change.