promt: I want to find old or deleted iMessage conversations that may still exist in my iPhone backup data. I'm connecting my iPhone to my computer via USB. Act as an iOS forensic recovery specialist. Handle the technical work using Claude Code. STEP 1 — CONNECT Detect my connected iPhone. Identify its iOS version. Help me establish a trusted USB connection. Use Apple Devices, Finder, or compatible open-source tools. STEP 2 — EXTRACT Create a local backup of my connected iPhone. Check for existing local backup snapshots that might contain older conversations. Don't overwrite existing backups. Work only with local data. Never upload my messages anywhere. STEP 3 — INVESTIGATE Locate the iOS backup manifest and Messages database (sms.db). Examine available iMessage/SMS records and attachments. Look for conversations that may have survived in older backup snapshots or recoverable database artifacts. Compare message timestamps and backup dates. Identify conversations that may no longer appear on my iPhone. STEP 4 — RECOVER Show me what you actually found. Recover available messages, timestamps, contacts and attachments. Export recoverable conversations into readable HTML or PDF files. Distinguish recovered messages from incomplete traces or missing data. IMPORTANT RULES No jailbreak. Never reset or restore my iPhone. Don't delete or modify original backups. Ask before installing software or exporting private data. If backups are encrypted, request the password securely. If Messages in iCloud prevents extraction, explain why. Don't invent messages or promise recovery of permanently erased data. Do as much as possible automatically. Start by detecting my connected iPhone, then guide me through anything requiring manual approval.

Want your TV to look like one of these? Copy this into Claude Code. It'll help identify your TV, check compatibility, and install or adapt an open-source home screen. FULL PROMPT ↓ You are my Smart TV customization engineer. I want to replace or customize my TV's home screen using one of these four open-source projects: 3D Home TV OS github.com/Rod292/3d-home-tv… TV Bookshelf github.com/griffincockfoster… Tigris github.com/lesnolie/Tigris Couchy Launcher github.com/conreo/couchy-lau… Your job is to identify my TV, determine which projects are actually compatible, and help me install or adapt my preferred interface safely. Do not assume every Smart TV runs Android. STEP 1 — IDENTIFY MY TV Ask me for: My TV brand and exact model, or a photo of its model label. My TV's OS and firmware version, if known. Whether I'm using Windows, macOS, or Linux. Whether my TV and computer share a local network. Whether I want a 3D, Apple-like, minimalist, or custom interface. Identify whether my TV runs Android TV, Google TV, Samsung Tizen, Samsung pre-Tizen, LG webOS, Apple tvOS, or another system. STEP 2 — RESEARCH COMPATIBILITY Read the current README, installation documentation, release notes and known issues for all four repositories. Compare their minimum OS requirements, hardware requirements, available releases, installation methods and known limitations. Important: Tigris targets Android TV, with official APK support starting at Android 9. TV Bookshelf targets Android TV and may require building from source. Couchy targets Android TV / Google TV, Android 5.0+. 3D Home TV OS is a larger project requiring a compatible TV, a running local bridge and additional hardware for real smart-home control. For the 3D option, ask whether I have smart lights, Home Assistant, Hue, a suitable always-on computer, and an iPhone with LiDAR or another way to build a floor plan. If I own a Samsung Tizen, pre-Tizen, LG webOS or other unsupported TV, explain why these Android launchers cannot simply be installed. Consider an external Android TV / Google TV streaming device where appropriate. Never claim native compatibility without evidence. STEP 3 — HELP ME CHOOSE Present the compatible options with: How each interface looks. What features actually work. Setup difficulty. Additional hardware or software required. Known limitations. Whether the original home screen can be restored. Recommend the best fit for my TV and preferences. Wait for my choice before installing anything. STEP 4 — PREPARE THE INSTALLATION After approval: Confirm that I own or am authorized to modify the TV. Check connectivity and device compatibility. Identify required tools. Install trustworthy dependencies only with permission. Inspect downloaded packages, source repositories and release files. Explain every required permission. For compatible Android TVs, use official Android SDK Platform-Tools and ADB where supported. Guide me through enabling debugging and approving the computer on the TV. Never bypass authentication or security controls. STEP 5 — PRESERVE MY EXISTING SETUP Before making changes: Record the current default launcher. Back up relevant settings and configuration. Preserve installed apps and accounts. Prepare a working rollback procedure. Explain how to restore the original home screen. Do not root, flash firmware, factory reset, uninstall system apps, disable stock launchers or system services, or enter hidden service menus. Ask before enabling special permissions, accessibility services, background services or persistent debugging. STEP 6 — INSTALL OR ADAPT Follow the selected project's official installation instructions. Use the correct approach for my TV model and operating system. If source compilation is required, inspect the build instructions and dependencies before proceeding. If small compatibility changes are needed, propose them, explain the risks and request approval. Keep everything local unless the selected project requires a documented external service that I explicitly approve. Do not expose ADB or TV controls to the public internet. STEP 7 — TEST THE REAL TV Verify: The interface opens on my physical TV. The remote works. Installed apps launch correctly. The Home button behaves as expected. Settings and input switching remain accessible. The original launcher can be restored. Test reboot and standby behavior only with my permission. For the 3D project, distinguish simulated lights from real connected smart-home devices. Ask before switching real lights or devices. Never mark anything as working without evidence. STEP 8 — FINISH Give me: The installed project's name and version. Exact setup and reconnect commands. Verified working features. Anything that failed or remains untested. Customization instructions. How to disable debugging when finished. A complete rollback procedure. If my TV cannot support any of these interfaces directly, explain the best compatible alternative. Start by asking for my TV model or a photo of its label. I want you to help me actually set this up, not just describe how it works.

1/ Step 1: make an encrypted backup. Plug the iPhone into a Mac, open Finder, select the phone, tick “Encrypt local backup” and back up. Encryption matters here: an encrypted backup includes far more of the data the checks need. Write the password down. 2/ Step 2: let Claude Code run the scan. Open Claude Code in an empty folder and ask: “Install Amnesty’s Mobile Verification Toolkit (mvt). Download the latest public spyware indicators. Decrypt my iPhone backup at [path] into a new folder and check it against those indicators. Read only: don’t modify the backup or the phone. Explain every result in plain English.” 3/ Step 3: check the system logs. On the iPhone, press both volume buttons and the side button together for a second. That records a sysdiagnose. After about 10 minutes it appears in Settings → Privacy & Security → Analytics & Improvements → Analytics Data. AirDrop it to the Mac and ask: “Open this sysdiagnose. Check shutdown.log and the process logs for anything that isn’t part of iOS, anything that delayed a reboot, or any name matching known spyware indicators. Show me the file and line for every finding.” 4/ Step 4: if it finds something. Don’t wipe the phone first. Keep a copy of the backup and the full report. From a different device, change your Apple ID password, then contact Access Now’s Digital Security Helpline or Amnesty’s Security Lab. Both help people with suspected spyware for free. Update iOS and turn on Lockdown Mode. 5/ Rather run it all at once? Paste this into Claude Code: “You are a mobile forensics assistant. SCOPE: my own iPhone backup at [path] and a sysdiagnose at [path]. Read only: never modify, delete or upload anything. If a step needs to write to the phone, skip it and tell me. GOAL: tell me in plain language whether anything on this phone matches known spyware. STEPS: install mvt, download the latest public indicators, decrypt the backup into a new folder, run the backup check, then review the sysdiagnose logs. For every finding, show the file, the matching indicator and its source. Mark anything you can’t confirm as UNCONFIRMED. End with a summary: clean, suspicious or infected, and what to do next.”

full prompt: "This is my own robot vacuum connected to my home network. I want to know if someone else could be watching or listening through it. I've attached a photo of the robot or its Settings → About screen. Use Claude Code to investigate what this device can access, transmit, and expose. Help me find evidence of unauthorized access, not just theoretical risks. The check: step 1 → Identify the exact manufacturer, model, firmware and operating system. Find out whether it has a camera, microphone, speaker or remote-viewing feature. step 2 → Research its documented security vulnerabilities, previous hacking incidents and manufacturer advisories. Use credible sources and provide links. step 3 → Check what data it can send over the internet: live video, audio, room maps, photos, device telemetry and cloud recordings. Explain which features are actually supported. step 4 → Walk me through checking the manufacturer's app for unknown accounts, shared users, active sessions, unfamiliar devices, remote-viewing history and security alerts. Tell me if the app doesn't expose this information. step 5 → If I'm running Claude Code locally, help identify the robot on my Wi-Fi and inspect available network information. Ask permission before testing anything. Only investigate devices I own. step 6 → Look for evidence of suspicious access: unexpected logins, unfamiliar sharing permissions, unexplained camera activity, unusual remote commands or security warnings. Don't treat ordinary cloud connections as proof of spying. step 7 → If something suspicious appears, explain what it means, how confident you are and how to secure the device. Guide me through revoking unknown access, changing passwords, enabling 2FA, updating firmware and disabling remote viewing where supported. Final report: → Does this robot have eyes or ears? → Can someone access them remotely? → Are there known security vulnerabilities? → Is there actual evidence of unauthorized access? → What should I change immediately? Don't root the robot, exploit vulnerabilities, bypass authentication or access anyone else's devices. Never claim someone is watching me without evidence. If the manufacturer doesn't expose access logs, say that the check is inconclusive. Give me exact instructions for my model, not generic advice. Start by identifying my robot vacuum from the photo. When possible, perform the checks yourself instead of just explaining them. I want to know who, if anyone, can see through the thing cleaning my floors."

FULL PROMPT — Turn Your Smart TV Into a Claude-Controlled TV "This is my own Smart TV connected to the same home network as my computer. I want Claude Code to discover it, connect to it, and let me control it using natural-language commands. I've attached a photo of my TV's model label or Settings → About screen. If the model isn't clear, ask me for it. GOAL: Turn Claude Code into a working AI remote control for my TV. Done means: Claude can execute supported commands on my real television, such as changing volume, navigating menus, switching inputs, opening apps, and playing a video when supported. I should be able to say 'Claude, turn up the volume' or 'Open YouTube' without manually typing terminal commands. STEP 1 — IDENTIFY Identify the TV's manufacturer, exact model, year, operating system, and supported control methods. Determine whether it uses Android TV, Google TV, Samsung Tizen, older Samsung Smart TV, LG webOS, Roku, Fire TV, or another platform. Never assume every TV runs Android or supports ADB. STEP 2 — DISCOVER Confirm this computer can access my home network. Discover the TV using appropriate local discovery methods, such as SSDP, mDNS, or documented device APIs. Find its local IP address and available control services. If discovery fails, show me exactly where to find the TV's IP address. Explain any compatibility limitations before continuing. STEP 3 — CONNECT Choose the correct method for my TV: Android TV / Google TV / Fire TV: investigate supported ADB or official remote-control interfaces. Samsung Tizen: investigate supported local remote-control APIs and pairing. Samsung 2014 / older Smart TV: investigate compatible legacy Samsung remote-control protocols, including encrypted PIN pairing where applicable. LG webOS: investigate supported WebSocket remote-control pairing. Other TVs: identify an appropriate documented local control interface. Use established open-source libraries or official tools where appropriate. Install required software from trustworthy sources after my approval. If no compatible controller exists, build a minimal local controller using the documented protocol. Never use an incompatible protocol just because it's easier. Guide me through any required on-screen permissions, PIN codes, or developer settings. STEP 4 — TEST Once connected, test these actions one at a time: Increase volume by one step. Decrease volume by one step. Open the home screen or main menu. Navigate using remote-control commands. Open YouTube or another available app, if supported. Attempt to play a video I choose, if the TV supports this. Ask me to confirm what happened on the screen whenever the TV cannot provide reliable feedback. Don't claim success until a command actually works. STEP 5 — NATURAL-LANGUAGE CONTROL Create a reusable local controller and teach Claude Code how to operate it. I want to type or dictate requests such as: 'Turn the volume up by 5.' 'Open YouTube.' 'Switch to HDMI 1.' 'Play the Interstellar trailer.' 'Pause the video.' 'Go back to the home screen.' Translate each request into supported TV commands and execute them automatically. Don't make me manually type terminal commands once the controller is configured. STEP 6 — DEMO Help me demonstrate the result on camera. Show a natural-language request in Claude Code, the actual command execution, and the physical TV responding. Keep the demonstration real, visible, and reproducible. RULES: Never root, flash, or factory-reset the TV. Never enter hidden service menus. Never uninstall or disable system apps. Ask permission before installing software or changing settings. Never expose TV controls to the public internet. Never enter passwords or approve pairing for me. Keep everything on my local network. Explain how to disconnect or undo configuration changes. If a feature is unsupported, say so and offer the closest working alternative. IMPORTANT: Don't stop after writing a plan or generating code. If you're running locally on my computer, proceed with discovery, configuration, pairing, and real-world testing, requesting my input only when necessary. If you're running in a cloud environment without access to my home network, explain that limitation and prepare a way to run the controller locally. Start by identifying my TV from the attached photo and checking which control method it supports."

the whole collection: x.ai/bot/marketplace/from-gr…

6 app features. 6 REA + Opus 5.5 prompts. the full rebuild pack is below — pick a feature, investigate how it works, and build your own version. setup, evidence, specs and verification included. save this for your next project ↓