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
kotlin-code-style
Apply Kotlin-specific code style and design guidance for file organization, type design, constructors, extensions, nullability, serialization, coroutines, Flow, and Kotlin unit/integration test style outside Cucumber or BDD. Use when the user wants idiomatic Kotlin conventions or Kotlin-language-specific code review guidance, excluding Spring application architecture, Spring-managed wiring concerns, and Cucumber/BDD-specific test design.
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
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