Theme plugin
Case study
active · Selected build
Hue for Yaak
A native Yaak theme plugin that turns one Huế-inspired token contract into three focused moods for everyday API work.

- Status
- active
- Last activity
- 4 Sep 2026
- Verified host
- Yaak 2026.6.0
- Registry downloads
- 16
- Snapshot
- 7 Sep 2026
- License
- MIT
- typescript
Verified distribution
Published packages
3 themes · 16 downloads
| Package | Version | Downloads |
|---|---|---|
| @crafts69guy/hue-theme | 0.3.0 | 16 |
Installed on Yaak 2026.6.0 formacOS; registry counts verified 7 Sep 2026.
Inside the workflow
03 views


Why I built it
API work moves constantly between navigation, request inputs, authentication, response bodies, history, and status feedback. A useful theme has to preserve those boundaries without turning every panel into a different visual system.
The system
The Yaak package contains three generated themes: Mưa, Hương, and Cung. Its adapter maps the shared Hue contract into Yaak’s native surface, text, border, accent, selection, and status slots, then the Yaak CLI bundles the result for registry distribution.
Yaak does not expose syntax-highlighting slots through its theme API. The adapter records that limitation explicitly instead of inventing unsupported mappings, so the contract remains honest about what the host controls.
Decisions that matter
- One plugin carries all three moods because Yaak supports multiple themes per package.
- Every exposed color comes from a semantic token rather than a copied hex palette.
- Unsupported syntax roles are documented, not approximated.
- The generated plugin is verified both as a registry artifact and inside the desktop app.
What it demonstrates
Portability does not mean forcing every application into the same shape. Hue for Yaak preserves the shared visual language while respecting the smaller, host-defined theme API that an API client actually provides.