Advanced AI Library. Three Ways to Use It.

Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.

Each resource is structured for all three.

Category counts cover all available entries.

Tag

Troubleshooting Guides

Entries tagged Troubleshooting Guides across the library, including matching entries from the original collection.

Explore entries

Develop a Comprehensive Troubleshooting Guide for Enhanced User Support

Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.

This prompt is designed to help content creators develop detailed troubleshooting guides that empower users to resolve common issues on their own. The focus is on identifying frequent problems, logically organizing solution steps, and incorporating visual aids to improve clarity and engagement. By creating structured, easy-to-follow guides, businesses can enhance user satisfaction and reduce support requests.

{
  "role": "You are a technical writer specializing in creating effective troubleshooting guides.",
  "goal": "Create a troubleshooting guide for [product\/service] addressing [common issue] with clear, step-by-step instructions to enhance user independence and satisfaction.",
  "context": [
    "Identify common issues faced by users of [product\/service].",
    "Organize the solution steps logically, ensuring they are easy to follow.",
    "Incorporate visual elements such as diagrams or screenshots to aid understanding.",
    "Provide tips for users to prevent the issue in the future."
  ],
  "output": [
    "A detailed troubleshooting guide with a clear title and problem description.",
    "Step-by-step instructions with accompanying visuals for each step.",
    "A section on common pitfalls and how to avoid them.",
    "Tips for maintaining [product\/service] to prevent similar issues."
  ],
  "toneStyle": "Clear, concise, and user-friendly.",
  "constraints": [
    "Ensure the guide is accessible to users with varying levels of technical expertise.",
    "Avoid overly technical jargon that may confuse users."
  ],
  "startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
  "followUpQuestions": "After presenting the result, only if resolving which diagnostic branch or instruction to clarify would materially improve its usefulness, ask up to [3] concise follow-up questions about that decision. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
  "successCriteria": [
    "Troubleshooting steps follow a usable diagnostic sequence and clarify when an issue remains unresolved.",
    "The response delivers a detailed troubleshooting guide with a clear title and problem description; step-by-step instructions with accompanying visuals for each step.",
    "The response also delivers a section on common pitfalls and how to avoid them; tips for maintaining the specified product/service to prevent similar issues.",
    "The result respects these original limits: ensure the guide is accessible to users with varying levels of technical expertise; avoid overly technical jargon that may confuse users. Factual claims and examples or results presented as real are supported by supplied or verifiable evidence; missing evidence is identified without inventing results.",
    "Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
  ]
}

End of results.