A desktop monitor displays a sleek productivity dashboard with a clock, task lists, system stats, and an AI assistant.
Custom Windows desktop widgets do not have to begin with hours of hunting for matching skins—or learning an entire configuration language. How-To Geek’s Dibakar Ghosh reports using Claude to create a personalized set of Rainmeter widgets, refining their appearance and behavior through a few conversational exchanges.

The interesting part is not simply that AI produced a clock. Ghosh describes a coordinated desktop dashboard with a daily schedule, deadline reminders, persistent checklists, activity graphs, and a Claude usage estimate. His “few minutes” claim is a personal experience, however, not a tested completion time that every Windows user should expect.

Rainmeter runs the widgets; Claude helps write them. That distinction matters more than the model name.

A desktop monitor displays a sleek productivity dashboard with a clock, task lists, system stats, and an AI assistant. Windows 11 widgets and desktop skins serve different needs​

Windows 11 already has widgets. Microsoft documents its Widgets Board as a flyout opened through the taskbar icon, Windows+W, or a swipe from the screen’s left edge. Rainmeter instead describes its skins as movable, potentially interactive windows displayed over the Windows desktop. These are different presentation models, not interchangeable implementations of the same feature.

Ghosh prefers information that is visible whenever he returns to the desktop. That is a reasonable preference, but it does not make Microsoft’s board inherently useless: an on-demand panel and a persistent desktop arrangement suit different working habits.

There is another qualification to “always visible.” Rainmeter exposes a skin’s position relative to other windows, so desktop placement should not be confused with a guarantee that information will remain above every application.

The practical question is straightforward: do you want a dashboard to summon, or information waiting on your desktop?

What the Claude-assisted dashboard contains​

Ghosh reports actively using six custom widgets:

  • Today: A color-coded timeline spanning 11 a.m. to 2 a.m., with a current-time indicator and a card showing the current and next activity. He describes its input as a locally saved CalDAV file; the account does not establish a live calendar-sync setup.
  • Day Left: A workday countdown whose text moves from white to amber to red, intended to discourage work from spilling into the evening.
  • Pitch Day: An editable ideas checklist with a Thursday deadline. Entries are saved locally, completed pitches move to an archive file, and unfinished items carry into the following week.
  • Activity: A graph drawing on a locally running ActivityWatch server to summarize active PC time, busy hours, and application usage.
  • Claude: A daily Claude Code usage tracker that estimates when a five-hour usage window resets. It should be understood as the author’s estimate, not an independently validated account-limit indicator.
  • Clock: A large animated time display, included mainly for its appearance.

These examples make the experiment more useful than another desktop makeover. Several widgets concern the author’s actual workflow rather than generic weather or system statistics.

They also reveal the project’s limits. A countdown and an editable archive are not equally demanding. The latter needs correct file-writing behavior, while the activity graph depends on another service. Ghosh does not provide the completed files, exact prompts, or a reproducible setup for all six.

Why Rainmeter is a workable target for AI assistance​

Rainmeter’s official documentation explains that a skin is stored as a named .ini text file inside a skin folder. Its configuration separates information-gathering “measures” from display elements called “meters”; every skin needs at least one meter. Supporting resources can accompany more complex projects.

That structure provides a credible explanation for the workflow: a coding assistant can draft and revise readable configuration files rather than having to produce a compiled Windows application.

Anthropic’s documentation confirms that Claude Code can read code, edit files, and run commands. That supports Ghosh’s preference for a local coding workflow that places files directly into a project. His alternative is ordinary Claude chat, with the user saving the generated files manually. File-editing capability does not itself verify that a finished skin works correctly.

Ghosh favors Opus 5.5 and reports more problems with Sonnet 5.5. Those impressions are not a controlled comparison, and the experiment does not establish that a particular model is necessary.

A sensible way to try the approach​

For Windows 11 users who already have Rainmeter installed and access to Claude, the safest starting point is one small widget—not the entire six-part dashboard.

The following is a suggested development workflow, rather than a reproduction of Ghosh’s unpublished files:

  1. Specify one job. Describe the information, dimensions, colors, and expected behavior. Start with a clock or countdown before adding calendar access or editable records.
  2. Request an explanation with the files. Ask what each file does, which dependencies it needs, and whether it reads data, writes files, or executes commands.
  3. Save it in the correct skin directory. Rainmeter documents the normal default as C:\Users\YourName\Documents\Rainmeter\Skins, with each skin’s .ini inside its own named folder. Portable installations and customized paths differ.
  4. Load and inspect it. Open Rainmeter’s Manage window from its notification-area icon, select the skin’s .ini, and use Load. After editing an existing skin, use Refresh to apply the changes.
  5. Test behavior, not just appearance. For a checklist, confirm that entries survive a refresh and that archiving preserves the intended records. For a countdown, check the deadline boundary before relying on it.

If a newly added file does not appear, Rainmeter’s documentation directs users to Refresh all after adding, renaming, or removing skin files. If it loads incorrectly, Open log in Manage exposes Rainmeter’s diagnostic log.

Success means more than an attractive rectangle: the displayed information should be correct, changes should persist where intended, and failures should be understandable.

Keep the customization, retain the caution​

For downloaded skins, Rainmeter recommends trusted publishers and its .rmskin package format where possible. It explicitly warns against downloading an .exe presented as a skin installer. Those precautions do not certify AI-generated files, which still deserve inspection before use.

A separate practical safeguard is worth remembering: Rainmeter layouts save arrangement and settings, not the skin files themselves. Back up the generated project separately before asking an assistant to make substantial revisions.

Ghosh’s experiment offers a useful idea without proving effortless perfection. Describe the dashboard you actually need, let an assistant handle some configuration work, and keep testing in your own hands. The desktop can become more personal—but the attractive clock should not be the only thing keeping accurate time.

 

References

  1. I built my own Windows desktop widgets using Claude, and it only takes a few minutes - How-To Geek How-To Geek 2026-10-31T00:00:15+00:00
  2. Introducing Claude Opus 5.5 \ Anthropic anthropic.com
  3. Overview - Claude Code Docs code.claude.com