Overcooked

What it is. A coop cooking game whose real subject is communication under pressure. A recipe ticket demands a chain of steps; a timer demands speed; and the kitchen layout splits the work so no one player can do it alone. The result is a controlled panic where players must shout, hand off, and plan — and every level cranks the layout to make coordination harder.

Player fantasy. Beautiful chaos with people you like. The joy is the table-slamming, cross-talking scramble — and the shared triumph when a frantic kitchen suddenly clicks into a rhythm. You didn’t beat the level; you and your crew did.

Design DNA

The core isn’t cooking — it’s forced interdependence. Overcooked engineers situations where solo play is impossible, so communication becomes a mechanic, not a nicety. Two levers do it: task decomposition (a dish is a pipeline of steps that naturally splits across hands) and spatial constraint (counters, gaps, moving floors that make one person physically unable to cover the kitchen). A shared clock (pattern-pacing-and-tension) turns coordination into pressure, and each level escalates the layout — a rising difficulty of coordination, not reflexes. See genre-coop-chaos for the parent pattern.

Load-bearing structures

Structure	Why it works
Forced interdependence	The layout makes solo impossible, so players must coordinate — communication becomes required play, not optional. → `system-coop-and-competition`.
Task decomposition	A dish is a pipeline (chop→cook→plate→serve) that splits cleanly across hands — instant, legible division of labour.
Spatial constraint as difficulty	Counters, gaps, moving/hazard floors gate movement; the room is the antagonist, not enemies. → `system-encounter-design`.
Shared clock	One timer everyone races creates the pressure that makes coordination fail interestingly. → `pattern-pacing-and-tension`.
Escalating layouts	Each level ratchets the coordination demand (splitting kitchens, conveyor floors) — a difficulty of teamwork. → `system-difficulty-and-dda`.
Legible shared state	Every player can read every ticket, station, and timer at a glance — coordination needs shared readability. → `pattern-readability`.
Instant, blameless retry	Fail a level, restart at once; the momentum and the laughter carry over. → `system-save-and-checkpoint`, FUN.md law 5.

What to steal

Design interdependence, don’t request it: make solo impossible via layout and task-split, so communication is a mechanic. Politeness is not a design.
Decompose the task into a pipeline that maps to hands — the clearest way to create “you do this, I’ll do that” without a manual. → system-coop-and-competition.
The room as antagonist: escalate difficulty through space and layout, not enemy stats — a party game’s threat is geometry (cf. FUN.md §5 stealth’s safe pockets, §8 coverage geometry).
A shared clock + blameless retry: pressure to make coordination fail funnily, and instant restart so failure is a laugh, not a punishment.

What’s just theme (drop it)

The cooking fiction — the loop is “a decomposable task, split by space, under a clock.” Firefighting, ship-repair, surgery, moving house all fit. → world-theme-vectors.
Specific recipes/stations — content on the pipeline system; swap freely.
Physical/janky controls — the humour helps but isn’t load-bearing; the interdependence is. Precise controls + hard layouts work too.
Local-only — the DNA is coordination pressure; it survives online with good shared-state readability. → system-coop-and-competition.

Composes into

genre-coop-chaos — the parent genre (couch-coop/party; communication under time pressure); Overcooked is its defining anchor.
system-coop-and-competition — forced interdependence and shared-state hooks.
system-encounter-design — composing kitchen layouts as escalating “fights” against space.
system-difficulty-and-dda — difficulty expressed as coordination load.
pattern-pacing-and-tension — the shared clock as the tension engine.

Twist seams

Overcooked but roguelite + you build the track ahead (mechanic-swap + structure) — Unrailed: the pipeline is laying rail before a moving train; the “kitchen” advances. (The worked twist in process-the-twist.)
Overcooked but asymmetric roles (perspective) — each player has different verbs/abilities, so interdependence comes from complementary powers, not just layout. Pairs with anchor-it-takes-two.
Overcooked but silent (constraint) — no voice/text allowed; coordination must route through in-game signals only. Forces diegetic communication.
Overcooked but competitive (tonal) — two crews share one sabotageable kitchen; coop pressure becomes PvP. Pairs with system-coop-and-competition.