hud 0.1.0: a live usage HUD above the prompt (replaces buddy)

.claude-plugin/marketplace.json

@@ -4,11 +4,14 @@
   "owner": { "name": "Samarth Rayar", "url": "https://github.com/Samarth2001" },
   "plugins": [
     {
-      "name": "buddy",
-      "source": "./plugins/buddy",
-      "description": "A pixel-art companion above the prompt that acts out what Claude is doing, with a sprout that wilts as context fills, a context sparkline, usage limits and cost",
+      "name": "hud",
+      "source": "./plugins/hud",
+      "description": "A live usage cockpit above the prompt: context, plan limits with pace forecasts, and cost by day, week and month, in a one-line glance that expands into tabs and a dashboard pane",
       "category": "mods",
-      "tags": ["mod", "companion", "pixel-art", "status"]
+      "tags": ["mod", "usage", "cost", "limits", "dashboard"]
     }
-  ]
+  ],
+  "renames": {
+    "buddy": "hud"
+  }
 }

.claude/skills/release/SKILL.md

@@ -10,5 +10,5 @@ Release plugin: $ARGUMENTS
 1. Read `plugins/<name>/CHANGELOG.md` and run `git log <name>--v<current-version>..HEAD -- plugins/<name>`. If that tag doesn't exist, use the full log for the folder. Then list what changed.
 2. Choose the bump if none was given: patch for fixes, minor for features, major for breaking changes such as renamed commands or settings. Confirm it with me.
 3. Set `version` in `plugins/<name>/.claude-plugin/plugin.json`. Add a `## [<version>] - <today>` section to the CHANGELOG under Added, Changed or Fixed, plus its compare link at the bottom.
-4. Run `claude plugin validate .`, `claude plugin validate plugins/<name>`, `claude plugin test plugins/<name>` if it has tests, and `node --experimental-strip-types scripts/catalog.mts --check`.
+4. Run `claude plugin validate --strict .`, `claude plugin validate --strict plugins/<name>`, `claude plugin test plugins/<name>` if it has tests, and `node --experimental-strip-types scripts/catalog.mts --check`.
 5. Commit as `<name>: release <version>`. Then stop and show me the commands to push and tag: `git push` and `claude plugin tag plugins/<name> --push`.

.github/workflows/validate.yml

@@ -21,13 +21,13 @@ jobs:
       - name: Install Claude Code
         run: npm install -g @anthropic-ai/claude-code
       - name: Validate marketplace
-        run: claude plugin validate .
+        run: claude plugin validate --strict .
       - name: Validate and test each plugin
         run: |
           set -e
           for dir in plugins/*/; do
             echo "::group::$dir"
-            claude plugin validate "$dir"
+            claude plugin validate --strict "$dir"
             if find "$dir" -name '*.test.ts' -o -name '*.test.tsx' | grep -q .; then
               claude plugin test "$dir"
             fi

.gitignore

@@ -2,3 +2,8 @@
 plugins/*/.claude-plugin/types/
 node_modules/
 .DS_Store
+
+# Personal, machine-local Claude Code files: never published
+CLAUDE.local.md
+.claude/settings.local.json
+.claude/**/*.local.*

CLAUDE.md

@@ -8,7 +8,7 @@ A Claude Code plugin marketplace (`samarth`). Each plugin lives in `plugins/<nam
 - Keep each plugin self-contained, in Claude Code's standard layout, with its own README.md and CHANGELOG.md. Dev-only tooling goes in `scripts/`, never inside a plugin.
 - Never rename a plugin's `name`. Leave `version` out of marketplace entries.
 - Any change to a plugin's shipped files needs a version bump and a CHANGELOG section. README, CHANGELOG, `assets/` and tests are exempt.
-- Before reporting work done, run `claude plugin validate .`, `claude plugin validate plugins/<name>`, `claude plugin test plugins/<name>` (if it has tests) and `node --experimental-strip-types scripts/catalog.mts --check`.
+- Before reporting work done, run `claude plugin validate --strict .`, `claude plugin validate --strict plugins/<name>`, `claude plugin test plugins/<name>` (if it has tests) and `node --experimental-strip-types scripts/catalog.mts --check`.
 - Before writing a mod, load the `plugin-authoring` skill.
 - Guides in `docs/` summarize the official docs at code.claude.com. Link to the source and don't state behavior you haven't checked.
 

CONTRIBUTING.md

@@ -33,8 +33,8 @@ If you edit the marketplace by hand, run `node --experimental-strip-types script
 ## Try it
 
 ```bash
-claude plugin validate .                     # the marketplace
-claude plugin validate plugins/<name>        # the plugin
+claude plugin validate --strict .            # the marketplace
+claude plugin validate --strict plugins/<name> # the plugin
 claude plugin test plugins/<name>            # its tests (mods)
 claude --plugin-dir plugins/<name>           # a session with it loaded; mods hot-reload on save
 ```
@@ -77,4 +77,4 @@ Never change a plugin's `name`, because it is the install id. Change `displayNam
 
 ## Commits
 
-Commit as `Samarth Rayar <samarthsr2001@gmail.com>`. Make one change per commit. Start the subject with the plugin name for plugin changes (`buddy: ...`) and describe the area for repo-wide changes (`Release workflow: ...`).
+Commit as `Samarth Rayar <samarthsr2001@gmail.com>`. Make one change per commit. Start the subject with the plugin name for plugin changes (`<name>: ...`) and describe the area for repo-wide changes (`Release workflow: ...`).

README.md

@@ -34,7 +34,7 @@ Installed plugins also load in the Claude desktop app (Code tab, local sessions)
 <!-- catalog:start -->
 | Plugin | Install id | Type | What it does |
 | --- | --- | --- | --- |
-| [Buddy](plugins/buddy) | `buddy` | mods | A pixel-art companion above the prompt that acts out what Claude is doing, with a sprout that wilts as context fills, a context sparkline, usage limits and cost |
+| [HUD](plugins/hud) | `hud` | mods | A live usage cockpit above the prompt: context, plan limits with pace forecasts, and cost by day, week and month, in a one-line glance that expands into tabs and a dashboard pane |
 <!-- catalog:end -->
 
 Each plugin has its own README covering what it adds, how to use and configure it, and its changelog. This table is generated from [`marketplace.json`](.claude-plugin/marketplace.json) by `scripts/catalog.mts`.