Agent Skills › trycompai/crm › zero-tech-debt

zero-tech-debt

GitHub

指导以最终理想状态重构代码，删除兼容包袱和意外复杂度。通过识别真实调用者清理死代码，重塑产品表面，统一共享规则并验证新流程，旨在消除技术债务并保持代码整洁。

.agents/skills/zero-tech-debt/SKILL.md trycompai/crm

Trigger Scenarios

重构遗留代码清理兼容性逻辑优化架构设计

Install

npx skills add trycompai/crm --skill zero-tech-debt -g -y

More Options

Non-standard path

npx skills add https://github.com/trycompai/crm/tree/release/.agents/skills/zero-tech-debt -g -y

Use without installing

npx skills use trycompai/crm@zero-tech-debt

指定 Agent (Claude Code)

npx skills add trycompai/crm --skill zero-tech-debt -a claude-code -g -y

安装 repo 全部 skill

npx skills add trycompai/crm --all -g -y

预览 repo 内 skill

npx skills add trycompai/crm --list

SKILL.md

Frontmatter

{
    "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.",
    "user-invocable": true
}

Zero Tech Debt

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

Steps

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 clear 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.

Rules

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.