Skip to main content
A Pattern is a reusable structure: the shape of a section, page, or component as you want it built. Where a Skill is the procedure, a Pattern is the thing the procedure produces, captured so it comes out the same way every time.

​
What a Pattern captures

  • The structure: the parts of the section or page and how they are arranged.
  • The defaults: spacing, layout, and the elements that should always be present.
  • The variations: the parts that change per use, and the parts that never do.

​
Why Patterns matter

Patterns are how you keep a consistent build across many pages and many sites. A “hero section” Pattern means every hero you create starts from the same proven structure, so the work is faster and the result is predictable. This is the difference between an agent that improvises and one that builds the way your team builds.

​
Patterns and the rest of memory

1

Playbook sets the rules

Brand and convention rules a Pattern must respect.
2

Pattern sets the structure

The reusable shape, built to those rules.
3

Skill drives the work

The procedure that places and fills the Pattern on a real page.
When WPOS builds something in the Command Center that you would want again, save it as a Pattern on the spot. That single action is what makes the next build faster.