When reviewing or writing code, apply these guidelines:

Clean Code Guidelines

Constants Over Magic Numbers

When reviewing or writing code, apply these guidelines:

When reviewing or writing code, apply the principles above consistently. Focus on:

This expert skill consolidates 1 individual skills:

ALWAYS leave code cleaner than you found it — every change is an opportunity for progressive improvement; accumulating small improvements prevents large-scale refactors from becoming necessary.
NEVER use magic numbers — hard-coded values without context make code unreadable and unmaintainable; always extract to named constants with descriptive names that explain the purpose.
ALWAYS write self-documenting code first, then add comments only for "why" — comments explaining "what" the code does are redundant and become stale; reserve comments for non-obvious design decisions.
NEVER allow functions to do more than one thing — single responsibility is the strongest predictor of testability and maintainability; a function needing a "and" in its name should be split.
NEVER optimize prematurely — write clear, correct code first; profile to identify actual bottlenecks before optimizing; premature optimization produces complex code with unmeasured benefit.

Anti-Pattern	Why It Fails	Correct Approach
Magic numbers in logic	`if (status === 200)` is opaque; value could change	Extract to `const HTTP_OK = 200` with clear name
Comments explaining "what" not "why"	Code changes make comments stale and misleading	Write self-documenting code; comment only design rationale
God functions (>50 lines, multiple concerns)	Hard to test, debug, and modify independently	Extract single-purpose functions with clear names
Premature optimization	Adds complexity before proving a bottleneck exists	Profile first; only optimize measured hot paths
Duplicated code blocks	Bug fixes must be applied in N places	Extract to reusable function; DRY principle

Before starting:

cat .claude/context/memory/learnings.md

After completing: Record any new patterns or exceptions discovered.

ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.