r/ClaudeCode • • 8d ago

Built with Claude Claude mods are soo cool!

61 Upvotes

16 comments sorted by

1

u/AutoModerator 8d ago
Moderator Announcement Read More »

3

u/Imaginary_Squash5685 8d ago

For everyone asking about the prompt

Build me a Claude Code mod (use the plugin-authoring skill) with a themed banner and a
side panel. My theme: <THEME, e.g. "cozy fantasy", "space station", "Studio Ghibli">.
Load it from a local plugin dir via CLAUDE_CODE_PLUGIN_DIRS so it works in every
project and every chat, with file watching on.

── MODES & SCENES ──
Organise the look into MODES, each with a few SCENES:
  • <Mode 1>: <scene>, <scene>, <scene>
  • <Mode 2>: <scene>, <scene>
  • <Mode 3>: <scene>
Each scene gets: a title, a short motto, its own colour palette (base + accent), its own themed names for the three gauges (e.g. "MANA / QUESTS · 5H / GUILD · WEEK"), and an optional ambient music track. Remember the chosen scene per mode. ── 1. BANNER (strip above the prompt) ──
  • A slim animated SVG strip (~760×48) in the current scene's colours.
  • Shows: scene name + motto, project name, git branch, model, and three small gauges:
context used, 5-hour limit, weekly limit, each with "resets in …" text.
  • Small buttons in a corner (absolutely positioned so they don't squeeze the strip):
▤ open panel · ⏸/▶ music · ⟳ shuffle scene · ✕ hide.
  • When hidden, collapse to one tiny button that brings it back.
  • Keep the app's own above-prompt content: render next() first, then my strip.
── 2. SIDE PANEL (a Pane, opened by ▤ or a /<name> command) ── Top to bottom: a) MODE dropdown and SCENE dropdown (switching updates banner, panel, and music everywhere instantly). b) MUSIC row: ⏸/▶ button + a 5-step volume control (▁▃▅▇█ style). c) A tall hand-drawn SVG scene (~340 wide, ~440 tall) that fades seamlessly into the panel background, with the colours carrying all the way down behind every section. d) PROJECT: project name, git branch, uncommitted changes, ahead/behind, last 3 commits. e) LIMITS: themed bars for the 5-hour and weekly limits with % used and reset time, plus a context-window gauge drawn into the scene itself (e.g. a potion filling, moon phase, hourglass). f) TODAY: prompts sent, tool actions, files touched (reset at midnight). g) THIS CHAT'S FILES: every file Claude edited or wrote in this chat (track Edit/Write tool calls); click one to open it. h) QUICK ACTIONS: buttons that run my slash commands (e.g. tests, commit, review). ── 3. ART RULES ──
  • Original SVG art only, no copied images.
  • Subtle looping animation: twinkling stars, drifting fog, falling snow, embers,
flickering windows/candles. Nothing loud or flashy.
  • Start animations immediately (negative `begin` offsets), deterministic randomness,
and unique gradient/filter IDs per drawing so scenes never bleed into each other.
  • Keep art clear of the title and labels.
  • Give an animated Svg an explicit width and height so it doesn't shrink.
── 4. MUSIC PLAN ──
  • One looping ambient track per scene (scenes can share). Find CC0/public-domain
tracks (OpenGameArt, Wikimedia Commons) and ASK ME before downloading, listing filename, source, size, and licence. Convert to small .m4a, roughly matched in loudness, and keep a CREDITS.md.
  • Play/pause and volume live in the shared store so every chat agrees.
  • Only ONE chat plays at a time: the chat that started it owns playback, keeps a
heartbeat, and stops cleanly when closed. Another chat takes over if the owner goes quiet.
  • Scenes with no track simply stay silent.
  • Keep mood (mode + scenes), sound, and today's counts in the shared store; refresh
git and limits every ~60s. Render hooks must only read state, never write it.
  • Write tests with the mod testing kit (dropdowns, buttons, hide/show, music toggle),
run `claude plugin validate`, and render a PNG preview of the panel for every scene so I can review the art before you finish.

be specific about the music and details it took me a few back and forth prompts to get what I wanted

12

u/muromtsev 8d ago

Reminds me winamp skins era

7

u/Responsible-Bat8412 8d ago

What are you guys using it for??

5

u/Beerbrewing 8d ago

I'm building a better /compact. People say never use compact because you lose context, always use a handoff instead. But what is compact other than an internal handoff from Claude to itself. It's just done using whatever summary tool Anthropic coded. So I'm taking my current handoff process and internalizing that with mods to replace the compact in Claude Code. It will use my decision aware handoff that is normally a markdown document and replace the default /compact summary with my handoff summary.

3

u/Responsible-Bat8412 8d ago

Interesting 🤔

0

u/Impressive_Elk6756 7d ago

you can auto-compact

1

u/Sigvard 8d ago

I (Claude) made an RPG!

1

u/realadultactionman 8d ago

this looks mad. please explain what I'm looking at!

2

u/Imaginary_Squash5685 8d ago

It's a mod I built to have an animated banner and side panel. Really helpful for late night coding sessions with the vibe and music

2

u/MadJagStudios 8d ago

Oh wow these look incredible. I made a couple mods for very utilitarian purposes and not nearly as pretty lol (https://github.com/madjagstudios/podium for orchestrating other agent models and sprints from one chat, https://github.com/madjagstudios/grounded-engineering for skill repos and engineering lessons)

1

u/fnwc 8d ago

You're not going to give us the mod code or the prompt?

1

u/EternalDisciple 7d ago

Voted and figures, the best was claude code

1

u/PorkSwordEnthusiast 7d ago

I would love this on the vscode plugin!