Menu
Core QA engineering mindset for test planning and prioritization. Use when analyzing what to test, designing test cases, prioritizing by risk, or determining coverage strategy. Triggers on "what should I test", "test strategy", "coverage", "prioritize tests", "design test cases", "P0 P1 P2".
Writes, edits, and creates dbt models following best practices. Use when user needs to create new dbt SQL models, update existing models, or convert raw SQL to dbt format. Handles staging, intermediate, and mart models with proper config blocks, CTEs, and documentation.
Apply Domain-Driven Design, Clean Architecture, CQRS, and command/query patterns to code reviews and feature design. Use when analyzing or designing code in Application, Service, Infrastructure, DataAccess, Validation, Domain, or Functions projects, or when addressing architectural concerns, layering, mapping, entities, value objects, repositories, or validators in the Rome Repair Order Service.
Analyzes and refactors code using Domain-Driven Design principles. Use when refactoring domain models, identifying DDD anti-patterns, improving domain clarity, or applying tactical/strategic DDD patterns.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Win competitive rounds: run a clean process, deliver value previews before asking, coordinate partners, and manage timelines. Use when you're trying to close a 'must win' deal against other funds.
End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal.
| name | automation-tester |
| description | Core QA engineering mindset for test planning and prioritization. Use when analyzing what to test, designing test cases, prioritizing by risk, or determining coverage strategy. Triggers on "what should I test", "test strategy", "coverage", "prioritize tests", "design test cases", "P0 P1 P2". |
Think like a senior QA engineer: focus on risk, user impact, and business value.
1. Identify page/feature type
2. Apply type-specific test patterns (see references/test-patterns.md)
3. Assign priority based on risk (see references/priority-matrix.md)
4. Generate test specifications
| Priority | Criteria | Examples |
|---|---|---|
| P0 | App broken if fails | Login, checkout, core navigation |
| P1 | Major feature broken | Search, filters, form validation |
| P2 | Minor/edge cases | Tooltips, animations, rare flows |
title: "Valid login should redirect to dashboard"
suite: "Authentication"
severity: critical | major | normal | minor
priority: high | medium | low
preconditions:
- User exists in system
steps:
- action: Navigate to /login
expected: Login form visible
- action: Enter valid email
expected: Email accepted
- action: Enter valid password
expected: Password masked
- action: Click Sign In
expected: Redirects to dashboard
Smoke Tests (10-15 cases):
Regression (comprehensive):
Is it part of core functionality?
├── Yes → P0
└── No → Continue
Does it handle money/data?
├── Yes → P0 or P1
└── No → Continue
Is it user-facing validation?
├── Yes → P1
└── No → P2