large-featureUse when a feature touches 5+ files, involves multiple layers (API + DB + frontend), or will take more than one session to complete. Enforces structured decomposition with design-first, task breakdown, review gates, and integration verification. Prevents context drift during long implementation sess
operating-standardUse at every session start and throughout all development work. This is the core engineering standard — it governs session start/end procedures, code quality rules, investigation protocol, circuit breakers, security baselines, performance targets, commit format, rollback playbooks, and observability
tddUse when implementing any new feature, endpoint, service method, or critical flow. Enforces strict RED-GREEN-REFACTOR cycles where tests must fail before implementation exists. Does NOT trigger for quick bug fixes, config changes, documentation, single-line patches, or UI tweaks with no logic.