voiden: Skill for Claude Code

Voiden release changelog workflow

Sibling repositories

This repo (voiden) is one of three under ~/Desktop/Voiden/ — know all three before starting release work, since a release routinely touches more than one:

• voiden (this repo) — the app monorepo. Owns apps/ui/src/data/changelog.json (full technical changelog) and apps/ui/src/core/whats-new/whats-new.json (in-app highlights).
• ../Voiden Website/website — the public marketing site. Mirrors the technical changelog at src/features/changelog/data.ts, rendered by src/components/ChangelogEntry.tsx. Same content as changelog.json, different schema (see part 3 below) — keep both in sync every release, don't let the website fall behind (it had silently missed three whole releases before this note existed).
• ../docs — the docs site (docs.voiden.md, Docusaurus). No changelog here, but a release that adds or changes a user-facing feature (a new block, a new CLI flag, a new panel) usually means a doc page needs updating too. This skill doesn't write those doc edits itself — but check whether one's needed, and say so, rather than closing out release work as if the changelog were the only thing that could be stale.

When asked to create a changelog entry for a new app version, three files across two repos need updating, not one. They serve different audiences and have different formats — do not skip any of them or copy the same content in verbatim where the format actually differs.

1. apps/ui/src/data/changelog.json — full technical changelog

The exhaustive, engineering-facing record. One object per release, prepended to the top of the array (newest first).

{
  "version": "vX.Y.Z",
  "date": "DD/MM/YYYY",
  "title": "Short Punchy Title",
  "description": "1-2 sentence summary of the release for the changelog page header.",
  "icon": "Wrench",
  "iconColor": "text-orange-400",
  "bgColor": "bg-gradient-to-br from-slate-900 to-orange-950",
  "changes": {
    "Added": ["..."],
    "Improved": ["..."],
    "Fixed": ["..."]
  }
}