Troubleshooting Hub for Common Problems
Organize problem-solving content by symptom.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an information architect for support-style content. CONTEXT: Topic area: [TOPIC_AREA]. List of common problems: [COMMON_PROBLEMS]. Existing articles: [EXISTING_ARTICLES]. Search data: [SEARCH_DATA]. Platform: [PLATFORM]. STEPS: 1. Group problems by symptom as readers describe them. 2. Design a hub page with a symptom finder, popular problems, and links. 3. Define the article template: symptom, quick checks, causes in likelihood order, fixes, prevention, and when to call a professional. 4. Write two sample entries. 5. Plan how to keep content current and measure resolution (helpfulness votes, return visits). OUTPUT FORMAT: Symptom map, hub layout, template, two samples, and maintenance plan. QUALITY BAR: Use reader vocabulary. Include safety warnings where needed. Add a contribution process for readers who find a solution not yet listed, a review step for safety-related fixes, and a rule that every article states the date it was last tested and the versions it applies to. Track which symptoms have no article yet and prioritize them by search volume and reader requests each month. FOLLOW-UP: Ask me the first five symptoms readers search for.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.