القائمة
Generate exhaustive edge cases across 12 dimensions before implementation or testing. Use for 'edge cases for X', 'test scenarios', 'what could go wrong', 'boundary testing'.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Asset Hunter Pro — unused asset detection, dependency graph, duplicate finder, project cleanup automation for Unity
Author game-design diagrams (quest trees, economy flows, narrative branches, level layouts) from copy-ready Mermaid templates. Authoring only — NOT an adapter.
DOTS RPG grid inventory, item passive effects, and set bonuses — polyomino placement, rotation, auto-fit, PassiveEffectSystem, ItemSetBonusSystem, ModifierSource.ItemPassive/ItemSet.
Practical tools and validation methods for game balance — DPS calculators, EHP formulas, spreadsheet layouts, stat audits, difficulty spike detection
GDD structure, templates, and living documentation patterns for game projects — wiki pages, design docs, section layout, sync triggers
Game feel and juice — screen shake, hit stop, particles, animation curves, input responsiveness, feedback timing. Makes actions feel satisfying.
| name | t1k:scenario |
| description | Generate exhaustive edge cases across 12 dimensions before implementation or testing. Use for 'edge cases for X', 'test scenarios', 'what could go wrong', 'boundary testing'. |
| keywords | ["edge-cases","scenarios","boundary","testing","what-could-go-wrong","exhaustive"] |
| version | 1.0.0 |
| argument-hint | <topic|--file path> [--dimensions 1,2,4] [--for-tests] |
| effort | medium |
| origin | theonekit-core |
| repository | The1Studio/theonekit-core |
| module | null |
| protected | true |
Generate comprehensive edge cases before implementing or testing a feature. Covers 12 orthogonal risk dimensions.
/t1k:scenario "user registration flow" # All 12 dimensions
/t1k:scenario --file src/auth/login.ts # Analyze a specific file
/t1k:scenario "payment processing" --dimensions 1,2,3,9 # Specific dimensions only
/t1k:scenario "order API" --for-tests # Output as test-plan format
| # | Dimension | Focus |
|---|---|---|
| 1 | Auth / Permissions | Who can access, what happens when they can't |
| 2 | Concurrency / Race Conditions | Parallel requests, shared state, locks |
| 3 | Network Failure / Timeout | Partial failures, retries, idempotency |
| 4 | Invalid Input / Boundary Values | Null, empty, overflow, malformed data |
| 5 | i18n / l10n | Unicode, RTL, locale-specific formats |
| 6 | Scale / Volume | Large datasets, high throughput, memory |
| 7 | State Transitions | Invalid state sequences, partial updates |
| 8 | Backward Compatibility | Old clients, schema changes, deprecated paths |
| 9 | Error Cascades | One failure causing downstream failures |
| 10 | Config / Env Variation | Missing env vars, wrong config, multiple envs |
| 11 | Data Integrity | Partial writes, constraint violations, corruption |
| 12 | Observability / Logging | Missing logs, PII leakage, trace gaps |
Detailed scenario lists per dimension: references/dimension-details.md
Grouped checklist per dimension with: short description, expected behavior, test approach (unit/integration/E2E).
Output as test-plan structured for the tester agent (tabular format with Test ID, Scenario, Input, Expected, Type).
Pass output directly to /t1k:test as test plan input.
--dimensions to focusTriggers on: scenario, edge cases, edge case, test scenarios, boundary testing, what could go wrong, risk analysis, corner cases