AI Prompts for IT Support

Help me with Windows troubleshooting planning. Task: Build a startup-problem triage separating boot login and app launch. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with Windows troubleshooting planning. Task: Compare baseline and incident resource snapshots to isolate a slow-PC pattern. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]; [baseline and incident CPU memory and disk snapshots with timestamps]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with Windows troubleshooting planning. Task: Explain an update failure with evidence needed before changing settings. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with Windows troubleshooting planning. Task: Compare a local account problem with a device-wide problem. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with Windows troubleshooting planning. Task: Build an application-crash log with time version and reproduction steps. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with Windows troubleshooting planning. Task: Identify categories responsible for storage growth using two inventory snapshots. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]; [two storage inventories with dates and category sizes]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with Windows troubleshooting planning. Task: Diagnose a missing-device symptom from anonymized Device Manager information. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with Windows troubleshooting planning. Task: Draft a rollback plan for an approved configuration change. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with Windows troubleshooting planning. Task: Compare sleep hibernate and shutdown symptoms in the supplied record. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with Windows troubleshooting planning. Task: Create a support handover note with attempted checks and results. My inputs: [Windows version]; [device model]; [exact error]; [recent changes]; [admin permissions]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with macOS support planning. Task: Build a Mac startup issue checklist distinguishing user and system symptoms. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with macOS support planning. Task: Create an application-permission review using supplied prompts and settings. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with macOS support planning. Task: Compare a Finder display issue with an actual missing-file concern. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with macOS support planning. Task: Compare app caches user documents and system categories in a supplied storage inventory. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]; [anonymized inventory of app caches user documents and system categories]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with macOS support planning. Task: Build a safe external-display diagnosis from cable and monitor details. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with macOS support planning. Task: Explain an app compatibility question requiring vendor support evidence. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with macOS support planning. Task: Create a macOS update-preparation checklist with backup verification. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with macOS support planning. Task: Compare login-item symptoms before proposing an approved change. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with macOS support planning. Task: Draft a support record for recurring beachball symptoms. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with macOS support planning. Task: Identify data needed to investigate unexpected battery drain. My inputs: [macOS version]; [Mac model]; [exact symptom]; [recent changes]; [permission scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with Linux support planning. Task: Compare the same Linux error across two environments to isolate a configuration difference. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]; [the same anonymized error and read-only configuration details from both environments]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with Linux support planning. Task: Build a service-failure evidence checklist from anonymized log excerpts. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with Linux support planning. Task: Compare file permissions ownership and execution rights conceptually. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with Linux support planning. Task: Create a package-update troubleshooting plan requiring official repository evidence. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with Linux support planning. Task: Explain filesystem capacity versus inode exhaustion using provided figures. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with Linux support planning. Task: Draft a safe read-only diagnostic command plan with explanations. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with Linux support planning. Task: Compare user-shell configuration issues with system-wide failures. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with Linux support planning. Task: Create a support checklist for a mounted-drive accessibility problem. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with Linux support planning. Task: Review a proposed shell command for destructive flags and assumptions. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with Linux support planning. Task: Build an escalation summary for a recurring scheduled-task failure. My inputs: [distribution and version]; [non-sensitive error text]; [recent changes]; [access level]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with basic network troubleshooting. Task: Separate DNS failure from basic network reachability symptoms. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.

Help me with basic network troubleshooting. Task: Build an IP-configuration review using anonymized address examples. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with basic network troubleshooting. Task: Create a connectivity evidence table across several affected devices. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with basic network troubleshooting. Task: Explain gateway subnet and DNS roles in the supplied layout. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with basic network troubleshooting. Task: Compare an application outage with a whole-network outage. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with basic network troubleshooting. Task: Plan read-only tests that localize a problem without scanning others. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with basic network troubleshooting. Task: Create a network-change record with an approved rollback checkpoint. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with basic network troubleshooting. Task: Diagnose a duplicate-address suspicion without declaring it confirmed. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with basic network troubleshooting. Task: Explain what a latency measurement does and does not prove. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with basic network troubleshooting. Task: Draft an ISP support note with timestamps and reproducible evidence. My inputs: [network layout]; [device OS]; [exact symptom]; [affected devices]; [permitted checks]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with Wi-Fi connectivity support. Task: Compare weak signal interference and internet-service symptoms. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Provide a self-check section with expected outcomes and warning signs that the proposed approach is inappropriate.

Help me with Wi-Fi connectivity support. Task: Build a Wi-Fi issue map using location time and affected device. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Finish with a checklist that tests whether the deliverable meets the stated goal. Identify missing inputs and do not invent them.

Help me with Wi-Fi connectivity support. Task: Create a connection-failure checklist without requesting the Wi-Fi password. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Show how each recommendation follows from the supplied evidence. Flag contradictions, uncertain facts and anything requiring a current official source.

Help me with Wi-Fi connectivity support. Task: Explain band and channel concepts using the router documentation. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Verify units, dates, constraints and internal consistency where relevant. Include one independent way I can check the result.

Help me with Wi-Fi connectivity support. Task: Review a coverage complaint without promising one router location fixes it. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include an example using clearly labeled fictional data if necessary, then explain how I should validate it against my actual inputs.

Help me with Wi-Fi connectivity support. Task: Compare one-device and all-device disconnection patterns. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. State the assumptions that most affect the result and describe what would change if an assumption is false.

Help me with Wi-Fi connectivity support. Task: Draft a guest-network policy checklist for authorized administration. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. End with three targeted review questions and explicit pass criteria; avoid presenting guesses as established facts.

Help me with Wi-Fi connectivity support. Task: Create a before-and-after evidence plan for an approved Wi-Fi change. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Include a brief counterexample or edge case that tests the limits of your explanation. Trace factual claims to provided material.

Help me with Wi-Fi connectivity support. Task: Explain why signal strength alone does not determine throughput. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Distinguish what can be checked from the supplied information from what needs further evidence; list the smallest useful follow-up inputs.

Help me with Wi-Fi connectivity support. Task: Build a support handover for intermittent Wi-Fi with measurement limits. My inputs: [router model]; [client devices]; [room layout]; [symptoms]; [allowed configuration scope]. Adapt the task to [desired detail level and output length]. Produce the concrete artifact named in the task, with labeled sections or a table where useful. Explain the key reasoning and make the output directly usable with my supplied inputs. Start with reversible diagnostic steps. Protect personal data: use anonymized examples and never ask for passwords, tokens or private keys. Flag admin permissions, data-loss risk and organization-policy dependencies before any proposed change. Do not bypass access controls. Review the output for unsupported claims, omitted exceptions and unrealistic steps. Explain the corrections you made.