A coordinated workflow for refining an existing Roblox game feature after it already works. It reviews rough edges across gameplay, visuals, interface, audio, and user experience.

Use it to review playtest issues, improve effects and interface animation, add sound feedback, and tune controls, timing, and gameplay values.

It helps turn a functional feature into a clearer and more polished experience by finding friction and improving feedback.

team-polish — Skill for Claude Code by CodePhobiia

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add CodePhobiia/claude-roblox-game-studio --skill team-polish

Clone the repo

git clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/team-polish/github.svg)](https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-polish)

Your own site

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-polish"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/team-polish/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-polish"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/team-polish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 899 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.00899
Opus 5	$0.00023	$0.00449
Sonnet 5	$0.00009	$0.00180
Haiku 4.5	$0.00005	$0.00090

Measured 9d ago against content hash 43d4b6ec89e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

team-polish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/team-polish/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/team-polish — Polish Pass Team

Purpose

Polish turns "it works" into "it feels great." This skill orchestrates a polish pass across multiple specialists.

When to Use

Feature is functional but feels rough
Before a demo or launch
After external playtest feedback
As part of a dedicated polish sprint

Orchestration Flow

Phase 1: Identify Rough Edges

qa-tester: Play through the feature; note every moment that feels off
ux-designer: Review the flow for friction points
game-designer: Review for fun factor / moment-to-moment engagement

Present a consolidated list to user for prioritization.

Phase 2: Visual Polish

technical-artist: Add juice (particle effects, camera shake, screen flashes)
art-director: Review visual cohesion with game style
ui-programmer: UI animation polish (tweens, fades, bounces)

Phase 3: Audio Polish

sound-designer: Add missing sound effects (every action should have feedback)
audio-director: Review audio mix (not too loud, not too quiet, ducking correctly)

Phase 4: Feel Polish

luau-gameplay-programmer: Adjust timing, animation weights, input responsiveness
game-designer: Tune numbers (damage multipliers, cooldowns, speeds)

Phase 5: Validation

qa-tester: Replay and confirm improvements
performance-analyst: Verify polish didn't tank performance

Steps

1. Scope the Polish

Ask:

"Which feature needs polish?"
"What specific concerns have you or players mentioned?"
"How much time do we have for polish?"

2. Run Rough Edge Audit

qa-tester plays the feature with "feel detector" mode: every moment that feels wrong is noted
Categorize issues: visual, audio, feel, flow

3. Prioritize

Some fixes are 10-minute wins (add a particle, add a sound)
Some are bigger (rework the UI flow)
User picks which to address first

4. Polish Phase

Each specialist addresses their items
Each change goes through Question → Options → Decision → Draft → Approval
Small changes can batch; big changes reviewed individually

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 112 lines · 46 tokens per session scan A 43d4b6ec89e4

Subscribe to this mod's changes

team-polish is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 899 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Design and UX Game development

roblox-ui

Build production Roblox interfaces with ScreenGui/PlayerGui lifecycle, responsive UDim2 layouts, safe insets, reusable editable Instances, cross-device input and selection, restrained motion, cleanup, and multi-viewport verification. Use for Roblox HUDs, inventories, shops, settings, ability bars, ScrollingFrames…

gamedev-skills/awesome-gamedev-agent-skills · 101 tokens

game-ui-ux

Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected…

gamedev-skills/awesome-gamedev-agent-skills · 123 tokens

ux-design

Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.

Donchitos/Claude-Code-Game-Studios · 61 tokens

team-polish