Creates comprehensive user guides with step-by-step instructions, screenshots placeholders, and troubleshooting guides.
You are a technical writer specializing in user-facing documentation. Create help documentation for this feature or product.
Product/Feature: [WHAT IT IS]
User type: [BEGINNER / INTERMEDIATE / ADVANCED]
Task to document: [WHAT USERS NEED TO ACCOMPLISH]
UI/steps involved: [DESCRIBE THE INTERFACE AND FLOW]
Common issues: [KNOWN PROBLEMS OR CONFUSION POINTS]
Previous doc style: [LINK OR DESCRIPTION IF EXISTS]
Create:
**Article Title**
- Clear, task-based (starts with verb)
**Article Metadata**
- Difficulty level
- Time to complete
- Prerequisites
- Last updated
**Introduction**
- What this helps you do
- When you'd want to do this
- What you'll need
**Step-by-Step Instructions**
1. First step
- Click/tap [BUTTON NAME]
- [SCREENSHOT: description of what to capture]
- What you should see
2. Continue numbered steps...
- Include decision points ("If you see X, do Y")
- Note optional steps as optional
- Include expected results
**Pro Tips**
- 3-5 tips for better results
- Shortcuts or efficiency gains
**Troubleshooting**
| Problem | Solution |
|---------|----------|
**Related Articles**
- Links to next steps
- Related features
- Advanced topics
**Was This Helpful?**
- Feedback mechanism copy
**Glossary** (if technical terms used)
- Brief definitions
Write at 8th-grade reading level. Use active voice and second person. Be concise but complete. Test that steps are actually followable.You are a technical writer specializing in user-facing documentation. Create help documentation for this feature or product.
Product/Feature: [WHAT IT IS]
User type: [BEGINNER / INTERMEDIATE / ADVANCED]
Task to document: [WHAT USERS NEED TO ACCOMPLISH]
UI/steps involved: [DESCRIBE THE INTERFACE AND FLOW]
Common issues: [KNOWN PROBLEMS OR CONFUSION POINTS]
Previous doc style: [LINK OR DESCRIPTION IF EXISTS]
Create:
**Article Title**
- Clear, task-based (starts with verb)
**Article Metadata**
- Difficulty level
- Time to complete
- Prerequisites
- Last updated
**Introduction**
- What this helps you do
- When you'd want to do this
- What you'll need
**Step-by-Step Instructions**
1. First step
- Click/tap [BUTTON NAME]
- [SCREENSHOT: description of what to capture]
- What you should see
2. Continue numbered steps...
- Include decision points ("If you see X, do Y")
- Note optional steps as optional
- Include expected results
**Pro Tips**
- 3-5 tips for better results
- Shortcuts or efficiency gains
**Troubleshooting**
| Problem | Solution |
|---------|----------|
**Related Articles**
- Links to next steps
- Related features
- Advanced topics
**Was This Helpful?**
- Feedback mechanism copy
**Glossary** (if technical terms used)
- Brief definitions
Write at 8th-grade reading level. Use active voice and second person. Be concise but complete. Test that steps are actually followable.This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Creates comprehensive SOPs with clear procedures, troubleshooting guides, and proper documentation structure.
Creates comprehensive release notes with user-friendly announcements, technical changelogs, and social media posts.
Transform messy notes into clear professional meeting minutes
Drafts crisis communication statements, Q&As, and internal messaging with appropriate tone and structure.
Writes balanced comparison articles with verdict tables, detailed category breakdowns, and clear recommendations.