Enforce pragmatic coding standards for SRP, DRY, KISS, and YAGNI.
npx skills add https://github.com/skrymer/trading --skill clean-code-skrymer
Please help me install this Agent Skill. Skill: clean-code Source: https://github.com/skrymer/trading/tree/main/.claude/skills/clean-code Command: npx skills add https://github.com/skrymer/trading --skill clean-code-skrymer
Pragmatic coding standards that keep code clean, readable, and maintainable by guiding structure, naming, and minimal comments.
Follow the clean-code guidelines during code creation and reviews to ensure consistent, readable, and minimalistic code.
High-intent search queries and answers about installing and using this skill.
Pragmatic coding standards for code maintainability enforce concise rules for naming, structure, and minimal comments to ensure readability. They codify SRP, DRY, KISS, and YAGNI principles to guard against bloated implementations and reduce unnecessary boilerplate across software projects.
Apply clean code principles during code review by checking structure, naming, and minimal comments against SRP, DRY, KISS, and YAGNI rules. This ensures consistent patterns, improves long-term maintainability, and removes unnecessary complexity or anti-patterns in the implementation.
Use SRP, DRY, KISS, and YAGNI during refactoring to simplify and remove unnecessary complexity from existing code. Applying these default practices helps eliminate bloated implementations, ensures readability, and strips out unnecessary boilerplate across software projects.
Yes, you can use clean code rules to improve onboarding by applying consistent patterns and reduced boilerplate across software projects. Enforcing concise coding standards for naming and structure helps new developers read and understand the codebase faster.
The best way to prevent anti-patterns and bloated implementations is to enforce pragmatic coding standards that codify SRP, DRY, KISS, and YAGNI rules. This approach ensures code readability, consistency, and structural minimalism during code creation and reviews.
No, clean code does not require specific frameworks or dependencies to implement. These pragmatic coding standards are applied directly during code creation, reviews, and refactoring to enforce naming, structure, and minimal comments without relying on external components.
fsollaAnalyze code for smells and suggest specific refactoring steps.
t-stringsEnforce global code style guidelines when editing or generating code.
xenitV1Enforce pragmatic coding standards for concise, maintainable code.
fsollaImplements Clean Architecture pattern and Dependency Rule for modularizing business logic.
