mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
e289ce906f
* Add context resilience: file-backed state, incremental writing, auto-recovery Prevents "prompt too long" crashes from killing sessions by persisting work to disk incrementally instead of relying on conversation memory. Changes: - pre-compact.sh: dumps session state before context compression - session-start.sh: detects active.md for crash recovery - session-stop.sh: archives and clears active.md on clean shutdown - context-management.md: file-backed state as primary strategy - 9 agents updated with incremental section writing protocol (game-designer, systems-designer, economy-designer, narrative-director, level-designer, world-builder, writer, art-director, audio-director) - CLAUDE.md: trimmed redundant imports (10 → 5) to reduce token overhead - design-docs.md rule: enforces incremental writing pattern - .gitignore: excludes ephemeral session state files - directory-structure.md: documents session-state/ and session-logs/ - COLLABORATIVE-DESIGN-PRINCIPLE.md: documents incremental writing pattern Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add AskUserQuestion integration across collaborative protocols Explicitly reference the AskUserQuestion tool in all collaborative agent definitions, protocol templates, team orchestrator skills, and the master principle doc. Introduces the Explain-then-Capture pattern: agents write full expert analysis in conversation, then call AskUserQuestion with concise labels to capture decisions via structured UI. 26 files updated: - 3 protocol templates (design, leadership, implementation) - 14 agent definitions (10 design + 3 leadership + writer) - 8 orchestrator skills (brainstorm + 7 team-*) - 1 master principle doc (COLLABORATIVE-DESIGN-PRINCIPLE.md) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Add /design-systems skill: concept-to-GDD decomposition workflow Bridges the gap between game concept and per-system design documents. Professional studios use systems enumeration + dependency sorting between concept and feature docs — skipping this step is one of the most expensive mistakes (systems discovered during production cost 5-10x more to add). New files: - .claude/skills/design-systems/SKILL.md — 7-phase orchestration skill (enumerate systems, map dependencies, assign priorities, write GDDs) - .claude/docs/templates/systems-index.md — master tracking template Flow integration (7 existing skills updated): - brainstorm, start, setup-engine, design-review, gate-check, project-stage-detect, game-concept template all reference /design-systems at the appropriate workflow touchpoints Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix cross-platform bugs, add missing tool permissions, and update docs for v0.2.0 Hooks: fix \s → [[:space:]] in grep -E fallbacks (3 files), fix detect-gaps.sh empty-variable bug, fix log-agent.sh field name (agent_name → agent_type), harden validate-push.sh with explicit $MATCHED_BRANCH, convert for-in loops to while-read for space-safe iteration, add POSIX head -n syntax, increase PreCompact timeout, widen session-stop log window. Skills: add AskUserQuestion to 10 skills and TodoWrite to 8 multi-phase skills. Fix project-stage-detect template/output paths, tech-artist → technical-artist. Docs: add /design-systems to all references (README, quick-start, workflow guide, skills-reference), update skill count 35 → 36, remove stale AI artifacts from COLLABORATIVE-DESIGN-PRINCIPLE.md, add AskUserQuestion note to examples README. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
71 lines
3.5 KiB
Markdown
71 lines
3.5 KiB
Markdown
---
|
|
name: team-ui
|
|
description: "Orchestrate the UI team: coordinates ux-designer, ui-programmer, and art-director to design, implement, and polish a user interface feature from wireframe to final."
|
|
argument-hint: "[UI feature description]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task, AskUserQuestion, TodoWrite
|
|
---
|
|
When this skill is invoked, orchestrate the UI team through a structured pipeline.
|
|
|
|
**Decision Points:** At each phase transition, use `AskUserQuestion` to present
|
|
the user with the subagent's proposals as selectable options. Write the agent's
|
|
full analysis in conversation, then capture the decision with concise labels.
|
|
The user must approve before moving to the next phase.
|
|
|
|
## Team Composition
|
|
- **ux-designer** — User flows, wireframes, accessibility, input handling
|
|
- **ui-programmer** — UI framework, screens, widgets, data binding, implementation
|
|
- **art-director** — Visual style, layout polish, consistency with art bible
|
|
|
|
## How to Delegate
|
|
|
|
Use the Task tool to spawn each team member as a subagent:
|
|
- `subagent_type: ux-designer` — User flows, wireframes, accessibility, input handling
|
|
- `subagent_type: ui-programmer` — UI framework, screens, widgets, data binding
|
|
- `subagent_type: art-director` — Visual style, layout polish, art bible consistency
|
|
|
|
Always provide full context in each agent's prompt (feature requirements, existing UI patterns, platform targets). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 4 review agents can run simultaneously).
|
|
|
|
## Pipeline
|
|
|
|
### Phase 1: UX Design
|
|
Delegate to **ux-designer**:
|
|
- Define the user flow for this feature (entry points, states, exit points)
|
|
- Create wireframes for each screen/state
|
|
- Specify interaction patterns: how does keyboard/mouse AND gamepad navigate this?
|
|
- Define accessibility requirements: text sizes, contrast, colorblind safety
|
|
- Identify data the UI needs to display (what game state does it read?)
|
|
- Output: UX spec with wireframes and interaction map
|
|
|
|
### Phase 2: Visual Design
|
|
Delegate to **art-director**:
|
|
- Review wireframes against the art bible
|
|
- Define visual treatment: colors, typography, spacing, animations
|
|
- Specify asset requirements (icons, backgrounds, decorative elements)
|
|
- Ensure consistency with existing UI screens
|
|
- Output: visual design spec with style notes
|
|
|
|
### Phase 3: Implementation
|
|
Delegate to **ui-programmer**:
|
|
- Implement the UI following the UX spec and visual design
|
|
- Ensure UI NEVER owns or modifies game state — display only, events for actions
|
|
- All text through localization system — no hardcoded strings
|
|
- Support both input methods (keyboard/mouse + gamepad)
|
|
- Implement accessibility features (text scaling, colorblind mode support)
|
|
- Wire up data binding to game state
|
|
- Output: implemented UI feature
|
|
|
|
### Phase 4: Review (parallel)
|
|
Delegate in parallel:
|
|
- **ux-designer**: Verify implementation matches wireframes and interaction spec. Test keyboard-only and gamepad-only navigation. Check accessibility.
|
|
- **art-director**: Verify visual consistency with art bible. Check at minimum and maximum supported resolutions.
|
|
|
|
### Phase 5: Polish
|
|
- Address review feedback
|
|
- Verify animations are skippable and respect motion preferences
|
|
- Confirm UI sounds trigger through audio event system
|
|
- Test at all supported resolutions and aspect ratios
|
|
|
|
## Output
|
|
A summary report covering: UX spec status, visual design status, implementation status, accessibility compliance, input method support, and any outstanding issues.
|