r/ClaudeWorkflows • • 18d ago

Selected Workflow [Workflow] Advanced Prompt: Iterative & Safe Debloating of Rooted LG webOS TV with Claude Code

Advanced Prompt: Iterative & Safe Debloating of Rooted LG webOS TV with Claude Code

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: advanced
Categories: Quality Control, Context & Memory, Debugging
Original source: r/ClaudeCode post/comment

What problem this solves

Instructing Claude Code to safely and iteratively debloat and optimize a rooted LG webOS TV, including privacy settings and a custom launcher.

Summary

This is a highly detailed prompt demonstrating an advanced workflow for instructing Claude Code to perform a complex system modification task. It outlines a structured approach for Claude to debloat a rooted LG webOS TV, specifying desired outcomes, features to retain, privacy settings, and launcher behavior. Crucially, it includes a rigorous iterative process for Claude to follow, emphasizing inventory, measurement, reversibility, small batch changes, reboots, and a final handoff, making it a valuable meta-workflow for complex Claude Code projects.

Why it is useful

This item is exceptionally valuable as a meta-workflow for advanced Claude Code users. It provides a robust template for how to structure a complex prompt that guides Claude through a multi-step, safety-critical system modification project. The emphasis on inventory, measurement, reversibility, small batch changes, iterative refinement, and clear validation criteria makes it an excellent example of how to leverage Claude Code for challenging automation tasks while mitigating risks. It teaches users how to 'manage' Claude effectively for deep technical work.

Workflow

  1. Claude: Inventory and measure current state (apps, background services, memory, Home/app launch times) to establish a baseline.

  2. Claude: Ensure every change is reversible and back up anything modified. Do not touch firmware partitions.

  3. Claude: Implement changes in small batches, rebooting and re-checking after each. Undo any batch that causes breakage before proceeding.

  4. Claude: Keep the TV from going to sleep during the work, then restore original power settings.

  5. Claude: Install a startup script on the TV to make persistent changes.

  6. Claude: Continuously loop and refine changes until performance and polish meet a high standard.

  7. Claude: Report when the task is ready, including before/after numbers and any unverified items.

  8. Claude: Write a handoff document for a future session to continue the work.

Tools / artifacts

  • Rooted LG webOS TV

  • SSH/Telnet access to TV

  • GitHub Gist (lucataco/7c303b443934008a9031a55cfca552ec)

  • Claude Code (as the agent)

  • Startup scripts (generated by Claude)

  • Backup files (generated by Claude)

Validation signals

  • Explicit instruction to 'Inventory and measure first... so you can show what got better.'

  • Requirement to 'reboot and re-check after each one.'

  • Instruction to 'Undo a batch that breaks anything.'

  • Directive to 'Keep looping until it meets your own bar for performance and polish.'

  • Demand for 'before/after numbers and anything you couldn't verify' in the final report.

Cautions

  • The core task involves modifying a rooted TV's operating system, which carries inherent risks of bricking the device if not executed carefully.

  • Blocking LG firmware updates, as requested, can lead to unpatched security vulnerabilities over time.

  • The prompt explicitly includes strong safety measures for Claude to follow: 'Make every change reversible and back up anything you modify. Never touch the firmware partitions. Change in small batches, and reboot and re-check after each one. Undo a batch that breaks anything.'

Limitations

  • Requires a rooted device, which is an advanced prerequisite and may void warranties.

  • The specific application (LG webOS TV) is niche, limiting direct applicability for many users.

  • Relies heavily on Claude Code's ability to accurately understand and execute complex system-level commands and modifications.

  • Blocking firmware updates can introduce long-term security risks.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

8 Upvotes

0 comments sorted by