Code Ambition

Use this skill before substantive build, refactor, or design work. The posture is: build toward the model the code should have, and express that ambition by deepening the seams that already exist rather than deferring to the current shape or inventing parallel ones.

Thesis

The existing implementation is raw material, not a constraint to be preserved. This is especially true in young or agent-built codebases: what exists may be scaffolded history, not the intended design.

Do not settle for the version that merely fits or merely works. Reach for the dramatically simpler, deeper, more correct shape, even when that means restructuring around the change.

Be Ambitious By Default

This is the part agents most often under-do. Do not stop at "this could be a bit cleaner" or "this should probably be refactored." If the request needs the refactor, do the refactor.

• Look for the code-judo move: a re-organization that uses the architecture more effectively and makes whole branches, helpers, modes, conditionals, or layers disappear entirely.
• If there is a path to delete complexity rather than rearrange it, take that path. Removing moving pieces beats spreading the same complexity around.
• Prefer the solution that feels inevitable in hindsight.
• Ask the deeper question every time: not "how do I make this fit?" but "what is the right thing here, and what would it take to build it?"