zero-tech-debt
SolidRewrite an accreted patch into its intended end-state by removing unused compatibility layers, flags, fallbacks, and wrappers. Triggers "zero tech debt", "rewrite as if from scratch", "delete the compat layer", "kill the legacy path", "too many flags".
Install
Quality Score: 87/100
Skill Content
Details
- Author
- darkroomengineering
- Repository
- darkroomengineering/cc-settings
- Created
- 8 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
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".
refactor-skills
Reviews the markdown and template files changed in the current session and tightens them for agent performance — sharper trigger descriptions, progressive disclosure, imperative voice, one-claim-per-bullet, fewer redundant rules — while preserving every workflow step, constraint, and trigger condition. Use when the user has just edited one or more skill or prompt files (`SKILL.md`, `references/*.md`, `recipes/*.md`, agent templates, slash-command prompts) and wants a tightening pass before committing, or invokes "/refactor-skills", "refactor this skill", "tighten the skill", "polish SKILL.md", "make this skill leaner". Behaviour-preserving only — never use this to add features, expand scope, or remove rules.
refactor
Behavior-preserving restructuring of code NOT in your current diff — extract modules, rename across files, pay down tech debt. For just-changed code use /zero-tech-debt. Triggers "refactor X", "restructure", "extract Y from Z".