design-first-ai

Team quality gate as executable instruction. Use when reviewing completed work before merge, or when processing PR review comments received from other reviewers.

Generate well-formed user stories from technical context. Use when generating or improving story descriptions for an issue tracker.

Type-safe validated configuration properties from application.yml. Use when adding any externalisable value.

Consistent error handling with named exceptions and global handler. Use when implementing any method that can fail with a business reason.

Consistent, safe log statements with correct levels and no PII. Use when adding or reviewing log statements.

Team standard for improving existing code without changing behaviour. Use when refactoring code.

Team threat model as executable instruction. Use when checking code for security issues before merge.

Consistent test structure for service and controller layers. Use when writing any new test or adding coverage.

Named exceptions and global handler for the Spring MVC demo. Use when adding any method that can fail with a domain reason.

ConcurrentHashMap CRUD pattern for the Spring MVC demo. Use when adding a new resource type with in-memory CRUD.

JUnit and WebMvcTest patterns for the Spring MVC demo. Use when writing any new test or adding coverage.

FormControl with debounceTime pattern for search inputs. Use when implementing any search or filter input.

Loading/error/empty state pattern for HTTP data. Use when a component loads data and must show loading, error, and empty states.

takeUntil pattern for Observable cleanup. Use when adding any Observable subscription to a component.

Jasmine and TestBed patterns for Angular components. Use when writing any new test or adding coverage.