skills.rest
Enso-Soft
Enso-SoftCOMMUNITY
Explore all skills by this author →
GitHub

android-conventions

Standardize Android/Kotlin naming, patterns, and code style conventions.

1|Updated Dec 3, 2024
Search Tags:#architecture#style#coding#conventions#android#kotlin#naming
One-click install
npx skills add https://github.com/Enso-Soft/lotto-assist --skill android-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: android-conventions
Source: https://github.com/Enso-Soft/lotto-assist/tree/main/.claude/skills/android-conventions
Command: npx skills add https://github.com/Enso-Soft/lotto-assist --skill android-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines Android/Kotlin coding conventions to ensure consistency and readability across the codebase.

Core Features & Use Cases

  • Naming conventions for classes, interfaces, and data sources (e.g., GetLottoResultUseCase, LottoRepository, LottoDao).
  • Function and member naming patterns (e.g., invoke for UseCases, on{Action} handlers, to{Target} mappers).
  • Architecture and layering guidelines to enforce clean separation of concerns.

Quick Start

Create a new feature and name interfaces and classes following the conventions, e.g., HomeViewModel, HomeContract, GetLottoResultUseCase.

Frequently Asked Questions about android-conventions

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

FAQPage Schema
How do I establish consistent naming conventions for Android and Kotlin classes?▼

Android coding conventions standardize class naming across UseCase, Repository, ViewModel, DAO, and Entity layers—for example, GetLottoResultUseCase, LottoRepository, LottoDao—ensuring consistency and readability throughout your codebase.

What are forbidden patterns in modern Android and Kotlin development?▼

Conventions prohibit deprecated patterns including LiveData, AsyncTask, GlobalScope, findViewById, XML-only layouts, and mutable public collections, replacing them with preferred modern alternatives like Flow, suspend functions, and immutable state hoisting.

How should I structure function naming in Android architecture layers?▼

Function naming follows specific patterns: invoke for UseCases, on{Action} for event handlers, and to{Target} for mapper functions, creating a predictable naming scheme across feature layers.

Can I apply these conventions during code review and refactoring?▼

Yes, these conventions are enforceable across feature creation, refactoring, and code reviews, standardizing practices for naming rules, style guidelines, and preferred architectural patterns throughout active development cycles.

What's the difference between naming conventions and architectural guidelines in Android development?▼

Naming conventions define specific patterns for classes and functions, while architectural guidelines enforce clean separation of concerns and layering principles; this Skill combines both to ensure consistency and maintainability.

Related Skills

Explore More Software Engineering Skills→
rock-hurock-hu

android-gradle-logic

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

Community
Advanced
kleon6436kleon6436

kotlin-coding-standards

Enforce Kotlin coding conventions across source files.

Community
Intermediate
truongnattruongnat

android-pro

Guide Kotlin and Jetpack Compose Android development with MVVM/MVI architecture.

Community
Advanced
koralliskorallis
90

standards-enforcement

Configure ESLint, Prettier, and Husky to enforce coding standards.

Community
Intermediate