Act as a practical specialist helping me with saying no to a home network. My context: [current setup, goals, constraints].
1. Describe the request and who is asking
2. Weigh what saying yes would cost me
3. Draft a kind, clear no with an alternative if useful
4. Give me a shorter backup version and a line for pushback
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#digital life#say-no
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Move logins without locking yourself out halfway through.
Act as a personal security coach. My current password setup: [browser saves, old manager, reused passwords, devices]. New manager: [name]. My confidence: [level].
Write a staged migration plan: (1) inventory accounts and choose the email and banking accounts to move first; (2) set a strong master password and recovery method without asking me to paste either into this chat; (3) import and dedupe safely, then change reused passwords on high-risk accounts; (4) turn on MFA and store recovery codes privately; (5) test sign-in on a second device before deleting old copies. Include a rollback plan and a checklist for spotting a failed import. Do not print or request secrets.
Make the important accounts harder to hijack without losing access.
Act as an account-security coach. My accounts by category: [email, bank, social, shopping, work]. MFA methods available: [authenticator, passkey, SMS, hardware key]. Devices and backup access: [describe].
Prioritize accounts by takeover impact. For each tier, recommend the best available MFA method and explain its failure mode. Design a recovery plan that works if I lose my primary phone, with codes stored securely and separately. Give a step-by-step activation order that does not lock me out, a final test checklist, and the phishing signals to watch even after MFA is on. Never ask me to share codes or recovery keys.
Find the files that matter and stop paying for duplicates.
Act as a digital organizer. Storage services: [list]. Main file types: [photos, work docs, scans, backups]. Space used: [rough estimate]. Biggest irritation: [what cannot be found].
Map a cleanup in four passes: locate critical originals, identify true duplicates by content rather than filename alone, archive old projects, then remove trash only after backup verification. Propose a simple folder and naming convention with examples. Distinguish sync from backup, and give a safe deletion test on a small sample before any bulk action. End with a monthly fifteen-minute maintenance ritual.