jsw324 is reskinning Mike into unburdn law

A fork of Mike gets renamed everywhere a client would see it, turning the open-source tool into a branded product called unburdn law.

brandingpersonas

The rename runs deeper than a logo. jsw324 swapped "Mike" out of the parts of the product that users actually touch - the welcome copy, the signup terms and privacy links (now pointing at unburdn.ai), and, notably, the AI assistant's own self-description. The model that used to introduce itself as Mike now answers as unburdn law.

That last piece is worth flagging. The product name is baked into the assistant's underlying instructions, and changing it can quietly shift how the assistant talks - its tone, its sense of who it is - even when nothing else moves. Anyone rebranding for their own shop should re-test the assistant's behaviour after the swap rather than assume it's cosmetic. jsw324 kept the change deliberately shallow: under the hood, the plumbing still says Mike. This is a storefront, not a gut renovation.

So what Anyone weighing whether to white-label Mike for their own firm or product should study this fork first.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from jsw324/law-llm, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`492dd408`	Bump Next.js to ^16.0.11 and rebrand to unburdn law	Jason Walkow	2026-05-03	↗ GitHub
commit body Fixes critical CVEs in next@16.0.3 (CVE-2025-66478, CVE-2025-55184, CVE-2025-67779, CVE-2025-55183) flagged by Railway's security scan. Also resolves the @opennextjs/cloudflare peer-dep conflict that blocked fresh installs. Replaces user-visible "Mike" branding with lowercase "unburdn law" across page titles, sidebar/logo, AI persona system prompts, DOCX tracked-changes author, signup terms/privacy URLs, and column-prompt placeholders. Internal type names, MIME types, package names, and the MikeIcon component are unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
`99375788`	Remove frontend/bun.lock so Railpack uses npm + package-lock.json	Jason Walkow	2026-05-03	↗ GitHub
commit body Railpack prefers bun when bun.lock is present, but the file was stale relative to package.json after the Next.js bump and failed --frozen-lockfile. The repo standardizes on npm per the README, so the bun lockfile is unused - removing it lets Railpack fall back to npm and the up-to-date package-lock.json. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-104.md from inside the repo you want the changes in.

⬇ Download capture-thread-104.md