skills.rest
ClankerGuru
ClankerGuruCOMMUNITY
Explore all skills by this author →
𝕏@ClankerGuruGitHub

naming-conventions

Standardize Kotlin and Gradle identifiers across packages, classes, and plugins.

Updated Apr 8, 2026
Search Tags:#kotlin#gradle#naming#coding-conventions#package-naming#plugin-ids
One-click install
npx skills add https://github.com/ClankerGuru/opsx --skill naming-conventions-clankerguru
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: naming-conventions
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/naming-conventions
Command: npx skills add https://github.com/ClankerGuru/opsx --skill naming-conventions-clankerguru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines Kotlin and Gradle naming conventions to ensure consistent, readable identifiers across packages, classes, and plugins.

Core Features & Use Cases

  • Establishes naming rules for packages (lowercase, no underscores)
  • Class naming (PascalCase), Function naming (camelCase), and Gradle task IDs (kebab-case)
  • Documents plugin IDs, file naming, and test naming conventions to ensure a uniform codebase
  • Use Case: When starting a new Kotlin/Gradle module, apply these conventions to quickly align code structure and avoid refactoring later

Quick Start

Apply the Kotlin and Gradle naming conventions to a new module or artifact in your project.

Frequently Asked Questions about naming-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the standard naming conventions for Kotlin packages and classes?▼

Standard Kotlin naming conventions require packages to use lowercase letters without underscores, while classes must use PascalCase to ensure consistent, readable identifiers across your codebase.

How do I format Gradle plugin IDs and task names in a Kotlin project?▼

Gradle plugin IDs and task names should be formatted using kebab-case to maintain uniform structure and prevent refactoring issues during project onboarding or plugin development.

When should I apply Kotlin and Gradle naming conventions during development?▼

Apply Kotlin and Gradle naming conventions during project onboarding, code reviews, and plugin development to enforce consistent identifier rules across packages, classes, files, and tasks from the start.

How do I name Kotlin functions and test files according to coding conventions?▼

Kotlin functions should use camelCase, while test files and standard files follow specific naming rules to establish a uniform codebase and avoid technical debt during module creation.

Does this convention cover both Gradle plugin IDs and Kotlin class file naming?▼

Yes, it documents plugin IDs, file naming, class naming, and test naming conventions to standardize Kotlin and Gradle identifiers across your entire project structure.

Why should I standardize Gradle task IDs and package naming early in a project?▼

Standardizing Gradle task IDs and package naming early streamlines readability and ensures consistent identifiers across packages, classes, and plugins, helping you avoid costly refactoring later.

Related Skills

Explore More Software Engineering Skills→
new-silvermoonnew-silvermoon
915

android-gradle-logic

Centralize Android Gradle build logic with Kotlin DSL convention plugins.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
thinhtt264thinhtt264

android-gradle-logic

Centralize Android Gradle build logic with convention plugins and version catalogs.

Community
Advanced
ClankerGuruClankerGuru

ktlint

Enforce Kotlin code style and formatting using ktlint presets and editorconfig.

Community
Intermediate