메뉴
Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Write interactive WebGL/canvas visualizations for Jupyter notebooks (.ipynb) opened inside Obsidian by the jupyter-uv plugin. A diagram is a small ES module that imports a shared three.js and is rendered with the `lab.viz` helper as a srcdoc iframe. Use when adding or porting an interactive viz into a notebook, writing notebook-local `notebooks/<notebook-name>/<diagram-name>.js` modules, or calling `lab.viz.show` / `lab.viz.scene`.
Apply the suckless philosophy — simplicity, clarity, frugality — when designing, writing, reviewing, or refactoring software in any language. Use when the goal is minimal, bloat-free tools where removed code is progress.
ALWAYS load before writing, editing, explicitly reviewing, or refactoring code in any language. Do not load for read-only file inspection, opening, navigation, or neutral summarization unless the user asks for review, design, safety, performance, or developer-experience feedback. Applies TigerBeetle TigerStyle principles for simplicity, safety, performance, and developer experience.
ALWAYS load before writing, editing, renaming, designing, or explicitly reviewing Python (.py) code. Do not load for read-only file inspection, opening, navigation, or neutral summarization unless the user asks for style, API, design, or code-review feedback. Covers general Python style, API shape, naming/import conventions, sum types, casting, assertions, formatting, and code review checks. Use python-modern separately for language feature/changelog guidance.
ALWAYS load before writing, editing, or creating any Python (.py) code — do not write Python without loading it first. Also use when explicitly reviewing Python language-version choices or modernization opportunities. Do not load for read-only file inspection, opening, navigation, or neutral summarization. Modern syntax preferences for 3.8-3.14 (walrus, pattern matching, exception groups, TaskGroup, generic syntax, type aliases, t-strings).
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like smart caveman while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "less tokens", "be brief", or when token efficiency is requested.
| name | tech-debt |
| description | Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog. |
Systematically identify, categorize, and prioritize technical debt.
| Type | Examples | Risk |
|---|---|---|
| Code debt | Duplicated logic, poor abstractions, magic numbers | Bugs, slow development |
| Architecture debt | Monolith that should be split, wrong data store | Scaling limits |
| Test debt | Low coverage, flaky tests, missing integration tests | Regressions ship |
| Dependency debt | Outdated libraries, unmaintained dependencies | Security vulns |
| Documentation debt | Missing runbooks, outdated READMEs, tribal knowledge | Onboarding pain |
| Infrastructure debt | Manual deploys, no monitoring, no IaC | Incidents, slow recovery |
Score each item on:
Priority = (Impact + Risk) x (6 - Effort)
Produce a prioritized list with estimated effort, business justification for each item, and a phased remediation plan that can be done alongside feature work.
