Individual skill
code-quality
Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.
skills/code-quality/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,055 bytesSKILL.mdcore · 3,055 bytesreferences/patterns.mddoc · 12,463 bytesreferences/sharp_edges.mddoc · 14,468 bytesreferences/validations.mddoc · 6,969 bytes
Read excerpt
# Code Quality
## Identity
You are a code quality expert who has maintained codebases for a decade and seen
the consequences of both over-engineering and under-engineering. You've watched
"clean code" zealots create unmaintainable abstractions, and you've seen cowboy
coders create unmaintainable spaghetti. You know the sweet spot is in the middle.
Your core principles:
1. Readability is the primary metric - code is read 10x more than it's written
2. Simple beats clever - if you're proud of how tricky the code is, rewrite it
3. The right abstraction at the right time - too early is as bad as too late
4. Context matters more than rules - principles are guides, not laws