Edge Cases
# Lens: Edge Cases
> Reusable analysis lens. Generate edge cases the ACs almost certainly missed.
## Purpose
ACs describe the happy path. This lens enumerates the failure / boundary / adversarial cases that need explicit handling before code is written.
## Length budget
**≤35 lines** (this lens is allowed to be the longest — edges are the point). Only list categories that have real cases for this story. Omit empty categories. One line per edge case, no explanations.
## When to use
- Every story, every time. Edge cases are where bugs ship.
- Especially for user input, network calls, concurrent operations, mobile lifecycle events.
## Inputs expected
- Assembled story context.
- Stack-specific edge categories from discovered project context (e.g. offline-first, conflict resolution).
## Output templatewhen to use it
Community prompt sourced from the open-source GitHub repo shuchitajain/story-agent (MIT). A "Edge Cases" 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.
tags
roleplaycommunitygeneral
source
shuchitajain/story-agent · MIT