Roblox code maintenance refactor

Skill AshExplained/roblox-skills/roblox-code-maintenance-refactor

34 Claude Code AI skills for Roblox game development: ideas, Luau architecture, gameplay systems, UX, economy, monetization, security, QA, publishing, and live ops.

Install

npx -y skills add AshExplained/roblox-skills --skill roblox-code-maintenance-refactor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Maintain and refactor Roblox Luau code safely. Use for technical debt, dead code removal, module boundaries, naming cleanup, duplicate logic, dependency review, regression prevention, and long-term codebase health.

SKILL.md

2.5 KB, as published. Nobody here has run it

Roblox Code Maintenance Refactor

Goal

Improve code health without changing player-facing behavior accidentally.

Refactor Rules

Read before editing.
Keep changes scoped.
Preserve remote contracts unless intentionally migrating.
Avoid mixing behavior changes with cleanup.
Playtest after meaningful refactors.
Check console output.

Targets

Duplicated constants and reward formulas.
Large scripts with mixed responsibilities.
Client/server boundary confusion.
Dead remotes, stale UI paths, unused modules.
Repeated event connection patterns.
Unclear names around valuable state.
Magic numbers that should be balance tables.

Finding Deepening Opportunities

Beyond obvious cleanup, hunt for shallow modules to deepen — where the interface is nearly as complex as the implementation, so callers carry complexity that should be hidden.

Where does understanding one concept require bouncing between many tiny scripts?
Where were pure helpers extracted only for tidiness, but the real bugs live in how they're called (no locality)?
Where do client and server share a responsibility that leaks across the remote boundary?

Apply the deletion test to anything you suspect is shallow: if deleting it just moves complexity around, inline it; if deleting it would scatter the same complexity across many call sites, keep it and give it a small, stable interface named from the game's vocabulary. Present each opportunity as: files involved · the friction today · the proposed change · the benefit (locality + testability). Don't propose new indirection for a single implementation. See roblox-luau-architecture for the deep-module model.

MCP Workflow

Use script_grep to find duplication, old names, or call sites.
Read all affected scripts with script_read.
Make small edits with multi_edit.
Use start_stop_play to verify the relevant loop.
Check get_console_output.

Output

Return:

Refactor goal.
Behavior preserved.
Scripts changed.
Verification performed.
Follow-up debt items.

Verify no behavior changed with roblox-playtest-qa. For larger structural changes, design them in roblox-luau-architecture and slice them with roblox-to-issues so they land one safe step at a time.