The tool
.png)
Inputs:
- Feature description (free text): what the feature does
- Feature type (selector, optional): form, list, search, upload, payment, auth
Output: A grouped list of edge cases and states to design: empty, loading, error, partial data, permission denied, offline, timeout, long content, zero results, and first-run. Each with a one-line note on what to consider. Exportable.
Behavior: Generates instantly in-browser, no login. Items are checkable and exportable.
The happy path is the cheap part
Every feature demo shows the happy path: data loads, the form submits, everyone claps. Then it ships and users hit the empty state nobody designed, the error with no recovery, the permission wall with a dead end. Those screens are where products feel broken, and they are exactly the ones that get cut under deadline because they were never on the list. The cost is real and well documented in 10 edge cases every PM misses, where the gaps get 50 to 100 times more expensive after launch.
This tool puts the states on the list before design starts. You describe the feature, it returns the edge cases grouped and annotated. For depth, see edge case examples in software, edge case testing in UX, and the case for documenting edge cases before development.
How it works
1. Describe the feature. Enter what it does in plain language.
2. Optionally set the type. A payment flow has different edge cases than a search box.
3. Generate the list. Get grouped edge cases with notes.
4. Design for each. Use the list so no state ships unhandled.
A worked example
Take a file upload. The happy path is one screen. The generator surfaces the rest: no file selected, file too large, wrong format, upload in progress, network drop mid-upload, server rejection, and the success state. Suddenly a "simple" feature is eight screens, and the seven beyond the happy path are where the error-state design patterns matter most. Better to know that before design than to discover it in a support ticket.
This is what Figr does, natively
Edge cases are not an add-on for Figr; they are central to it. Through the Visual Context Graph, Figr reasons across your product to map the states a feature needs and produces Figma-ready screens for them, on your design system, not just the happy path. This free tool gives you the list; Figr designs the screens. That is also the core difference in the Figr vs UX Pilot comparison: context-aware reasoning about states, not one generation per prompt. Pair this with the acceptance criteria generator to make each state testable, the design review checklist to verify them, and the PRD template generator to capture them in the spec.
Who this is for
This is for product managers and designers on real products, where the difference between a good feature and a buggy one is how the states are handled.
What this tool is not
It lists likely edge cases; it does not know your specific business rules, so a complex feature still needs your judgment about which states exist and matter. It is also a free, standalone tool, not a Figr product feature.
FAQ
Is the edge case generator free?
Yes, free and no sign-up.
What edge cases does it cover?
Empty, loading, error, partial data, permission denied, offline, timeout, long content, zero results, and first-run, adjusted to the feature type.
Can I export the list?
Yes, as a checkable, shareable list.
Does Figr design these states for me?
The free tool lists them. Figr the product reasons through them from your product context and produces Figma-ready screens for each.
How is this different from Figr the product?
This is a free listing tool. Figr the product is an AI product designer that turns product context into UX decisions and Figma-ready design.