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.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "spring-application-code-style" with this command: npx skills add rotilho/skillsmp-rotilho-rotilho-spring-application-code-style
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
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.
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.
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.
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.