agentsclimarketplace
Sign in

Zero tech debt

Skill susomejias/rembric/.agents/skills/zero-tech-debt

Rework a change as if the intended UX and architecture had existed from day one — deleting compatibility cruft, dead branches, and accidental complexity instead of patching around them. Use when refactoring, cleaning up after a feature lands, removing flags, collapsing legacy paths, or when the user says the code "should look like X from scratch".From its SKILL.md

Install
npx -y skills add susomejias/rembric --skill zero-tech-debt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, as published. Nobody here has run it

Zero Tech Debt

Reshape the change from the intended end state, not from the historical path that produced the current patch. The goal is the code that should exist now, not the smallest diff from what's there.

Steps

  1. Name the end state. In one or two sentences, describe the product surface and architecture as if you were building it today.

  2. Find real callers before preserving anything. Grep for actual usage of each mode, prop, wrapper, route alias, or fallback. If nothing references it, delete it — do not "improve" it.

  3. Reshape around the final surface. Prefer one clear component or flow over mode flags. Split only when there is an obvious boundary: state, layout, controls, or domain commands.

  4. Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming must not be duplicated across pages or buried inside view components.

  5. Verify the intended flow. Test the new behavior and the assumptions you deleted — anything that touched navigation, permissions, or persisted state.

Rules

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

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.