plugins

A module in a large project spends most of its build file repeating the same setup: the same target platforms, the same compiler flags, the same test dependencies. These plugins move that setup out of the build file and leave behind a scaffold {} block where a module declares only the choices it actually has to make.

Apply the root plugin on the root project, then one plugin per module.

// root build.gradle.kts
plugins {
  id("io.github.thomaskioko.gradle.plugins.root")
}

// a module's build.gradle.kts
plugins {
  id("io.github.thomaskioko.gradle.plugins.multiplatform")
}

scaffold {
  useMetro()
}

The root plugin sets the daemon toolchain vendor, configures dependency analysis, and checks that it was applied to the root project and not a module. Every module plugin configures only its own module, so the suite works with Gradle's isolated projects turned on.

Packages

io.github.thomaskioko.gradle.plugins

jvm

The plugin entry points. Each one is registered under an io.github.thomaskioko.gradle.plugins.* identifier and is applied from a build file.

io.github.thomaskioko.gradle.plugins.checks

jvm

Static analysis applied to a module. SpotlessPlugin configures Spotless with the project's ktlint setup. With app.enableLintRules=true it also adds the custom rule set from the lint-rules artifact, so those rules run alongside the standard ones.

io.github.thomaskioko.gradle.plugins.extensions

jvm

The scaffold {} block and the platform blocks nested inside it. This is where a module says what it is: which platforms it targets, whether it uses Compose, which dependency injection and code generation it needs, and which dependencies to hold to a baseline.