Interactive State Flow

Use when an interactive flow is laggy, stale, or race-prone because user intent, source state, derived presentation, async IO, scheduling, or background work are mixed. Keep source state prompt, protect the urgent interaction path, and admit async or presentation results only through a freshness-owning boundary.

perhapsspy Updated

File contents

perhapsspy/interactive-state-flow commit f9d424fcad

Frequently asked questions

npx get-skill add perhapsspy/interactive-state-flow