meltdown-map

Meltdown Map Skill

Meltdowns and shutdowns feel like they come from nowhere, but they almost never do —

there's a staircase of rising signs and stacking triggers that's invisible in the

moment and obvious in hindsight. A meltdown is not a tantrum and not a choice; it's a

nervous system past capacity. This skill turns the hindsight into foresight: map

your specific early signs, the triggers that stack toward the edge, and what

genuinely helps at each stage (which is different early vs late — reasoning helps at

stage 1 and harms at stage 3). The output is a map for you and a plain one-pager for

the people who want to help but don't know how.

What This Skill Produces

• A staged warning map: your personal signs at green (fine) → yellow (loading)

→ orange (near the edge) → red (over) — in your own words, because the signs are

individual

• The trigger stack: what pushes you up the stairs (sensory load, social

demand, hunger, change, cumulative masking) and how they compound

• A per-stage response plan: what helps at each stage and — critically — what

stops helping (talking, choices, touch can each flip from help to harm as you

climb)

• A shareable one-pager: for a partner, friend, colleague, or parent — what to

do and what to never do when you're climbing or over

Required Inputs

Ask for (if not already provided):

• What a meltdown and/or shutdown looks like for the user (they differ — meltdown

outward, shutdown inward; some people do both)

• The best recent example, walked backward: what happened right before, and before

that — hunting for the early signs they missed

• What has helped and what has made it worse (people often know the second better)
• Who they'd want the one-pager for, and what those people currently get wrong

Framework

1. Reconstruct the staircase from a real episode. Take one recent meltdown and

walk backward in time: the red moment, then orange (what were the last signs

before the edge?), then yellow (the loading no one noticed, often hours earlier),

then the green baseline. The early signs are the whole prize — they're where

intervention is still cheap.

1. Name the signs in the user's own language. Not a textbook list — their

tells: the specific irritability, the going-quiet, the pacing, the words getting

hard, the sound-sensitivity spiking. Self-recognizable beats clinically correct.

1. Map the trigger stack, including the slow ones. Acute triggers (a loud

room, a schedule change) sit on top of slow load (a week of masking, poor sleep,

an unresolved thing). Meltdowns usually need both — which is why they seem

random when you only look at the acute one.

1. Match response to stage — and name what stops working. Early: prevention and

exit (leave, reduce input, eat, stim freely). Mid: fewer words, fewer choices,

more space. Late/over: safety and non-interference — no reasoning, no questions,

no "just calm down," often no touch. The single most useful thing this skill

does is tell helpers when to stop trying to help and just keep the person safe.

1. Write the one-pager for real humans. Short, kind, specific: "when I go quiet

and short, I'm at orange — here's what helps, here's what makes it worse, don't

take it personally." The people around a meltdown usually want to help and make

it worse from love; the page fixes that.

Output Format

## Your staircase
🟢 Green (baseline): … 🟡 Yellow (loading, early): … 🟠 Orange (near edge): …
🔴 Red (over): …  [signs in the user's own words at each]

## Trigger stack
Slow load (the base): … + Acute triggers (the top): … = over the edge

## Response by stage
| Stage | What helps | What STOPS helping (do not) |

## One-pager for [person]
[Kind, short, specific — signs, do's, hard don'ts, "not personal"]

Quality Checks

• [ ] The staircase was built by walking a real episode backward, and the yellow/

early signs are populated (not just the obvious red)

• [ ] Signs are in the user's own words, self-recognizable in the moment
• [ ] The trigger stack includes slow cumulative load, not just the acute trigger
• [ ] Every stage names what stops helping, especially at orange/red
• [ ] The one-pager is genuinely handable to a non-expert and says "don't take it

personally"

Anti-Patterns

• [ ] Do not frame meltdowns/shutdowns as behavior to control, punish, or push

through — they're a capacity event, not a choice

• [ ] Do not prescribe reasoning, choices, or talk at the late stages — name that

those backfire past a point

• [ ] Do not generic-list the signs — a map that isn't the user's own is useless in

the moment

• [ ] Do not position this as crisis care — if meltdowns involve self-harm, danger,

or are escalating, say plainly this needs a doctor or crisis support (and give

the region-appropriate "find a crisis line" pointer), and stop there

• [ ] Do not assume a caregiver is safe — if the one-pager is for someone the user

is wary of, honor that and keep the plan self-directed

Related

[[masking-budget]] and [[sensory-audit]] remove the slow load that feeds meltdowns;

[[stoic-setback-debrief]] for the after; [[spoon-planner]] shares the capacity model.