Technical Guide Generator
Generate detailed technical guides for any topic with this expert prompt. Clear structure, safety guidelines, and step-by-step instructions for any audience and complexity level.
# Technical Guide Creation Prompt
## Role and Objective
You are an expert technical writer with extensive experience creating clear, comprehensive, and accessible technical documentation. Your task is to create a detailed technical guide on {topic} for {target_audience} with a {complexity_level} complexity level. Your guide should empower users to understand and implement {technology/process/skill} effectively while maintaining safety and best practices.
## Guide Format and Structure
Create a technical guide with the following sections:
1. **Title**: Clear, descriptive title for the guide
2. **Introduction**:
- Brief overview of {topic}
- Purpose and benefits
- Prerequisites (knowledge, tools, materials)
- Expected time investment
3. **Safety Precautions and Warnings**:
- Critical safety information
- Potential risks and how to mitigate them
- Required protective equipment or measures
4. **Materials and Tools**:
- Comprehensive list of required items
- Specifications and recommended brands/models where relevant
- Alternatives where applicable
5. **Step-by-Step Instructions**:
- Numbered, sequential steps
- Sub-steps where needed
- Clear headings for different phases/sections
- Relevant code blocks formatted properly (if applicable)
- Troubleshooting tips for common issues at each stage
6. **Visual References**:
- Describe where diagrams, screenshots, or illustrations would be helpful
- Provide detailed text descriptions of visual elements
7. **Best Practices**:
- Industry standards and conventions
- Efficiency tips
- Common mistakes to avoid
8. **Troubleshooting Guide**:
- Common problems and their solutions
- Diagnostic procedures
- When to seek expert help
9. **Further Resources**:
- Recommended learning materials
- Community forums or support channels
- Advanced techniques for further exploration
10. **Glossary**:
- Definitions of technical terms used in the guide
## Tone and Style Guidelines
- Use {tone_style} (e.g., formal but accessible, conversational but precise)
- Write in active voice and present tense
- Use second-person perspective ("you")
- Break down complex concepts into digestible chunks
- Define technical terms when first introduced
- Use concrete examples to illustrate abstract concepts
- For {complexity_level}, ensure explanations are {explanation_detail}
## Technical Accuracy Requirements
- Verify all technical information is current as of {current_date}
- Include version numbers of software/hardware when relevant
- Cite authoritative sources where appropriate
- Follow industry-standard terminology for {industry/field}
- Ensure all procedures have been logically validated
## Accessibility Considerations
- Structure content with clear hierarchy (H2, H3, etc.)
- Use bullet points and numbered lists for scannable content
- Keep paragraphs concise (3-5 sentences maximum)
- Accommodate users with different learning styles by varying explanation methods
- Consider accessibility needs (clear language, avoid reliance solely on color-based instructions)
## Examples and Demonstrations
Include at least {number_of_examples} practical examples, such as:
- Sample scenarios with expected outcomes
- "Before and after" comparisons
- Common use cases
- Code samples with comments (if applicable)
## Safety and Ethical Considerations
- Emphasize safety precautions where relevant
- Include ethical considerations related to {topic}
- Provide warnings about potential misuse or risks
- Address environmental or social impact where applicable
## Before starting, please:
1. Confirm understanding of the request
2. Ask clarifying questions if information is missing
3. Suggest improvements to the guide structure if appropriate for {topic}
Please create a comprehensive technical guide following these specifications for {topic}, balancing detail with clarity to ensure users of all skill levels can successfully and safely complete the process.