Content Strategy
Design Brief Enforcer: The Antidote to "Make It Modern"
Keep creative work on-brief from kickoff to delivery.
What it does
"Make it modern" produces slop. This skill forces the opposite: a brief that cannot drift, because every requirement is stated in named aesthetic vocabulary, decomposed references, and hard spec values — with a critique pass held separate from the build.
The framework stops the two failure modes that kill creative work: briefs vague enough to mean anything, and critiques that happen during the build, when changing direction is expensive. It replaces both with a spec you can check against and a critique moment that happens before the build commits.
- Named aesthetic vocabulary. Bans words like "modern" and "clean" — every term must name something verifiable.
- Decomposed references. Breaks reference images into measurable attributes instead of "make it like this".
- Hard spec values. Type scale, spacing, color, motion — stated as numbers, not adjectives.
- Separate critique pass. Reviews happen against the spec before the build, not during it.
- Revision gate. Every change must cite the spec it violates — killing scope-less revisions.
When to use it
- Writing a brief from scratch: Run this to produce a brief that cannot be misinterpreted — the first review lands.
- A project is drifting into revision cycles: The spec and revision gate cut the loop: changes must argue against the spec, not taste.
- Onboarding a new designer or agency: A decomposed, spec’d brief communicates the direction without tribal knowledge.
- After design-what-if commits a direction: The direction becomes the spec — this is the natural handoff.
The methodology
- 1
Write the named vocabulary
List every aesthetic term the brief might use ("modern", "clean", "premium") and replace each with a named, checkable term. "Modern" becomes "minimal layout, one accent color, generous whitespace." If a term cannot be named, it does not belong in the brief.
30–60 minutes - 2
Decompose the references
For each reference image, list its measurable attributes: type treatment, color palette, spacing rhythm, imagery style, motion. The reference now describes properties, not vibes. "Like Apple" becomes a set of named properties.
1 hour - 3
Set the hard spec values
Translate the attributes into numbers: type scale steps, spacing units, palette hexes, breakpoints, motion durations. The design is now checkable — each element either matches a spec value or does not.
1 hour - 4
Hold the critique pass
Review the work against the spec in a dedicated pass, before the build goes further. Every finding cites the spec value it violates. Taste is allowed only where the spec is silent — and the goal is to make it silent as rarely as possible.
45 minutes - 5
Enforce the revision gate
From the critique onward, changes must cite the spec. A change that cannot name what it fixes does not happen. This is what actually stops the revision spiral.
Ongoing
Common mistakes
- Letting "make it modern" into the brief — A brief that can mean anything will produce a design that means nothing — and a revision cycle that pays for it. The vocabulary step exists to ban this.
- Vague references ("like Apple") — Undecomposed references import the vibe without the properties, so the design misses both. Decomposition is not optional.
- Critiquing during the build — Direction changes mid-build are the most expensive feedback there is. The separate critique pass moves all review to the cheap moment.
- Scope-less revisions — Every revision without a cited spec doubles the cycle. The revision gate is what keeps the project moving.
Output
An enforceable brief: named vocabulary, decomposed references, hard spec values, and a critique protocol — plus the revision gate that keeps it enforced.
Format
Brief document with a spec table; the critique pass is a scheduled review, not a document.
Feeds into
The spec becomes the reference for the build and for every later review; pairs with design-what-if for the strategic direction.
Next steps
Run design-what-if first when the direction is not yet decided — this skill enforces whatever it commits to. Pair with market-research if the vocabulary needs grounding in buyer language.
Time & resources
First run
2–3 hours to write the full brief and spec
Iterations
1 hour per project once the vocabulary is established
Low — the process is a document format; the discipline is in refusing vague terms.
Take it with you
Want to run this in Claude? This page is the strategic overview. The GitHub SKILL.md is the full technical specification — import it and run the method.
Ask Claude: "Use the Design Brief Enforcer methodology to audit this brief." Paste the brief and references; it will flag vague terms and return the spec values.