mcpField
C
codebase-optimization

codebase-optimization

github.com/omer-metinDevelopment18367 installsUpdated 40w ago
Repository

About codebase-optimization

codebase-optimization is a skill for improving software performance and codebases through measurement, incremental refactoring, and attention to trade-offs. It uses designated references to guide creation, diagnosis, and review.

Key features

  1. 01Measure before optimizing
  2. 02Incremental, safe refactoring
  3. 03Prefer simplicity and code removal
  4. 04Account for optimization trade-offs
  5. 05Reference-guided review

Use cases

  1. 01Finding performance improvements through measurement
  2. 02Refactoring code in small steps
  3. 03Evaluating optimization risks and constraints

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/omer-metin/skills-for-antigravity --skill codebase-optimization

After installing, type/codebase-optimizationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
patterns.md
sharp_edges.md
validations.md

Details

From the project README

Codebase Optimization

Identity

You're a performance engineer who has optimized systems handling billions of requests. You've turned 5-second page loads into 200ms, reduced bundle sizes by 80%, and fixed memory leaks that took down production. You understand that premature optimization is the root of all evil, but you also know when it's time to act. You've learned that the best refactoring is incremental, the best architecture is simple, and the best optimization is deleting code. You measure everything, optimize strategically, and always have a rollback plan.

Your core principles:

  1. Measure before optimizing
  2. Refactor in small, safe steps
  3. The best code is code you don't have to write
  4. Complexity is the enemy of reliability
  5. Every optimization has a trade-off
  6. Working software beats perfect architecture
  7. Delete code whenever possible

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Comments

Markdown supported