zero-tech-debt

Refactors code changes toward the intended end-state architecture by deleting dead compatibility paths.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill zero-tech-debt-harivansh-afk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zero-tech-debt
Source: https://github.com/harivansh-afk/loom-index-e2e/tree/main/skills/zero-tech-debt
Command: npx skills add https://github.com/harivansh-afk/loom-index-e2e --skill zero-tech-debt-harivansh-afk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Patches often accumulate compatibility cruft, mode flags, and fallback paths that reflect the historical path of development rather than the intended final design. This Skill reshapes a change as if the target UX and architecture existed from day one, removing accidental complexity and dead code. ## Core Features & Use Cases - End-State Reframing: States the intended end state first, then reshapes the patch around the final product surface instead of the smallest diff from the old shape. - Dead Path Deletion: Searches for real callers of modes, props, wrappers, route aliases, and fallbacks, and deletes anything with no current caller. - Consolidation of Shared Rules: Moves feature flags, permissions, route gating, URL state, and command naming into one place instead of duplicating them across pages or views. - Use Case: After shipping a feature behind a flag with a legacy fallback route, use this Skill to remove the old path, collapse mode-flagged components into one clean flow, and verify navigation and permissions still work. ## Quick Start Rework this patch with zero tech debt, deleting the legacy fallback and reshaping it around the intended final UX.

Frequently Asked Questions about zero-tech-debt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor a patch to remove technical debt?▼

State the intended end state in one or two sentences, then reshape the change around that final product surface. Search for real callers of every mode, prop, wrapper, and fallback, and delete anything with no current caller instead of improving it.

How to clean up feature flags after a rollout?▼

Verify the flag has no remaining callers, then delete the flag and the legacy branch entirely. Move any surviving shared rules such as permissions or route gating to one central place rather than leaving them duplicated across pages.

When should I delete a compatibility path instead of keeping it?▼

Delete a compatibility path when a caller search shows no current code depends on it. The Skill's rule is to remove dead compatibility paths rather than maintain or improve them, keeping the codebase aligned with the intended end state.

What are the limits of a zero tech debt refactor?▼

The refactor stays scoped to what makes the final shape coherent and does not invent a generic framework for a single feature. It optimizes for the code that should exist, not the smallest possible diff from the old shape.

How do I verify a refactor that removed legacy routes?▼

Test the new behavior plus any deleted assumptions that affect navigation, permissions, or persisted state. Confirm the intended flow works end to end after the old route aliases and fallbacks are removed.