A Playbook is the set of standing rules WPOS follows on a site. It is the place
to put the things that should always be true, so you never have to repeat them in
the Command Center.
What belongs in a Playbook
- Brand rules: colors, fonts, tone of voice, logo usage.
- Conventions: how sections are named, how pages are structured, what an SEO
field should contain.
- Boundaries: what WPOS should never change without asking.
- Client preferences: the specific way this client likes things done.
Why it matters
Every rule in the Playbook is a thing you do not have to say again. It is also a
thing a Guest agent and every Task will
follow automatically, which keeps work consistent across your team and across
sessions.
Playbook is rules. Skills are procedures, and
Patterns are structures. Use Playbook for the things that
should hold regardless of the specific task. A good Playbook entry
A strong entry is specific and testable. Compare:
| Weak | Strong |
|---|
| ”Keep it on brand" | "Headings use Inter Tight, body uses the theme default. Primary buttons use #1D2327." |
| "Good SEO" | "Every page has a meta title under 60 characters and a meta description between 140 and 160 characters.” |
Build the Playbook up as you go. The first time you correct WPOS on something
that should always be true, that correction is a Playbook entry.
