Files

T

jpmschweitzerandClaude Opus 4.6 7158ae9cf5 feat(meta): add whatsinagame multi-agent team starter kit

Claude-native starter kit that bootstraps multi-agent team
infrastructure for any project. Clone once, install as a global
skill, run /kit-install in any project directory.

Includes:
- 3-tier profile system (minimal/standard/full: 3-12 agents)
- 16 agent archetype templates with personality spectrum
- 18 skill templates using domain-action naming convention
- Stakeholder persona panel for workshops and PR reviews
- SQLite ticketing DB with CLI tools (config-based DB paths)
- Decision tracking, sprint lifecycle, workshop orchestration
- Multi-git-host support (GitHub, Gitea, GitLab)
- /kit-update skill for syncing with source repo evolution
- Naming theme support for agent identity/flavor
- Smoke tests for all three profile tiers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-18 02:22:30 +01:00

4.6 KiB

Raw Blame History

Reviewer Profiles by Branch Type

Use model: sonnet for all reviewers — sufficient for review, saves cost.

Code reviews (`server`, `client`, `backend`, `frontend`, `ci`)

QA Engineer (Code Quality)

subagent_type: qa-engineer (or your project's QA agent), model: sonnet
Prompt: Include source code and commit log. Ask the QA engineer to review for:
- Correctness and bug risks
- Error handling gaps
- Test coverage (are new features tested?)
- Code style and clarity
- Security concerns (OWASP top 10, injection risks)
- Performance issues

Architect (Architectural Consistency)

subagent_type: architect (or your project's architecture agent), model: sonnet
Prompt: Include source code and commit log. Tell the architect to read the relevant decisions/*.md files first, then review for:
- Architectural consistency with project decisions
- API/interface design quality
- Dependency and coupling concerns
- Scalability implications
- Whether the change respects project baselines and constraints
The architect can typically read files directly from the branch using git show origin/<branch>:<path>

Content reviews (`content`, `copy`, `docs`)

QA Engineer (QA)

subagent_type: qa-engineer, model: sonnet
Prompt: Include the changed files and commit log. Ask the QA engineer to review for:
- Formatting consistency (markdown, file naming, frontmatter)
- Broken references or links
- Spelling and grammar
- File organization and structure
- Missing or orphaned files

Content Author (Voice & Tone) — may lack Bash access

subagent_type: content-author (or your project's writing agent), model: sonnet
If this agent cannot read from branches, paste file contents and decision files directly into the prompt.
Prompt: Include full text of changed files, commit log, and relevant decisions/*.md content. Ask the content author to review for:
- Narrative quality and voice consistency
- Whether dialogue and text feel authentic to the project's tone
- Consequences and stakes — do choices carry weight?
- Emotional resonance — does the text make you feel something?

Domain Expert (Consistency) — may lack Bash access

subagent_type: domain-expert (or your project's world/lore agent), model: sonnet
If this agent cannot read from branches, paste file contents and decision files directly into the prompt.
Prompt: Include full text of changed files, commit log, and relevant decisions/*.md content. Ask the domain expert to review for:
- Factual accuracy — do details match established lore/setting?
- Internal consistency across files
- IP originality — nothing should read as a copy from another franchise
- Domain-specific details match the project's established canon

Visual reviews (`visual`, `design`, `art`)

QA Engineer (QA)

subagent_type: qa-engineer, model: sonnet
Prompt: Include the changed files and commit log. Ask the QA engineer to review for:
- File format and naming conventions
- Asset organization and directory structure
- Missing or broken references in scene/resource files
- Import settings consistency

Visual Designer (Art Direction)

subagent_type: visual-designer (or your project's art agent), model: sonnet
Prompt: Include the changed files and commit log. Tell the designer to read the style guide and relevant design docs first, then review for:
- Visual consistency with the established style guide
- Color palette adherence
- UI pattern consistency
- Whether assets scale gracefully across resolutions
- Mood and tone alignment with the project's aesthetic

Audio reviews (`audio`, `sound`)

QA Engineer (QA)

subagent_type: qa-engineer, model: sonnet
Prompt: Include the changed files and commit log. Ask the QA engineer to review for:
- File format and naming conventions
- Audio asset organization and directory structure
- Missing or broken references
- Import/bus configuration consistency

Audio Designer (Player Experience) — may lack Bash access

subagent_type: audio-designer (or your project's audio agent), model: sonnet
If this agent cannot read from branches, paste file contents directly into the prompt.
Prompt: Include full text of changed files and commit log. Ask the audio designer to review for:
- Emotional impact — does the audio enhance the moment?
- Atmosphere and tone — does it fit the project's setting?
- Player feedback clarity — can the user tell what just happened?
- Pacing — do sounds support or fight the interaction rhythm?
- Memorable moments — will users remember these audio cues?

4.6 KiB Raw Blame History

Reviewer Profiles by Branch Type

Code reviews (server, client, backend, frontend, ci)

Content reviews (content, copy, docs)

Visual reviews (visual, design, art)

Audio reviews (audio, sound)

4.6 KiB

Raw Blame History

Code reviews (`server`, `client`, `backend`, `frontend`, `ci`)

Content reviews (`content`, `copy`, `docs`)

Visual reviews (`visual`, `design`, `art`)

Audio reviews (`audio`, `sound`)