vcscenario

# vc:scenario — Edge Case & Scenario Explorer Decompose any feature or code path across 12 dimensions to surface edge cases, risks, and test targets before implementation begins. ## When to Use - Before implementing complex or stateful features - Before writing tests (generates test targets) - Risk assessment during planning or code review - API design review — surface contract edge cases early ## When NOT to Use - Trivial single-line changes or cosmetic UI tweaks - Already well-tested, stable code with no recent modifications - Pure configuration changes with no logic paths --- ## 12 Decomposition Dimensions Not all 12 apply to every feature. Identify relevant dimensions first, then generate scenarios only for those. | # | Dimension | What to Look For | |---|-----------|------------------| | 1 | **User Types** | admin, guest, banned, new user, power user, bot/scraper | | 2 | **Input Extremes** | empty, null, max length, unicode, special chars, SQL/script injection | | 3 | **Timing** | concurrent access, race conditions, timeout, slow network, retry storms | | 4 | **Scale** | 0 items, 1 item, 1M items, pagination boundary, cursor wrap | | 5 | **State Transitions** | first use, mid-flow abort, resume after crash, partial completion | | 6 | **Environment** | mobile/low-end CPU, no JS, screen reader, proxy/VPN, different timezone/locale | | 7 | **Error Cascades** | DB down, API timeout, disk full, OOM, network partition, partial write | | 8 | **Authorization** | expired...