clean-code

Apply pragmatic coding standards including SRP, DRY, naming and structure to improve code quality and maintainability.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/jieni777/opencode-config-backup --skill clean-code-jieni777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/jieni777/opencode-config-backup/tree/main/skills/clean-code
Command: npx skills add https://github.com/jieni777/opencode-config-backup --skill clean-code-jieni777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards help developers avoid over-engineering and unnecessary comments, ensuring code is concise, readable, and maintainable.

Core Features & Use Cases

  • Enforces SRP, DRY, KISS, YAGNI and other guiding principles to improve code quality.
  • Provides structured rules for naming, functions, and code structure to reduce bugs and complexity.
  • Useful for teams aiming to adopt a consistent, scalable coding discipline across projects.

Quick Start

Apply these guidelines to start writing concise, maintainable code in your project today.

Frequently Asked Questions about clean-code

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

FAQPage Schema
What are the best practices for writing maintainable code in software engineering?

Maintainable code relies on pragmatic coding standards like SRP, DRY, KISS, and YAGNI to reduce complexity and defects. Applying these guidelines ensures consistent practices, structured naming, and self-checks that streamline team collaboration.

How do I apply guard clauses to improve code readability and structure?

Guard clauses improve code structure by handling error conditions early and reducing nested logic. Applying pragmatic coding standards provides structured rules for functions and error handling to enforce these guardrails and reduce bugs.

Does this coding standard approach work for teams scaling across multiple projects?

Yes, these coding standards are useful for teams aiming to adopt a consistent, scalable coding discipline across projects. The guidelines provide guardrails and self-checks that developers can follow to streamline collaboration and reduce defects.

When should I use the YAGNI principle to avoid over-engineering during refactoring?

Use the YAGNI principle during refactoring to avoid over-engineering and unnecessary comments. Pragmatic coding standards ensure code remains concise, readable, and maintainable by enforcing only what is needed to reduce complexity.

How do I enforce SRP and DRY principles to reduce bugs and code complexity?

Enforce SRP and DRY principles by applying structured rules for naming, functions, and code structure. These pragmatic coding standards act as guardrails and self-checks to reduce bugs, eliminate duplication, and streamline collaboration.