brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
Explorer les Skills
Développement · SKILL.md
kotlin-tooling
kotlin-toolingConfigure Kotlin build and quality tooling, including Gradle Kotlin DSL, Version Catalogs, KMP, ktlint, Detekt, MockK, coverage, and quality plugins. Use for Kotlin-specific build, lint, test-tool, or coverage setup; defer Java-only tooling and Spring test behavior.
Independent GitHub snapshot · Automated classification · Original documentation governs
Documentation de la Skill
GitHubname: kotlin-tooling description: Configure Kotlin build and quality tooling, including Gradle Kotlin DSL, Version Catalogs, KMP, ktlint, Detekt, MockK, coverage, and quality plugins. Use for Kotlin-specific build, lint, test-tool, or coverage setup; defer Java-only tooling and Spring test behavior. metadata: triggers: files: - 'build.gradle.kts' - 'libs.versions.toml' - 'detekt.yml' keywords: - mockk - kts - version catalog - kotest
Kotlin Tooling Standards
Priority: P2 (MEDIUM)
Implementation Guidelines
- Gradle DSL: Use Kotlin DSL (
build.gradle.kts) exclusively — 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, readable test output.
Anti-Patterns
- No Groovy Gradle: Use Kotlin DSL (build.gradle.kts) exclusively; avoid legacy build.gradle.
- No Mockito in Kotlin:
when/thenconflicts with Kotlinwhen; use MockK (every/verify). - No Hardcoded Versions: Manage all versions in libs.versions.toml; never inline in build files.