Maintain the repository's Gradle agent skill artifact. Use when updating, calibrating, auditing, reorganizing, validating, or source-indexing `skills/gradle/**`, including Gradle skill runtime guidance, Gradle source/documentation calibration, compatibility snapshots, reference topology, validation gates, or maintenance scripts. Do not use for ordinary Gradle build troubleshooting in user projects.
Gradle development knowledge for agents maintaining builds, build logic, plugins, tasks, dependencies, JVM toolchains, caches, publishing, CI, security, and upgrades. Use when working with Gradle, gradlew, build.gradle(.kts), settings.gradle(.kts), gradle.properties, init.gradle(.kts), libs.versions.toml, dependencies/dependencyInsight reports, dependency locking or verification, Gradle plugins/tasks, TestKit, Java toolchains, Maven/Ant migration, or wrapper upgrades.
Use this skill for VitePress sites that publish Cursor rules, commands, and agent skills through docs/scripts/generate-docs.mjs (bootstrap from template/generate-docs.mjs and template/config.mts when starting fresh). Apply it when editing docs/.vitepress/config.mts and themeConfig.nav, sidebar.generated.mts, GITHUB_BASE, PATHS, FLAT_SECTIONS, the recursive .cursor/skills walker, npm scripts docs:prepare/docs:dev/docs:build, gitignore for generated docs/src trees, or CI paths and workflows for docs. Use it when the user wants to publish or sync .cursor content into docs, fix a broken docs build, add a generated section, replicate this pipeline in another repo, or mentions VitePress together with Cursor rules, commands, or skills—even if they never name generate-docs.mjs or this skill. Do not use it for VitePress-only docs with hand-written Markdown and no generate-docs.mjs pipeline from .cursor, or for generic site styling and content work unrelated to this Cursor-to-docs sync (prefer the general VitePress ski