kotlin-api-design-reviewer

Review Kotlin public APIs for naming, visibility, and interface design issues.

3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Desquared/agents-rules-skills --skill kotlin-api-design-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-api-design-reviewer
Source: https://github.com/Desquared/agents-rules-skills/tree/main/Android/skills/kotlin-api-design-reviewer
Command: npx skills add https://github.com/Desquared/agents-rules-skills --skill kotlin-api-design-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Kotlin API design often suffers from inconsistent naming, poorly designed interfaces, and non-idiomatic constructs that hinder usability and maintainability. This Skill provides criteria and guidance to review public APIs, library interfaces, and reusable components for Kotlin projects.

## Core Features & Use Cases

  • Enforces Kotlin naming rules: lowerCamelCase for functions and properties, UpperCamelCase for classes, and UPPER_SNAKE_CASE for constants.
  • Promotes proper interface design, explicit visibility, immutability where possible, and appropriate data class usage for DTOs.
  • Used during library design, API reviews, and when user asks for Kotlin naming conventions compliance or API design feedback.

### Quick Start Review a Kotlin module to verify naming conventions, interface design, and overall API quality.

Frequently Asked Questions about kotlin-api-design-reviewer

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

FAQPage Schema
How do I check Kotlin naming conventions in my API?

To check Kotlin naming conventions, verify functions and properties use lowerCamelCase, classes use UpperCamelCase, and constants use UPPER_SNAKE_CASE. This review identifies naming inconsistencies across public APIs and module boundaries.

What is the best way to review a Kotlin library's public API surface?

Reviewing a Kotlin public API surface involves checking interface design, explicit visibility, immutability, and appropriate data class usage for DTOs. This process identifies API surface issues and enforces idiomatic usage guidelines.

How do I enforce immutability and data class usage in Kotlin?

Enforce immutability and data class usage in Kotlin by applying explicit visibility rules and reserving data classes for DTOs. This approach reviews module boundaries to promote safe, consistent API design.

Can I use Kotlin API design review for Android module boundaries?

Yes, Kotlin API design review applies to public APIs, libraries, and module boundaries within Android projects. It focuses on naming, visibility, mutability, and idiomatic usage to ensure clean interfaces.

Why does my Kotlin API design have interface flaws?

Kotlin API interface flaws often stem from inconsistent naming, poor visibility control, and non-idiomatic constructs. Reviewing interface design and applying explicit visibility rules resolves these maintainability issues.

What are the limitations of automated Kotlin API reviews?

Automated Kotlin API reviews focus strictly on structural criteria like naming rules, mutability, and return types. They do not assess runtime behavior or business logic, serving only as guardrails for public API design.