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.
Put useful things one tap away and distractions out of sight.
Act as a phone UX designer. My device: [iPhone or Android]. Apps I use daily: [list]. Apps that steal time: [list]. What I need the phone for: [work, family, navigation, payments].
Design the first screen for essential actions only, a second screen for intentional tasks, and a folder or search path for everything else. Set notification defaults by urgency and person, not app popularity. Define a one-week experiment with screen-time and missed-important-message checks. Include a fast rollback if the layout hides something I genuinely need.
Turn scattered photos into a collection future-you can search.
Act as a family archivist. My photos live in: [devices and services]. Approximate count: [number]. People involved: [family, privacy restrictions]. Output wanted: [searchable archive, album, print].
Design an import and backup order that preserves originals and metadata. Create a year-event naming convention, a duplicate review method, and a way to mark favorites without deleting the rest. Suggest a small first album I can finish in two hours. Include a privacy rule for children's images and a test to confirm backups restore correctly.
Reduce inbox noise while keeping receipts and real people.
Act as an inbox organizer. My mail volume: [daily count]. Providers: [accounts]. The messages I cannot miss: [people, bills, work, security]. Newsletters I enjoy: [list].
Create a safe three-pass cleanup: identify repeat senders, unsubscribe through verified paths or use filters when links look suspicious, and archive old promotions without touching receipts or account notices. Give filter rules and a weekly review queue. Define an exception for security alerts and a small-batch test before bulk moves. End with a measure of whether the inbox improved.
Check a suspicious message without clicking what it wants you to click.
Act as a security analyst. The suspicious message: [paste sender address, subject and message text, with personal details removed]. Context: [was I expecting this? which service does it claim to be from?].
Assess observable red flags: sender domain, link destination if safely visible, urgency, requested action and mismatched context. Distinguish signs from proof. Give me a safe verification route through the service's official app or address I already know, not through the message. If I clicked or entered information, give a prioritized containment checklist. Do not request passwords or one-time codes.
Act as a technology buying advisor. Current device: [model, age, condition]. Frustrations: [specific tasks]. Candidate replacement: [model and price]. Budget: [amount].
Diagnose which problems are fixable by storage cleanup, battery service, settings or repair. Compare repair, used/refurbished and new by total cost over three years, using current quotes only if I provide them. Identify two specs that matter for my tasks and three that are mostly marketing. Give a buy/wait/repair decision with the fact that would change it.
Act as a home-network troubleshooter. Internet plan: [speed]. Router: [model/age]. Home layout: [rooms/floors/walls]. Devices affected: [list]. Symptoms: [time, location, speed].
Build a safe test sequence: wired baseline if possible, near-router Wi-Fi, far-room Wi-Fi, device comparison, then peak-time repeat. Explain what each result implicates: ISP, router, interference, coverage or one device. Recommend fixes from free repositioning through mesh only if evidence supports it. Include password and firmware checks, and a simple result log.
Turn fifty open tabs into a plan without losing the useful ones.
Act as a workflow organizer. My open tabs are about: [list rough themes]. Browser: [name]. Why they stay open: [fear of forgetting, active work, research].
Create a twenty-minute triage: close obvious duplicates, save reference material into a named note with link and reason, turn action tabs into next actions with deadlines, and keep only current-task tabs open. Design a naming convention for saved links and a weekly review. Give a rule that prevents the saved-link list from becoming a second graveyard.
Act as a backup specialist for a nontechnical household. Devices and services: [list]. Critical files: [photos, documents, work]. Existing backups: [what I think I have].
Map the difference between sync and backup for my setup. Design a 3-2-1-inspired plan sized to my budget, with encryption and account recovery handled securely. Write a small restore drill: pick a noncritical file, recover an older version to a separate folder, compare it with the original, and log the result. Set frequency and failure alerts without requiring daily babysitting.
Review what apps can see without breaking the features you like.
Act as a consumer privacy advisor. Device: [platform]. Apps of concern: [list]. Features I need: [location, camera, contacts, notifications].
Build a permission audit by sensitivity and necessity. For each app, decide always, while-using, ask-each-time or deny for location, camera, mic, contacts and photos, explaining the feature tradeoff. Add advertising ID and analytics settings worth reviewing. Create a test plan so I can catch any broken workflow and reverse a change intentionally.
Act as a mobile photography coach. Phone: [model]. Subjects: [people, food, pets, travel]. Conditions that frustrate me: [low light, blur, harsh sun].
Give me a seven-day practice plan with one exercise daily. Explain lens cleaning, light direction, focus and exposure lock, composition and movement in plain language. For each subject, give a three-step setup and one common mistake. Avoid recommending paid gear unless a clear limitation of my phone demands it. Include a before-after comparison method.
Make reminders useful again instead of constant background noise.
Act as a calendar systems designer. Calendars: [work, personal, shared]. Current alerts: [defaults and pain]. Time-sensitive events: [types]. Devices: [list].
Define alert rules by event type: travel, meeting, deadline, personal appointment and all-day item. Set two alerts only where preparation and departure differ. Identify duplicated device notifications and shared-calendar noise. Write a one-week test with missed-event and annoyance measures, and a simple exception for truly urgent events.
See all app payments in one place, including the easy-to-forget ones.
Act as a subscription auditor. Payment sources: [app stores, cards, direct debits]. Known subscriptions: [list]. Statements available: [range].
Create a search plan for recurring charges across each source, including annual renewals and trial conversions. Build a tracker with service, amount, frequency, payment route, renewal date, cancellation path and last use. Classify keep, decide and cancel based on use and replacement cost. Do not assume current cancellation terms; list what to verify before the deadline.
Act as a device-lifecycle advisor. Laptop: [model, age, battery, condition]. New device status: [migrated or not]. Private data: [types]. Goal: [sell, donate, repurpose, recycle].
Give me a decision tree for value versus effort. Write a safe data-migration verification checklist, sign-out and encryption review, and vendor-specific reset steps to confirm from official documentation. If selling, provide honest listing fields and a data-safe handoff. If recycling, name how to find certified local programs rather than guessing one.
Make family access convenient without sharing your main password.
Act as a household technology advisor. Shared services: [streaming, shopping, photos, bills]. Household members: [roles and ages]. Current workaround: [password sharing, one device].
Map which services offer family profiles or delegated access to verify. For each, separate viewing from purchasing or administration. Design a permission plan with account recovery, child controls where relevant, and an offboarding step if someone leaves the household. Do not ask me to paste credentials or recovery codes.
Let urgent people through while silencing everything else.
Act as a focus-settings coach. My phone: [platform]. People who must reach me: [relationship categories, not phone numbers]. Work hours and sleep: [times]. Apps that interrupt most: [list].
Design focus modes for work, evening and sleep. Define who can bypass each and what counts as an emergency repeat call. Keep essential alarms and critical alerts working. Write a test script involving one trusted person before I rely on the setup, plus a weekly review for messages I accidentally missed.
Help trusted people find essentials if you cannot guide them.
Act as a digital-estate organizer. Jurisdiction: [country]. People I trust: [roles, not secret details]. Important online assets: [email, finances, photos, domains].
Design a secure inventory that names accounts and recovery routes without putting passwords in plain text. Distinguish emergency access features from sharing a master password. Include device unlock, two-factor recovery and service-specific legacy-contact settings to verify. Write a periodic review checklist and the legal questions for an estate professional.
Change phones without losing photos, chats or authentication.
Act as a mobile migration specialist. Old and new phone platforms: [models]. Important data: [photos, chats, authenticator, banking, notes]. Backups: [status].
Sequence backup verification, app-by-app migration, SIM or eSIM transfer and sign-in tests. Pay special attention to authenticator and chat histories; do not assume they sync. Create a checklist to test calls, payments, messages and recovery before wiping or trading in the old device. Include a rollback if the new phone fails mid-transfer.
Act as a personal knowledge organizer. Notes app: [name]. Current note count and pain: [describe]. Topics: [work, home, learning].
Design a small structure with inbox, active projects, references and archive. Set title and metadata rules using concrete examples. Give a one-hour migration plan for the top fifty notes, not a full rewrite. Define a weekly inbox-clear routine and three sample searches that prove retrieval works.
Pause a suspicious purchase before money leaves your account.
Act as a consumer-fraud analyst. Offer: [description]. Seller URL or platform: [address]. Price and payment method proposed: [details]. What concerns me: [signals].
Check the observable warning signs: domain mismatch, impossible discount, copied listings, pressure, unsupported payment rail and missing return policy. Give independent ways to verify the seller without following their supplied links. Classify proceed, investigate or avoid with reasons. If payment already happened, list immediate preservation and dispute steps without promising recovery.
Describe a device problem clearly so the first support person can help.
Act as a technical support coach. Device/service: [model, version]. Problem: [symptoms]. When it started: [date]. Recent changes: [updates, drops, settings]. Troubleshooting already done: [list].
Write a one-minute issue description with expected versus actual behavior. Build a safe minimal-reproduction sequence and evidence list (screenshots, error text, timestamps). Separate steps I can try from ones that risk data loss. Draft three questions for support about cause, warranty and escalation, and a call log template.
Leave a service without leaving data and recurring charges behind.
Act as an account-offboarding planner. Service: [name]. Data stored there: [types]. Connected apps: [list]. Billing route: [where charged].
Plan export, verification of exported files, removal of connected access, cancellation of billing and account closure in the right order. Identify shared links or teammates who may be affected. Set a follow-up check for confirmation and further charges. Do not assume deletion is immediate or complete; list exact policy questions to verify.