Improve

Structured improvement pass grounded in what was observed during this session.

Principles (Always Active)

• Every suggestion must cite a specific observation — file path, error seen, pattern noticed, or behavior verified. "I saw X" beats "common practice suggests Y."
• Distinguish grounded suggestions (observed evidence) from speculative ones (general knowledge). Mark speculative suggestions explicitly.
• Prioritize by impact to the user, not by ease of description.
• Do not suggest improvements that would change public API contracts, auth boundaries, or data schemas without flagging as high-risk.
• Simplicity is a feature. Do not suggest adding complexity unless it prevents a concrete problem observed in this session.

When to Use

• User asks "knowing what you know now, what are some improvements?" or similar
• Before claiming done in a ralph loop (self-check)
• Before generating a handoff
• After completing a significant chunk of work
• When reviewing code that was just written or modified