Lifecycle And Side Effects Correctness

Overview

Use this skill to prevent duplicate, stale, missing, or misattributed side effects across lifecycle transitions. Treat analytics, purchases, network retries, persistence, and callbacks as contract-bearing effects, not incidental code inside a view or async closure.

Workflow

1. Identify the owner

• Name the durable owner for each effect: service, coordinator, store, view model, view task, or external SDK.
• Keep one-shot effects out of view identity when remounts, .id(...), previews, or sheet recreation can run the code again.
• Separate view-local state from session, purchase, analytics, or persisted state.

2. Map lifecycle transitions

List the transitions that can start, repeat, cancel, or complete work: