cleancode

Provide Java, Kotlin, and Spring coding guidelines enforcing KISS, DRY, and YAGNI principles.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/gykk16/spring-skeleton --skill cleancode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleancode
Source: https://github.com/gykk16/spring-skeleton/tree/main/.omc/skills/cleancode
Command: npx skills add https://github.com/gykk16/spring-skeleton --skill cleancode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write cleaner, more maintainable, and human-readable code by adhering to established principles like KISS, DRY, and YAGNI, reducing technical debt and improving collaboration.

Core Features & Use Cases

  • Principle Enforcement: Provides guidelines for Keep It Simple, Stupid (KISS), Don't Repeat Yourself (DRY), and You Aren't Gonna Need It (YAGNI).
  • Readability Standards: Offers best practices for meaningful naming, consistent conventions, and appropriate abstraction levels.
  • Language-Specific Idioms: Includes tips for Java and Kotlin, focusing on immutability, null safety, and idiomatic usage.
  • Spring Best Practices: Covers constructor injection, layer separation, and exception handling.
  • Testability Focus: Emphasizes designing code for ease of testing through pure functions and small units.

Quick Start

Apply clean code principles to refactor the provided Java code snippet.

Frequently Asked Questions about cleancode

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

FAQPage Schema
How do I write clean and maintainable Java code?

Write clean Java code by applying KISS, DRY, and YAGNI principles, using meaningful naming, consistent conventions, and constructor injection to reduce technical debt and improve collaboration.

What are the best practices for idiomatic Kotlin usage?

Idiomatic Kotlin best practices focus on immutability, null safety, and appropriate abstraction levels to ensure human-readable, maintainable code while avoiding unnecessary complexity.

How do I apply clean code principles to refactor a Spring application?

Refactor Spring applications by enforcing layer separation, constructor injection, and proper exception handling, while designing small units and pure functions for testability.

Does writing clean code require specific dependencies or tools?

Writing clean code requires no external dependencies, relying solely on applying established coding standards like KISS, DRY, YAGNI, and testable design principles directly.

What is the best way to improve code readability and testability?

Improve code readability and testability by enforcing meaningful naming, consistent conventions, appropriate abstraction levels, pure functions, and small units for easier testing.