What changed & why

new wayfinder and the four skills it calls

Plans work too big for one session as a map issue on the tracker, decision tickets as children, one resolved per session. The plan lives on the board, so it survives a /clear. Its four components needed narrower descriptions first: as shipped they competed with superpowers:brainstorming and impeccable. Why it matters: a component lifted out of its set becomes a second front door unless you name its caller.

new diagnosing-bugs, beside the debugger I already had

It wins on one idea: build a tight, deterministic loop that goes red on the bug before forming any theory. Both skills stay, routed by hand. Why it matters: neither self-routes reliably, because the other never says "debug" in its description. Two skills for one job needs a written rule, not a hope.

new bin/check, because nothing checked anything

Dangling links, two skills claiming one trigger, doctrine drifting between copies, and how much instruction loads before any work starts. It was wrong four times first, including a bug that made it pass over a 24-day gap. Why it matters: a check that can only pass is worse than none, because it reports health it never measured.

changed This page was publishing things it should not

The downloadable spec and the copy embedded in this page both carried a company name, colleagues by first name and a client. I fixed the file, called it done, and the page served the old copy for two more days. Why it matters: one document, four copies. Checking one is how the other three rot.

tidied Rules that said "never" now say what to do

Eight of eleven prohibitions had their positive form in the next sentence already. Three stayed, all where the mistake is irreversible. Why it matters: telling a model not to do something puts the thing in front of it. The count now prints on every run, so the sweep cannot quietly undo itself.

removed ui-ux-pro-max, despite its popularity

One of the most-shared design skills around, so the reasoning deserves daylight. Under the hood it isn't a design skill but a lookup database: 50 styles, 97 palettes, 57 font pairings and 99 generic UX rules behind a search script. Every question it answers has a sharper specialist here: frontend-design, design-md, impeccable, dataviz. Why it matters: popularity is not fit. A generic layer underneath specialist skills adds context weight and skill collisions, not quality.

new The claude-seo pack, routed next to marketing-skills

AgriciDaniel's claude-seo plugin brings execution-side SEO under one /seo command: technical audits, schema validation, sitemaps, hreflang, and live Search Console data. On paper it overlaps with the marketing-skills pack; in practice they split cleanly, so Boss got two routing rows. claude-seo measures and validates, marketing-skills does strategy and copy. Why it matters: the answer to overlapping packs is routing, not forking them into a homemade bundle you then maintain alone.

new Skill shadowing as a router technique

Both packs above ship a skill named seo-audit, so the same slash command showed up twice. You don't have to pick one, or edit the packs: a personal skill of the same name in ~/.claude/skills/ takes precedence. /seo-audit now opens a small menu and routes to the right pack; the originals stay reachable as /claude-seo:seo-audit. Why it matters: two skills sharing a name stop being a conflict and become a front door you design yourself.

tidied Every plugin checked against its upstream

All installed plugins and vendored skills were compared against their source repos. Most were current; marketing-skills was months of releases behind and jumped 1.9.0 → 2.8.12, and a marketplace that never delivered a single installed plugin was removed. Why it matters: a skill stack you never update quietly rots into exactly the stale-knowledge problem it was installed to solve.

new A "why not just let Claude do its thing?" section

The question I get most, answered up front: when the structure pays off, when it doesn't, and who it's for. Why it matters: you can decide in one minute whether this page is worth your next thirty.

changed Folder names that explain themselves

Team feedback: the old names didn't self-explain. build/ is now code/, development/ is _project/, deal sources live in sources/ (was the one Dutch name, bron/), consultancy hand-overs in reports/, and every project now carries a page/ in its permanent spine. The folder explorer reflects all of it. Why it matters: a folder name you don't have to explain is one less thing the next person (or the next AI) gets wrong.

new /deep-research joins the shipped workflows

Fan-out searches, adversarial verification, a cited report. Why it matters: third workflow that earned its card through real use.

new Added Cloudflare's official skill pack

Nine drop-in skills for building on Cloudflare (the platform, the Wrangler CLI, Workers best practices, Durable Objects, the Agents and Sandbox SDKs, email, Turnstile, and a web-performance auditor) now appear in the skills list. They pull from the live Cloudflare docs rather than training data. Why it matters: they were already installed and in use deploying these pages; now the page reflects it.

new An interactive folder explorer

The Folder-structure section now lets you toggle capabilities on and off and watch the folders, files, and routing change live. Why it matters: you can see how a project grows before you build it.

changed The StyleProbe comparison is now two short lists

The part of the guide that compares Google's design file with StyleProbe's used to be a wide table that was awkward to read on a phone. It's now two short lists side by side, with a one-line "when to use it." Why it matters: the same comparison, easier to scan on any screen.

refreshed The page now matches the live setup

The lists of skills, tools, helpers, and workflows were checked one by one against what's actually installed, and brought back in line. A couple of things that had been retired or renamed were corrected, and one workflow that wasn't really there was removed. Why it matters: the page should read as a true snapshot of the current system, not a stale one.

new Added an image and design pack to the skills

A borrowed set of skills for visuals (brand boards, design-reference images, building from a screenshot, and a component library) now appears in the skills list. Why it matters: it was already in use; now the page reflects it.

new Added a "handover" helper

A new tool that ends a working session cleanly: it finishes whatever's in progress, then writes a short note about where things stand and what's next. Why it matters: long sessions get sloppy past the halfway point. Wrapping up on purpose, and leaving a note for next time, means nothing gets dropped between sittings.

tidied One consistent project name

The project folder used to be called vibing-workflow in a few places and BossMode in others. It's now BossMode everywhere, matching the site you're on. Why it matters: two names for one thing is the kind of small confusion that adds up. Now it reads the same throughout.

refreshed Up-to-date downloads

The two files you can download from the guide, boss.md and the install prompt, had fallen behind the versions actually in use. They now match what's running today. Why it matters: if you copy the setup, you get the current version, not a stale one.

new This changelog

The page you're reading. From now on, changes to the guide get written down here, for anyone, in everyday words. Why it matters: a living document should show its history, not just its latest state.

changed Split the public page from the working notes

The guide and the private working notes behind it used to live together, which meant the notes could be reached by anyone who guessed the address. They were moved apart: only the finished page is public now, the notes stay private. Why it matters: the page is meant to be shared; the rough working notes aren't.

new The guide became a public web page

What started as a personal working document went online as the page you're reading, free to read and free to copy. Why it matters: the whole point is that other people can lift the setup for themselves.