Agent skill
zero-debt
Zero Technical Debt skill for the ikigai project
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/zero-debt
SKILL.md
Zero Technical Debt
Description
Zero technical debt philosophy and work style principles for ikigai.
Details
Zero Technical Debt Principle
When you discover any problem, inconsistency, or standards violation:
- Fix it immediately - don't defer or document
- Fix it completely - address root cause, not symptoms
- Fix it systematically - search for similar issues elsewhere
Examples requiring immediate fixes:
- Missing assertions on function preconditions
- Inconsistent naming conventions
- Code violating error handling philosophy
- Test coverage gaps
- Code not following established patterns
When to ask first:
- Architectural changes
- Unclear which solution is correct
- Breaking changes to public APIs
- Uncertainty about project conventions
If you discover deficiencies in existing code while working nearby, fix them as part of your current work.
Work Style
CRITICAL: Do not make architectural, structural, or refactoring changes unless explicitly requested.
Acceptable without asking:
- Formatting with
make fmt - Running
make checkandmake lint - Minor code style consistency
When discussing improvements:
- Present options and trade-offs
- Wait for explicit approval before implementing
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?