name	zero-tech-debt
description	Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Use when the user asks for zero tech debt, no legacy path, a clean end-state refactor, or wants a patch reshaped around the intended final product surface instead of the historical path that produced it.

Zero Tech Debt

Rework the change from the intended end state, not from the historical path that produced the current patch.

State the intended end state in one or two sentences.
Search for real callers before preserving compatibility. If a mode, prop, wrapper, route alias, or fallback has no current caller, delete it.
Reshape around the final product surface. Prefer one clean component or flow over mode flags. Split only when it creates an obvious boundary such as state, layout, controls, or domain commands.
Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming should not be duplicated across pages or hidden in view components.
Verify the intended flow. Test the new behavior and any deleted assumptions that affect navigation, permissions, or persisted state.

Optimize for the code that should exist, not the smallest diff from the old shape.
Delete dead compatibility paths instead of making them better.
Do not invent a generic framework for one feature.
Keep the refactor scoped to what makes the final shape coherent.
Prefer names that describe product intent over implementation history.

name	zero-tech-debt
description	Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Use when the user asks for zero tech debt, no legacy path, a clean end-state refactor, or wants a patch reshaped around the intended final product surface instead of the historical path that produced it.

Rework the change from the intended end state, not from the historical path that produced the current patch.

State the intended end state in one or two sentences.
Search for real callers before preserving compatibility. If a mode, prop, wrapper, route alias, or fallback has no current caller, delete it.
Reshape around the final product surface. Prefer one clean component or flow over mode flags. Split only when it creates an obvious boundary such as state, layout, controls, or domain commands.
Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming should not be duplicated across pages or hidden in view components.
Verify the intended flow. Test the new behavior and any deleted assumptions that affect navigation, permissions, or persisted state.

Optimize for the code that should exist, not the smallest diff from the old shape.
Delete dead compatibility paths instead of making them better.
Do not invent a generic framework for one feature.
Keep the refactor scoped to what makes the final shape coherent.
Prefer names that describe product intent over implementation history.

zero-tech-debt