team-art
Skill0 starsChanged 4 months agoMITView on GitHub
Use when working on art direction, visual identity, art bible, asset pipeline, illustration style, card art, or character art specifications. 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-audioSkill
- team-combatSkill
- team-economySkill
- team-infraSkill
- 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
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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/art.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
- Distinctive: line 35
When the execution chain says "dispatch specialist," use these agents:
≈ “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 Art
🌱 ShiningPlague-authored. No upstream version exists. Team-orchestrator skill for the art workstream.
Execution protocol: .claude/docs/templates/team-orchestrator.md
Workstream state: production/workstreams/art.md
Domain code: AR
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/art.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
When the execution chain says "dispatch specialist," use these agents:
| Step in chain | Agent to dispatch | What they do |
| Design: brainstorm / spec | art-director | Visual identity, style guide, asset standards |
| Design: GDD authoring | art-director | 8-section GDD per /design-system |
| Build: asset pipeline | technical-artist | Asset pipeline, shaders, rendering optimization |
| Build: implementation | gameplay-programmer | Illustration system code, asset loading |
| Content: art specs | art-director | Per-asset visual direction, reference sheets |
| Playtest: visual review | art-director | In-context visual validation |
| Review: concept visual | art-director | Gate AD-CONCEPT-VISUAL |
| Review: art bible | art-director | Gate AD-ART-BIBLE |
| Review: per-asset visual | art-director | Gate AD-VISUAL |
| Review: pillars check | creative-director | Gate CD-PILLARS |
Gates to Fire
| Gate | When | Director |
| AD-CONCEPT-VISUAL | Concept phase visual direction | art-director |
| AD-ART-BIBLE | Art bible validation | art-director |
| AD-VISUAL | Per-asset or per-system visual review | art-director |
| CD-PILLARS | If art changes affect aesthetic pillars | creative-director |
Templates
.claude/docs/templates/art-bible.md
Project-Specific Context
Fill in for your project (examples):
- Rendering approach (e.g. 2D illustrated panels, no 3D)
- Asset format constraints (e.g. preferred image formats; engine importer quirks such as Godot's WebP issues)
- Art production approach (e.g. AI-generated art directed by the designer)
- Art bible status (exists / Concept-phase gap)
- Style reference (genre + aesthetic keywords)
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.