@Voxyz_ai: Every time you let Opus 5.5 run a long task on its own, have it vibe-code a quick ๐—›๐—ง๐— ๐—Ÿ ๐—ฑ๐—ฎ๐˜€๐—ต๐—ฏ๐—ผ๐—ฎ๐—ฟ๐—ฑ like thisโ€ฆ

X AI KOLs Timeline News

Summary

This article proposes a technique for using Opus 5.5 to automate the creation and updating of an HTML dashboard during lengthy coding sessions, by configuring a specialized subagent that builds dashboards tailored to user preferences.

Every time you let Opus 5.5 run a long task on its own, have it vibe-code a quick ๐—›๐—ง๐— ๐—Ÿ ๐—ฑ๐—ฎ๐˜€๐—ต๐—ฏ๐—ผ๐—ฎ๐—ฟ๐—ฑ like this first. Then give it ๐—ฎ ๐˜€๐˜‚๐—ฏ๐—ฎ๐—ด๐—ฒ๐—ป๐˜ ๐˜๐—ต๐—ฎ๐˜ ๐—ผ๐—ป๐—น๐˜† ๐—ฏ๐˜‚๐—ถ๐—น๐—ฑ๐˜€ ๐—ฑ๐—ฎ๐˜€๐—ต๐—ฏ๐—ผ๐—ฎ๐—ฟ๐—ฑ๐˜€: โ†’ Name it dashboard-builder, set its effort to medium, and preload a design skill โ†’ The first time, it asks what style you like and saves it to memory. After that, every dashboard fits your taste and the task at hand โ†’ Call it before every long task. It builds the dashboard in the background in about two minutes, and the main session keeps coding on high without stopping โ†’ The dashboard shows four things: task progress, what's stuck, questions waiting on you, and what it'll do by default if you don't answer Send this prompt to Claude Code ๐Ÿ‘‡ "Set up a subagent that only builds progress dashboards: 1. Create dashboard-builder in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). It can only read and write the .dashboard/ folder and its own memory. 2. The first time, it asks me what style I like: dark or light, dense or airy, and one accent color. It saves my answer to memory and follows it every time. Pick the panels for the current task; don't use a template. 3. The dashboard is one HTML file showing tasks and their status, questions waiting for me with the default action, the latest deliverables, and anything stuck. Use the real clock for every time. It opens with a double-click and refreshes itself every 10 seconds. 4. Add a rule to ~/.claude/CLAUDE.md: for any task with more than 5 steps or that should take longer than 30 minutes, have dashboard-builder set up the dashboard before starting; update it after every step; when you need a decision from me, add it to the questions list and keep going with the default. Show me the contents of the files you'll create or change, then explain the whole flow in words a 10-year-old could follow. Don't write anything until I confirm."
Original Article
View Cached Full Text

Cached at: 09/27/26, 05:16 AM

Whenever you let Opus 5.5 run a long task on its own, have it vibe-code a quick HTML dashboard like this first.

Then give it a subagent that only builds dashboards: โ†’ Name it dashboard-builder, set its effort to medium, and preload a design skill โ†’ The first time, it asks what style you like and saves it to memory. After that, every dashboard fits your taste and the task at hand โ†’ Call it before every long task. It builds the dashboard in the background in about two minutes, and the main session keeps coding on high without stopping โ†’ The dashboard shows four things: task progress, whatโ€™s stuck, questions waiting on you, and what itโ€™ll do by default if you donโ€™t answer

Send this prompt to Claude Code ๐Ÿ‘‡

โ€œSet up a subagent that only builds progress dashboards:

  1. Create dashboard-builder in ~/.claude/agents: model: opus, effort: medium, memory: user. Preload the design skills I have installed (for example impeccable). It can only read and write the .dashboard/ folder and its own memory.
  2. The first time, it asks me what style I like: dark or light, dense or airy, and one accent color. It saves my answer to memory and follows it every time. Pick the panels for the current task; donโ€™t use a template.
  3. The dashboard is one HTML file showing tasks and their status, questions waiting for me with the default action, the latest deliverables, and anything stuck. Use the real clock for every time. It opens with a double-click and refreshes itself every 10 seconds.
  4. Add a rule to ~/.claude/CLAUDE.md: for any task with more than 5 steps or that should take longer than 30 minutes, have dashboard-builder set up the dashboard before starting; update it after every step; when you need a decision from me, add it to the questions list and keep going with the default.

Show me the contents of the files youโ€™ll create or change, then explain the whole flow in words a 10-year-old could follow. Donโ€™t write anything until I confirm.โ€œ

Similar Articles

Getting the most out of Opus 5.5 in Claude and Claude Code

Hacker News Top

Anthropic published a practical guide on getting the most out of Opus 5.5 in Claude and Claude Code, covering how to hand over whole tasks with clear finish lines, drop "think carefully" lines since the model always reasons before replying, and steer long autonomous coding runs.