spring-application-code-style
Apply Spring Boot application-layer conventions for package structure, controllers, services, repositories, transactions, configuration properties, bean wiring, observability, and integration testing. Use when the user wants Spring application structure or Spring application architecture and wiring guidance, including coroutine or Flow usage inside Spring-managed code, especially for WebFlux or coroutine-first services, not shared libraries or framework internals.
Repository SourceNeeds Review
code-practice
Improve or apply language-agnostic, framework-neutral code practices for clean code, maintainability, refactoring, ownership, boundaries, state, error handling, testing, and reusable engineering defaults. Use when the user wants broad code quality guidance rather than Kotlin-, Spring-, or framework-specific conventions.
Repository SourceNeeds Review
kotlin-cucumber-tests
Plan, review, or improve Kotlin Cucumber / BDD tests: decide when Cucumber fits, structure feature files, step definitions, hooks, fixtures, and Kotlin helpers, and keep domain language readable without coupling steps to implementation details. Use when the request explicitly centers on Kotlin Cucumber, Kotlin BDD, feature files, step definitions, hooks, or executable-specification tests and reviews.
Repository SourceNeeds Review
deep-research
Run thorough, evidence-backed research or audit and refresh existing research artifacts with a gap-first workflow: inventory existing knowledge, identify only the missing high-impact gaps, verify important claims with primary sources, and synthesize a decision-useful answer with traceable evidence. Use for research-heavy comparisons, validation, or evidence-backed audits, not routine local code or prompt review.
Repository SourceNeeds Review