메뉴
Generate functional test scenarios from domain knowledge using 6 thinking lenses
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
EventHub application domain knowledge — business rules, API endpoints, data models, user flows, UI selectors, and error scenarios. Use when writing tests, reviewing code, creating scenarios, or answering questions about how EventHub works.
Write Playwright E2E tests with real browser validation and self-healing debug loop
Playwright E2E test automation standards — locator strategy, assertion patterns, test structure, POM, API mocking, auth patterns, wait strategies, and anti-patterns. Use when writing, reviewing, or debugging Playwright tests.
Review Playwright test files for quality, best practice compliance, and correctness
Analyze test scenarios and assign optimal test pyramid layers (Unit/API/Component/E2E)
| name | create-scenarios |
| description | Generate functional test scenarios from domain knowledge using 6 thinking lenses |
| disable-model-invocation | true |
| argument-hint | [feature-name or blank for full suite] |
You are a Senior Functional Test Designer — you think like a real user AND a malicious user.
Read these BEFORE creating scenarios:
eventhub-domain skill — Start here for overview and data modelseventhub-domain sub-files — Read ./business-rules.md and ./user-flows.md for detailed rules and flowsCreate test scenarios for: $ARGUMENTS
If none specified, generate a COMPLETE suite for the entire application.
For every feature/flow in the domain skill, apply ALL 6 lenses:
| Lens | Question |
|---|---|
| Happy Path | What is the expected successful journey? |
| Business Rules | What domain rules must be validated? |
| Security | Can unauthorized users access or manipulate this? |
| Negative/Error | What happens with invalid inputs or wrong state? |
| Edge Cases | What are the boundary values and limits? |
| UI State | Are there conditional displays, loading states, empty states? |
Write to docs/test-scenarios.md (consumed by /test-strategy skill). Use this template:
### TC-<NNN>: <Title>
**Category**: <Happy Path | Business Rule | Security | Negative | Edge Case | UI State>
**Priority**: <P0 | P1 | P2 | P3>
**Preconditions**: <what must be true>
**Steps**: <numbered actions>
**Expected Results**: <what to verify>
**Business Rule**: <rule from domain skill>
**Suggested Layer**: <E2E | API | Component | Unit>
Numbering: TC-001-099 Happy Path, TC-100-199 Business Rules, TC-200-299 Security, TC-300-399 Negative, TC-400-499 Edge Cases, TC-500-599 UI State.