skills.rest
404-Profit-Not-Found
404-Profit-Not-FoundOFFICIAL
Explore all skills by this author →
WebsiteGitHub

clean-code

Enforce pragmatic coding standards for maintainable AI-assisted code across routine tasks.

Updated Dec 5, 2025
Search Tags:#DRY#KISS#refactor#coding-standards#naming#clean-code#SRP
One-click install
npx skills add https://github.com/404-Profit-Not-Found/neural-ticker-core --skill clean-code-404-profit-not-found
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/404-Profit-Not-Found/neural-ticker-core/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/404-Profit-Not-Found/neural-ticker-core --skill clean-code-404-profit-not-found

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards help software engineers write clean, maintainable code by applying SRP, DRY, KISS, YAGNI, and other proven guidelines.

Core Features & Use Cases

  • Core principles: SRP, DRY, KISS, YAGNI, Boy Scout Rule.
  • Naming Rules: Variables use clear, descriptive names; Functions are named with verbs; Booleans use question form; Constants use SCREAMING_SNAKE.
  • Function Rules: Small, One Thing, One Level of Abstraction, Few Args, No Side Effects.
  • Code Structure: Guard Clauses, Flat structures, Composition, Colocation.
  • AI Coding Style: Prioritize direct, actionable outputs when users request features or bug fixes.
  • Anti-Patterns (DON'T): Avoid over-commenting, avoid deep nesting, avoid over-abstracting.

Quick Start

Review a new or existing function and apply SRP, DRY, and KISS to refactor it. Rename ambiguous identifiers to improve readability. Remove unnecessary comments while preserving intent.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I apply clean code principles to refactor an existing function?▼

To refactor existing code with clean code principles, apply SRP, DRY, and KISS to enforce clear function boundaries, minimal side effects, and disciplined code structure for maintainable software.

What are the best naming conventions for writing maintainable code?▼

Maintainable code requires clear naming conventions: variables use descriptive names, functions use verbs, booleans use question form, and constants use SCREAMING_SNAKE to preserve intent and improve readability.

How do I structure functions to avoid deep nesting and side effects?▼

Function structure should use guard clauses, flat structures, and small single-purpose blocks to avoid deep nesting and side effects, ensuring one level of abstraction per function.

Does clean code work for small to medium codebases?▼

Yes, pragmatic coding standards are designed to apply to routine software tasks across small to medium codebases, enforcing clear boundaries and minimal side effects for AI-assisted code maintenance.

What clean code anti-patterns should I avoid during code review?▼

When reviewing code, avoid anti-patterns such as over-commenting, deep nesting, and over-abstracting, while ensuring functions do one thing, have few arguments, and contain no side effects.

Related Skills

Explore More Software Engineering Skills→
BenavidesMichaelBenavidesMichael

clean-code

Apply clean code principles to improve code quality in reviews, refactoring, and architecture.

Community
Advanced
rsmdtrsmdt
381

refactoring-methodology

Plan staged code refactorings with baseline tests and behavior preservation.

Community
Advanced
sebafermanellisebafermanelli
1

sfermanelli-clean-code

Clean up TypeScript/JavaScript naming, structure, formatting while preserving behavior.

Community
Intermediate
markhamsquareventuresmarkhamsquareventures

pint

Format Laravel PHP code automatically using Pint styling rules.

Official
Intermediate