State Changes

GPTClaudeGemini··▲ 991 copies·updated 2026-07-14

state-changes.prompt

# Lens: State Changes

> Reusable analysis lens. Surface every persisted state mutation a change introduces.

## Purpose
Catch DB schema changes, cache invalidations, feature-flag toggles, local-storage shifts, and migration ordering issues before implementation begins.

## Length budget
**≤30 lines.** Only list stores that are actually touched. Schema diff in one line per field. Migration plan in 1-2 sentences max.

## When to use
- Any story that adds / removes / renames a field on a persisted entity.
- Anything touching feature flags, environment-keyed config, or user preferences.
- Caching changes (TTLs, keys, invalidation triggers).
- Mobile: SharedPreferences / Hive / sqflite / secure storage edits.

## Inputs expected
- Assembled story context (`story.md` + ACs + attachments).
- Workspace overview for current schema / storage conventions.

## Output template

when to use it

Community prompt sourced from the open-source GitHub repo shuchitajain/story-agent (MIT). A "State Changes" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.