agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/tech-debt/SKILL.md

tech-debt

Skill9 starsChanged 7 months agoMITView on GitHub

Identify and catalog technical debt with severity and estimated fix cost. Use for periodic debt audits or when deciding what to clean up next.

38 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use playtest-report, soak-test and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CoralGameSkill

    playtest-report

    Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

    Also in 12 projects that use this

  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 12 projects that use this

  • +5 more from lilangMax
  • +2 more from CoralGame

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Update production/session-state/tech-debt-tracker.md with totals.

    line 116

“Common” is measured: kept by at least 6 in 10 of the 31 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/tech-debt — Technical Debt Catalog

Delegate to: lead-programmer (with technical-director for architecture debt)

Steps

1. Search for Debt Markers

grep -rn "TODO\|FIXME\|HACK\|XXX\|DEPRECATED" src/ --include="*.lua" --include="*.luau"

2. Search for Known Anti-Patterns

# Deprecated APIs
grep -rn "[^.]wait(" src/ | grep -v "task.wait\|:Wait"

# Magic numbers in gameplay
grep -rn "[^a-zA-Z_][0-9]\{3,\}" src/ServerScriptService src/ServerStorage

# Stringy bools
grep -rn "== \"true\"\|== \"false\"" src/

3. Catalog Each Item

For each piece of debt:

  • Location: file:line
  • Category: Architecture / Code Quality / Performance / Security / Documentation
  • Description: What's wrong
  • Severity: Critical / High / Medium / Low
  • Estimated fix cost: hours or T-shirt size
  • Impact if ignored: What breaks or gets worse
  • Suggested fix approach: High-level plan

4. Score and Prioritize

Priority = Impact / Cost

High-impact, low-cost items go first.

5. Categorize

Architecture Debt

  • Coupling problems
  • Missing abstractions
  • Circular dependencies
  • Inconsistent patterns

Code Quality Debt

  • Duplicated code
  • Magic numbers
  • Missing type annotations
  • Commented-out code

Performance Debt

  • Inefficient algorithms
  • Missing caching
  • Unoptimized hot paths
  • Memory leaks

Security Debt

  • Missing validation
  • Client-trust assumptions
  • Deprecated security APIs
  • Missing rate limits

Documentation Debt

  • Missing GDD sections
  • Out-of-date comments
  • No architecture diagrams
  • Missing ADRs

6. Generate Report

# Tech Debt Inventory

**Date**: YYYY-MM-DD
**Total items**: X
**Estimated total cost**: Y hours

## By Category
- Architecture: X items
- Code Quality: X items
- Performance: X items
- Security: X items
- Documentation: X items

## Top 10 Priority Items
| # | Location | Issue | Category | Severity | Cost | Priority Score |
|---|----------|-------|----------|----------|------|----------------|
| 1 | src/combat/hit.lua:42 | No input validation | Security | High | 1h | 9/10 |
| 2 | ... | ... | ... | ... | ... | ... |

## Critical Items (fix ASAP)
1. [Description]

## Quick Wins (high impact, low cost)
1. [Description]

## Long-term Investments
1. [Description — worth doing but not urgent]

## Recommendations
- Allocate ~15% of each sprint to debt paydown
- Fix critical items this sprint
- Schedule quick wins for next sprint
- Plan dedicated refactor sprint for architecture items

7. Optionally: Write to Disk

On approval, save to production/tech-debt-<date>.md. Update production/session-state/tech-debt-tracker.md with totals.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.