agentleFS
Sign inStart free
ShiningPlagueShiningPlague/shiningplague-studio/skills/team-polish/SKILL.md

team-polish

Skill0 starsChanged 4 months agoMITView on GitHub

Use when working on performance optimization, visual polish, feel improvements, juice effects, or pre-release refinement. Routes to the correct workflow pattern and executes step-by-step. ShiningPlague-adopted: full implementation with performance-analyst + technical-artist + qa-tester dispatch and a project polish-context block.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 2 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.
  • 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

  • +2 more from lilangMax

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read production/workstreams/polish.md — what's done, in-progress, next

    line 31
  2. Distinctive:

    Ask or infer: which ACTIVITY?

    line 32
  3. Very specific:

    Follow the matching execution chain from team-orchestrator.md

    line 33
  4. Distinctive:

    Test/validation approach (e.g.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 13 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

Team Polish

🌱 ShiningPlague-adopted. Originally Donchitos (barebones stub); battle-tested on a shipped Godot project. Upstream was a pointer-only file; this version is the full implementation.

Execution protocol: .claude/docs/templates/team-orchestrator.md Workstream state: production/workstreams/polish.md Domain code: PL

If an artifact named here is absent: say so plainly in one line, skip that step, and continue. Never invent the file to satisfy a checklist, and never fail a close because an optional artifact was never created.

Step 0: Load State + Select Activity

  1. Read production/workstreams/polish.md — what's done, in-progress, next
  2. Ask or infer: which ACTIVITY? (Design / Build / Content / Playtest / Review / Ship)
  3. Follow the matching execution chain from team-orchestrator.md

Agent Routing — WHO to dispatch at each step

Step in chainAgent to dispatchWhat they do
Design: performance targetsperformance-analystFrame time budgets, memory targets, profiling plan
Design: visual targetstechnical-artistShader specs, VFX targets, visual optimization goals
Build: optimizationgameplay-programmerGDScript optimization, scene tree cleanup
Build: visual polishtechnical-artistShaders, VFX, visual optimization
Build: code qualitygodot-gdscript-specialistGDScript optimization patterns
Playtest: regressionqa-testerRegression after polish passes
Review: playtest feelcreative-directorGate CD-PLAYTEST
Review: code reviewlead-programmerGate TD-CODE-REVIEW
Review: test coverageqa-testerGate QL-TEST-COVERAGE

Gates to Fire

GateWhenDirector
CD-PLAYTESTPlayer experience validation after polishcreative-director
TD-CODE-REVIEWAfter optimization code shipslead-programmer
QL-TEST-COVERAGERegression coverage after polish changesqa-tester

Project-Specific Context

Fill in for your project (examples):

  • Code health baseline (e.g. current TODO/FIXME count in src/)
  • Test/validation approach (e.g. no test suite or linter — validation = run scene + watch console output)
  • Performance profile (e.g. UI/Control-node based, no 3D rendering)

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.

Check your setup, free