Clean Code

Pragmatic coding standards that keep AI-written code simple, readable, and not over-engineered — clear names, small functions, no dead features. It makes our connector code easier for a non-coder to maintain later.

Cowork & Chat

How to use it

Ask Claude to write or tidy code with clean-code in mind and it applies the principles (SRP, DRY, KISS, YAGNI, good naming) and trims unnecessary complexity and comments. Works in Cowork/Chat — it reads and rewrites code you give it, no project run needed.

How to invoke / keep it on

Ask Claude to “keep it clean / simple” or name the skill; it loads automatically. Add it to a Project’s instructions so every build stays tidy by default.

20 powerful examples for Melinda Maria

Copy, tweak, make them yours. Just describe the task — Claude loads the skill automatically.

01"Clean up this connector tool Claude generated — simpler names, smaller functions, drop anything we don’t actually use — so I can still read it in six months."

02"Review this script for over-engineering and rewrite it to the simplest version that still works, explaining what you removed."

03"Rename the variables and functions in this Worker so the code reads in plain English without needing comments."

04"Apply clean-code standards to a file and give me a short before/after on what got clearer."

05"Break this giant 200-line function in the shipbob connector into a few small, well-named ones."

06"Remove the dead code and unused options from this connector tool we never ended up using."

07"Simplify the nested if-statements in this handler so the logic is obvious at a glance."

08"This script repeats the same block three times — factor it into one reusable function (DRY) cleanly."

09"Replace the cryptic abbreviations in this code with clear names a teammate could understand."

10"Tidy the JavaScript behind the hub’s time-saved calculator so it’s readable and not clever-for-clever’s-sake."

11"Tell me where this code is solving a problem we don’t actually have (YAGNI) and strip it back."

12"Rewrite these tangled comments away by making the code itself self-explanatory."

13"Standardize naming across this connector so similar things are named consistently."

14"Flatten this deeply nested data-handling code so it’s easier to follow."

15"Make this Python script’s structure match one-job-per-function so each piece is testable."

16"Review two connector files and align them to the same clean style so they’re consistent."

17"Simplify the configuration object in this Worker so only the settings we use remain."

18"Take this AI-generated tool and make it the smallest thing that still does the job, then explain the trims."

19"Clean up the error messages in a connector so they’re short, clear, and human."

20"Give me a quick “is this maintainable by a non-coder?” verdict on this file and the top three simplifications."

← Back to Engineering & Prompt-craft