Does this skill sacrifice performance for readability?

While readability is prioritized, performance is still a core goal; it follows a hierarchy where functionality comes first, followed by readability, and then performance.

How does this skill handle code comments?

It instructs Claude to only add comments that explain the 'why' behind business logic or non-obvious decisions, rather than describing what the code is doing.

What is the primary focus of the General Code Quality skill?

The skill prioritizes human readability and code maintainability (80%) over raw performance optimization (20%).

Can I use this skill with any programming language?

Yes, these are general-purpose development guidelines that apply to any language, from TypeScript to Python and beyond.

General Code Quality Guidelines

Name: General Code Quality Guidelines
Author: kevincrabbe

bykevincrabbe

개발자 도구

Enforces high-standard coding principles by prioritizing readability and meaningful documentation over raw performance.

소개

The General Code Quality Skill provides Claude with a foundational set of principles for any software project, emphasizing human-readable code and a specific focus on maintainability. It establishes a hierarchy of importance where functional correctness and readability take precedence, ensuring that code remains accessible to humans while staying performant. By guiding Claude to provide comments that explain 'why' rather than 'what,' this skill helps eliminate redundant documentation and reduces technical debt across your entire codebase.

주요 기능

0 GitHub stars
Discourages redundant or obvious code documentation
Prioritizes readability and maintainability using an 80/20 rule
Ensures functional correctness is the top project priority
Standardizes logic for complex workarounds and edge cases
Enforces meaningful 'why-not-what' commenting standards

사용 사례

Onboarding new team members to a project's core development philosophy
Standardizing coding style and documentation across a multi-developer repository
Refactoring legacy code to improve long-term maintainability

소개

주요 기능

0 GitHub stars
Discourages redundant or obvious code documentation
Prioritizes readability and maintainability using an 80/20 rule
Ensures functional correctness is the top project priority
Standardizes logic for complex workarounds and edge cases
Enforces meaningful 'why-not-what' commenting standards

사용 사례

Onboarding new team members to a project's core development philosophy
Standardizing coding style and documentation across a multi-developer repository
Refactoring legacy code to improve long-term maintainability