Agent skill
Kotlin Tooling Standards
Build tools (Gradle KTS), Static Analysis (Detekt), and Testing standards.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tooling-hoangnguyen0403-agent-skills-standar-6
Metadata
Additional technical details for this skill
- labels
-
kotlin tooling gradle detekt ktlint testing
- triggers
-
{ "files": [ "build.gradle.kts", "libs.versions.toml", "detekt.yml" ], "keywords": [ "gradle", "kts", "detekt", "mockk", "junit" ] }
SKILL.md
Kotlin Tooling Standards
Priority: P2 (RECOMMENDED)
Consistent build and quality verification tools.
Implementation Guidelines
- Gradle DSL: Use Kotlin DSL (
build.gradle.kts) exclusively. It provides type safety and better IDE support. - Version Management: Use Version Catalogs (
libs.versions.toml). - Linter: Use Ktlint for formatting and Detekt for complexity/code-smell analysis.
- Testing: Use MockK for mocking (first-class Kotlin support). Use JUnit 5.
- Assertions: Use Truth or Kotest Assertions for fluent reading.
Anti-Patterns
- Groovy Gradle: Avoid legacy
build.gradlefiles. - Mockito (Java): Avoid Mockito if possible;
when/thensyntax conflicts with Kotlinwhen. Use MockK (every/verify). - Hardcoded Versions: Don't put versions in build files. Use the catalog.
Code
For full MockK testing templates and libs.versions.toml setup:
references/testing-tooling.md
// Modern Gradle KTS + Version Catalog
dependencies {
implementation(libs.kotlin.stdlib)
testImplementation(libs.mockk)
}
// Concise MockK Verify
verify(exactly = 1) { repo.getUser("1") }
Related Topics
best-practices | testing
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?