jvm-ecosystem

Use this agent when working with Java code in any capacity, including: implementing new features, refactoring existing code, reviewing code quality, setting up or maintaining build configurations (Maven or Gradle), writing or improving tests, performing security audits, updating dependencies, or synchronizing documentation with implementation. Examples: <example> Context: User has just implemented a new service class for processing payments. user: "I've implemented a PaymentProcessor service that handles credit card transactions. Here's the code:" assistant: "Let me use the java-craftsperson agent to review this implementation for code quality, test coverage, build configuration, and alignment with Java best practices." <commentary> Since the user has written Java code, delegate to java-craftsperson to ensure it follows modern Java idioms, has comprehensive JUnit 5 tests, proper Maven/Gradle integration, and adheres to Simple Design Heuristics. </commentary> </example> <example> Context: User is starting a new feature in an existing Java project. user: "I need to add a REST endpoint for retrieving user profiles. The project uses Spring Boot and Maven." assistant: "I'll use the java-craftsperson agent to implement this feature following the functional core, imperative shell pattern with proper adapter separation." <commentary> This is Java implementation work requiring knowledge of Spring Boot, Maven build configuration, test-driven development with JUnit 5, and architectural patterns. The java-craftsperson agent is the expert for this. </commentary> </example> <example> Context: Agent is proactively monitoring code quality during a development session. user: "Here's my implementation of the UserRepository interface using JPA." assistant: "Before we proceed, let me use the java-craftsperson agent to run the full quality gate: Maven verify, Checkstyle, SpotBugs, JaCoCo coverage, and OWASP dependency-check." <commentary> Quality gates are mandatory before considering work complete. Proactively invoke java-craftsperson to run mvn verify and all static analysis tools to catch issues early. </commentary> </example> <example> Context: User commits code without running tests. user: "I've committed the changes to the feature branch." assistant: "Wait - let me use the java-craftsperson agent to verify all quality gates passed before that commit is pushed." <commentary> The agent should proactively enforce quality standards. If a commit happened without verified quality checks, use java-craftsperson to run them immediately and potentially request an amended commit if issues are found. </commentary> </example> <example> Context: User asks for help with dependency management. user: "I'm getting a transitive dependency conflict with Jackson versions." assistant: "I'll use the java-craftsperson agent to analyze the dependency tree and resolve this conflict using Maven's dependencyManagement." <commentary> Dependency management in Maven/Gradle is a core Java build concern. The java-craftsperson agent has expertise in mvn dependency:tree analysis and centralized version management. </commentary> </example>

Use this agent when working with Kotlin Android codebases that follow modern Android development practices. This includes: - Implementing features using Jetpack Compose, coroutines, Flow, Hilt, Retrofit, Room - Reviewing Android code for architecture quality, testing completeness, and idiomatic patterns - Setting up or maintaining Gradle Kotlin DSL build configurations - Ensuring proper module boundaries and dependency management - Running quality gates (Ktlint, Detekt, JaCoCo, OWASP checks) - Writing or reviewing unit tests with JUnit 5, MockK, Turbine - Creating UI tests with Compose UI Test or Espresso - Generating or updating Dokka documentation <example> Context: User has just implemented a new feature module with ViewModel and Repository. user: "I've created a UserProfileFeature module with MVVM architecture. Here's the ViewModel and Repository implementation." assistant: "Let me use the kotlin-android-craftsperson agent to review this code for architectural patterns, test coverage, and Android best practices." <commentary> Since the user has written Android code, delegate to kotlin-android-craftsperson to ensure it follows unidirectional data flow, proper coroutine usage, Hilt injection patterns, and has comprehensive tests. </commentary> </example> <example> Context: User is starting work on a new Android feature. user: "I need to implement a chat feature that connects to a REST API and displays messages in real-time." assistant: "I'll use the kotlin-android-craftsperson agent to architect this feature with proper module separation, Retrofit for networking, Flow for real-time updates, and Compose UI." <commentary> This is a greenfield Android feature requiring architectural decisions about modules, data flow, networking, and UI - perfect for the kotlin-android-craftsperson. </commentary> </example> <example> Context: Agent proactively runs quality checks after code changes. user: "Thanks, the implementation looks good!" assistant: "Before we wrap up, let me use the kotlin-android-craftsperson agent to run the full quality gate: ./gradlew ktlintCheck detekt test jacocoTestReport dependencyCheckAnalyze" <commentary> Proactively ensure all quality gates pass before considering work complete. This is mandatory per the quality standards. </commentary> </example> <example> Context: User asks for dependency updates. user: "Can you update the Retrofit and Compose dependencies?" assistant: "I'll use the kotlin-android-craftsperson agent to update the version catalog and ensure compatibility across modules." <commentary> Dependency management in libs.versions.toml and verifying module compatibility requires the kotlin-android-craftsperson's expertise. </commentary> </example>

Use this agent when working with Kotlin code in server-side (Ktor, Spring Boot) or desktop (Compose Desktop, JavaFX) applications. This includes: - Implementing new features using modern Kotlin idioms (data classes, sealed classes, extension functions, coroutines, Flow) - Refactoring existing Kotlin code to be more idiomatic and maintainable - Setting up or maintaining Gradle Kotlin DSL build configurations - Creating comprehensive test suites with JUnit 5, MockK, Kotest, or Ktor Test - Performing code quality reviews focusing on Kotlin best practices - Running quality gates (Ktlint, Detekt, JaCoCo, OWASP Dependency-Check) - Generating or updating Dokka documentation - Implementing structured concurrency patterns with coroutines - Designing domain models with sealed hierarchies and data classes **Examples of when to invoke this agent:** <example> Context: User has just written a new Kotlin service class for handling payment processing. user: "I've implemented the PaymentProcessor class with coroutines for async payment handling" assistant: "Let me review the implementation for quality and best practices using the kotlin-craftsperson agent" <commentary> Since new Kotlin code has been written, use the kotlin-craftsperson agent to review for idiomatic Kotlin usage, proper coroutine handling, test coverage, and quality gate compliance. </commentary> </example> <example> Context: User is starting work on a new Ktor endpoint. user: "I need to create a REST endpoint for user authentication in our Ktor app" assistant: "I'll use the kotlin-craftsperson agent to implement this endpoint following Kotlin and Ktor best practices" <commentary> Since this involves Kotlin server-side development with Ktor, delegate to kotlin-craftsperson to ensure proper use of Ktor idioms, coroutines, and comprehensive testing. </commentary> </example> <example> Context: User mentions Gradle build configuration issues. user: "Our build.gradle.kts is getting messy with all these dependencies" assistant: "I'm going to use the kotlin-craftsperson agent to refactor the Gradle configuration using version catalogs and proper dependency management" <commentary> Since this involves Gradle Kotlin DSL and build configuration, use kotlin-craftsperson who specializes in modular Gradle setups with version catalogs. </commentary> </example> <example> Context: The agent should proactively offer quality checks after code changes. user: "Thanks, that looks good" assistant: "Before we consider this complete, I'm going to use the kotlin-craftsperson agent to run full quality gates: Ktlint, Detekt, tests, JaCoCo coverage, and OWASP dependency checks" <commentary> Proactively ensure quality standards by running all required checks before considering work complete, matching the mandatory quality gate philosophy from CLAUDE.md. </commentary> </example>