From Brand Book to Installed Skill

The afternoon move that turns your brand book into a constraint engine.

Most brand books die as PDFs on a shared drive.

The team can read them. The tools cannot. Every new asset starts from a brief, a rough memory of the rules, and an apology when something ships off-brand.

That is a format problem, not a brand problem.

This guide is the afternoon move that fixes it. Take your written brand identity, run it through Claude Design to generate a working system, wrap the result as a Cowork plugin, install it once. From that point forward every Claude session designs on-brand without re-briefing.

What is inside:

The setup-block discipline. Stop pre-formatting your input for the wrong UI. The actual fields Claude Design asks for, and what to put in each one.
The doctrine test for images. Why most of your existing photography is wrong for the new system, and the three questions that force an honest shortlist.
The canonical / downstream split. Where the brand doctrine lives versus where the generated system goes. Confuse the two and the system rots.
The Cowork plugin wrap. How to bundle one or more design skills into a single .plugin file, including the nested-zip gotcha that breaks installs.
The maintenance rule. The codified behaviour that keeps doctrine and plugin in lockstep when the brand evolves.
Chat versus Cowork. Two operating patterns, both real, with the trade-off named so you pick the right one.

Built from an actual production run on my own personal brand on June 26, 2026. Seven stages. A focused afternoon. The compounding starts the next session.

Written by someone who runs AI systems in production. Sable, an AI Chief of Staff that operates without supervision. MiniBrain, a Claude-native second brain. CMO Doctrine, a published Claude skill that refuses bad work.

The brand book stops being a document the team reads. It becomes the constraint engine the work runs on.

From Brand Book to Installed Skill

The afternoon move that turns your brand book into a constraint engine.

Most brand books die as PDFs on a shared drive.

The team can read them. The tools cannot. Every new asset starts from a brief, a rough memory of the rules, and an apology when something ships off-brand.

That is a format problem, not a brand problem.

What is inside:

The setup-block discipline. Stop pre-formatting your input for the wrong UI. The actual fields Claude Design asks for, and what to put in each one.
The doctrine test for images. Why most of your existing photography is wrong for the new system, and the three questions that force an honest shortlist.
The canonical / downstream split. Where the brand doctrine lives versus where the generated system goes. Confuse the two and the system rots.
The Cowork plugin wrap. How to bundle one or more design skills into a single .plugin file, including the nested-zip gotcha that breaks installs.
The maintenance rule. The codified behaviour that keeps doctrine and plugin in lockstep when the brand evolves.
Chat versus Cowork. Two operating patterns, both real, with the trade-off named so you pick the right one.

Built from an actual production run on my own personal brand on June 26, 2026. Seven stages. A focused afternoon. The compounding starts the next session.

The brand book stops being a document the team reads. It becomes the constraint engine the work runs on.