team-infra
Skill0 starsChanged 4 months agoMITView on GitHub
Use when working on framework maintenance, hook extensions, skill authoring, editor tools, Python automation, CI pipeline, or Donchitos customization. Routes to the correct workflow pattern and executes step-by-step.
In this repository68 other files it gives its agents.
- adoptSkill
- architecture-decisionSkill
- architecture-reviewSkill
- art-bibleSkill
- asset-specSkill
- brainstormingSkill
- bug-reportSkill
- bug-triageSkill
- code-reviewSkill
- consistency-checkSkill
- content-auditSkill
- create-architectureSkill
- create-control-manifestSkill
- create-epicsSkill
- create-storiesSkill
- day-one-patchSkill
- design-reviewSkill
- design-systemSkill
- dev-storySkill
- dispatching-parallel-agentsSkill
- estimateSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- gate-checkSkill
- goal-add-minorSkill
- goal-checkSkill
- goal-setSkill
- godot-engineSkill
- helpSkill
- map-systemsSkill
- narrative-designerSkill
- project-stage-detectSkill
- propagate-design-changeSkill
- qa-planSkill
- quick-designSkill
- red-flag-scanSkill
- regression-suiteSkill
- retrospectiveSkill
- review-all-gddsSkill
- safety-pushSkill
- scope-checkSkill
- security-auditSkill
- session-closeSkill
- setup-engineSkill
- sprint-planSkill
- startSkill
- story-doneSkill
- story-readinessSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- team-artSkill
- team-audioSkill
- team-combatSkill
- team-economySkill
- team-levelSkill
- team-marketingSkill
- team-narrativeSkill
- team-polishSkill
- team-releaseSkill
- team-securitySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 29
Read production/workstreams/infrastructure.md — what's done, in-progress, next
- Distinctive: line 30
Ask or infer: which ACTIVITY?
- Very specific: line 31
Follow the matching execution chain from team-orchestrator.md
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Team Infra
🌱 ShiningPlague-authored. No upstream version exists. Team-orchestrator skill for the infrastructure workstream (framework customization + tooling).
Execution protocol: .claude/docs/templates/team-orchestrator.md
Workstream state: production/workstreams/infrastructure.md
Domain code: IF
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
- Read
production/workstreams/infrastructure.md— what's done, in-progress, next - Ask or infer: which ACTIVITY? (Design / Build / Content / Playtest / Review / Ship)
- Follow the matching execution chain from
team-orchestrator.md
Agent Routing — WHO to dispatch at each step
| Step in chain | Agent to dispatch | What they do |
| Design: tool spec | tools-programmer | Tool requirements, automation design |
| Design: CI/CD plan | devops-engineer | Build pipeline, deployment strategy |
| Build: Python automation | tools-programmer | Python scripts, pipeline tools, editor extensions |
| Build: Godot plugins | godot-gdscript-specialist | Godot addon/dock development |
| Build: CI/CD | devops-engineer | Build scripts, deployment automation |
| Build: code review | lead-programmer | Architecture compliance, ADR adherence |
| Playtest: tool testing | qa-tester | Hook/script/dock validation |
| Review: code review | lead-programmer | Gate TD-CODE-REVIEW |
Gates to Fire
| Gate | When | Director |
| TD-CODE-REVIEW | After infrastructure code ships | lead-programmer |
Templates
.claude/docs/templates/technical-design-document.md
Template Infrastructure Inventory
.claude/hooks/— session lifecycle hooks (session-start, skill-trigger-detect, pre/post-compact, validate-commit, etc.).claude/rules/— path-scoped rules.claude/skills/— the studio skill set (repo-canonical)tools/— Python automation shipped with the studio (consistency_check.py — the doc-stack gate; doc_stack_check.py — the path-promise guard; workflow_state_check.py — the flow-ledger check) plus whatever runners this project addsaddons/— engine editor docks/plugins, if the project uses them (e.g. a project dashboard, data-editor docks)server/— MCP server, if the project has one (rebuild whenserver/src/changes)- The framework lives at
.claude/docs/,.claude/agents/,.claude/skills/(all project-local, repo-canonical). Two-home rule: studio skills live in the repo's.claude/skills/; user level holds only personal skills — never create a user-level twin of a project skill (precedence would silently shadow it).
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
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.