Skip to main content
prompt GP ChatGPT

Gradle Build taste — ChatGPT prompt: what it does, how to install

Gradle Build taste is a ChatGPT prompt that enforces fast JVM builds using Kotlin DSL and the wrapper.

CC0-1.0 ★ 178,201 updated 2026-10-24

Open on GitHub

What Gradle Build taste does

The prompt sets standards for JVM project configuration with a focus on speed and predictability. It requires using build.gradle.kts for scripts, committing the Gradle wrapper, and running builds via ./gradlew.

Instructions mandate setting Java versions through toolchains, managing versions in gradle/libs.versions.toml, and sharing build logic via convention plugins in build-logic. Tasks should register lazily with the Provider API, and builds must enable the configuration cache.

For dependencies, the setup dictates using implementation by default and locking versions for production. Secrets must stay out of the repository, and ./gradlew check serves as the single command for local and CI testing.

What it helps with

  • configure Kotlin DSL for JVM builds
  • manage dependency versions in catalog
  • enable build and configuration cache
  • set up Java toolchain in Gradle

Example prompts for the agent

  • Apply Gradle Build taste standards to this JVM project
  • Set up Gradle configuration following Gradle Build taste rules
  • Review build setup against Gradle Build taste best practices

How to install Gradle Build taste

How to use

Paste the text at the start of a chat or into project instructions

Questions about Gradle Build taste

How to install Gradle Build taste in Claude Code?

Create the file .claude/commands/prompts.csv.md and add the prompt text to it.

What does Gradle Build taste do?

It provides rules for fast JVM builds with Gradle, Kotlin DSL, dependency catalogs, and caching.

What is required to use Gradle Build taste?

The project needs a committed Gradle wrapper and Java toolchain support.

Source text

prompts.csv · CC0-1.0
# Gradle Build taste of a JVM developer who wants fast and boring builds
- Use the Kotlin DSL (`build.gradle.kts`) for build scripts so editors give real completion and type checking. Confidence: 0.85
- Always commit the Gradle wrapper and run builds with `./gradlew`, never a globally installed Gradle. Confidence: 0.95
- Verify the wrapper distribution with `distributionSha256Sum` so a tampered download never runs in CI. Confidence: 0.75
- Keep every dependency and plugin version in a `gradle/libs.versions.toml` version catalog. Confidence: 0.90
- Share build logic through convention plugins in `build-logic`, not through `allprojects` or `subprojects` blocks. Confidence: 0.85
- Set the Java version with a toolchain (`java { toolchain { languageVersion = ... } }`) instead of relying on whatever JDK is installed. Confidence: 0.90
- Enable the build cache and configuration cache, and treat any task that breaks them as a bug to fix. Confidence: 0.80
- Turn on `org.gradle.parallel=true` and a sensible `org.gradle.jvmargs` in `gradle.properties` checked into the repo. Confidence: 0.80
- Register tasks lazily with `tasks.register` and the Provider API; avoid `tasks.create` and eager configuration. Confidence: 0.85
- Declare task inputs and outputs properly so up-to-date checks and caching work for custom tasks. Confidence: 0.85
- Use `implementation` by default and expose `api` only for types that are truly part of a module's public interface. Confidence: 0.90
- Lock or verify dependencies with dependency locking or `verification-metadata.xml` for builds that ship to production. Confidence: 0.70
- Never use dynamic versions like `1.+` or `latest.release` in anything that gets released. Confidence: 0.90
- Use a platform or BOM to align versions of related libraries such as Jackson, Netty or Spring. Confidence: 0.80
- Keep modules small and focused, with a clear dependency direction and no cycles between them. Confidence: 0.80
- Publish build scans or keep profiling output for slow CI builds, and look at them before guessing what to optimize. Confidence: 0.70
- Make `./gradlew check` the single command that runs tests, static analysis and formatting checks locally and in CI. Confidence: 0.90
- Keep secrets like signing keys and repository passwords in environment variables or CI secrets, never in `gradle.properties` in the repo. Confidence: 0.95
- Avoid running shell scripts from the build when a typed Gradle task or plugin can do the job. Confidence: 0.70
- Upgrade Gradle regularly and fix deprecation warnings before they become errors in the next major version. Confidence: 0.80
- Keep the root build script almost empty; real configuration lives in convention plugins and module scripts. Confidence: 0.75

© f · CC0-1.0 · f/prompts.chat

Similar prompts

All prompts for Backend and APIs →

From the same set218

The whole set →
Jupyter Notebook taste Jupyter Notebook taste is a ChatGPT prompt for clean, repeatable notebooks. It applies when an analysis is prepared for review or a commit. GP ChatGPT ★ 178,201repo stars MongoDB taste MongoDB taste is a ChatGPT prompt for MongoDB document design around query patterns, indexes, and schema checks. Claude Code loads it from a command file. GP ChatGPT ★ 178,201repo stars API Key and Credential Rotation Runbook (JSON) The API Key and Credential Rotation Runbook (JSON) is a prompt for ChatGPT, Claude.ai, and Claude Code that builds a secure secret rotation plan. It outputs a structured JSON object with steps. GP ChatGPT ★ 178,201repo stars Storybook taste The Storybook taste prompt for ChatGPT sets conventions for writing component stories in Storybook. It covers story structure, component states, interaction checks and sharing changes for review. GP ChatGPT ★ 178,201repo stars RAG Pipeline taste RAG Pipeline taste — a prompt for ChatGPT defines engineering standards for building retrieval systems and evaluating generation accuracy. GP ChatGPT ★ 178,201repo stars Makefile taste The Makefile taste ChatGPT prompt sets conventions for project Makefiles. It guides target structure, recipes, and dependencies so make can act as the project’s front door. GP ChatGPT ★ 178,201repo stars API Deprecation and Sunset Plan Builder (YAML) API Deprecation and Sunset Plan Builder (YAML) is a prompt that turns API deprecation details into a structured YAML sunset plan with timelines, communication strategies, and migration steps. GP ChatGPT ★ 178,201repo stars Nginx Config taste The Nginx Config taste ChatGPT prompt sets conventions for Nginx configuration and operations. Use it while configuring virtual hosts, HTTPS, or proxy routes. GP ChatGPT ★ 178,201repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open