clean-code

Enforces pragmatic coding standards for concise, direct, and maintainable code generation.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill clean-code-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill clean-code-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often suffers from over-engineering, excessive comments, deep nesting, and unnecessary abstractions. This Skill enforces pragmatic coding standards so generated code stays concise, readable, and free of bloat. ## Core Features & Use Cases - Coding Standards Enforcement: Applies SRP, DRY, KISS, YAGNI, and Boy Scout principles with concrete naming, function size, and structure rules. - Anti-Pattern Detection: Flags common mistakes like god functions, magic numbers, deep nesting, and unnecessary helper files, with direct fixes. - Dependency-Aware Editing: Requires checking imports and dependents before editing any file, preventing broken references across the codebase. - Verification Workflow: Maps agents to validation scripts (lint, type coverage, UX audit, security scan) with a mandatory read-summarize-ask output handling process. - Use Case: When asking an AI to add a feature or fix a bug, this Skill ensures the response is working code only—no tutorials, no obvious comments, and all dependent files updated in the same task. ## Quick Start Ask the AI to implement a feature or fix a bug and it will write concise, self-documenting code following clean code principles.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I make AI-generated code follow clean code principles?▼

Apply explicit rules for naming, function size, and structure: functions under 20 lines, max 3 arguments, guard clauses instead of nesting, and no obvious comments. This Skill encodes SRP, DRY, KISS, and YAGNI as enforceable constraints during code generation.

What coding standards should AI assistants follow when writing code?▼

Effective standards include single responsibility per function, intention-revealing names, early returns for edge cases, and avoiding premature abstraction. The Skill also bans over-commenting, one-line helper files, and explanatory tutorials in favor of direct working code.

How to prevent broken imports when AI edits shared files?▼

Before editing any file, check what imports it and what it imports, then update all dependent files in the same task. The Skill mandates this dependency check as a pre-edit step to avoid leaving broken references.

Does this coding standard work with linters and type checkers?▼

Yes, the Skill maps agents to verification scripts including a lint runner and type coverage checker. After completing work, the agent runs its designated script, summarizes errors and warnings, and asks before fixing.

When should I avoid creating helper functions and utility files?▼

Avoid helpers for one-liner logic, factories for two objects, and utils files holding a single function. Inline small code where it is used and only extract when duplication actually appears, following the YAGNI principle.