- 📁 tools/
- 📄 android-build.md
- 📄 asset-gen.md
- 📄 asset-planner.md
This skill should be used when the user asks to "make a game", "build a game", "generate a game", or wants to generate or update a complete Godot game from a natural language description. --- # Game Generator — Orchestrator Generate and update Godot games from natural language. ## Capabilities Read each sub-file from `${CLAUDE_SKILL_DIR}/` when you reach its pipeline stage. | File | Purpose | When to read | |------|---------|--------------| | `visual-target.md` | Generate reference image | Pipeline start | | `decomposer.md` | Decompose into task DAG | After visual target | | `scaffold.md` | Architecture + skeleton | After decomposition | | `asset-planner.md` | Budget and plan assets | If budget provided | | `asset-gen.md` | Asset generation CLI ref | When generating assets | | `rembg.md` | Background removal | Only when an asset needs transparency removed | | `task-execution.md` | Task workflow + commands | Before first task | | `quirks.md` | Godot gotchas | Before writing code | | *(godot-api skill)* | GDScript syntax ref | When unsure about GDScript syntax | | `scene-generation.md` | Scene builders | Targets include .tscn | | `test-harness.md` | Verification scripts | Before test harness | | `capture.md` | Screenshot/video | Before capture | | `visual-qa.md` | Visual QA (forked skill) | After capture | | `android-build.md` | APK export | User requests Android | ## Pipeline ``` User request | +- Check if PLAN.md exists (resume check) | +- If yes: read PLAN.md, STRUCTURE.md, MEMORY.md -> skip to task execution | +- If no: continue with fresh pipeline below | +- Generate visual target -> reference.png + ASSETS.md (art direction only) +- Analyze risks + define verification criteria -> PLAN.md +- Design architecture -> STRUCTURE.md + project.godot + stubs | +- If budget provided (and no asset tables in ASSETS.md): | +- Plan and generate assets -> ASSETS.md + updated PLAN.md with asset assignments | +- Show user a concise plan summary (risk tasks if any, main buil
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.
Enforce correct form UI patterns when creating or modifying forms in packages/admin. Use when writing form fields, edit drawers, create modals, or any form-based UI in the admin package. Covers Form.Field pattern, labels, errors, hints, grids, submit guards, drawer/modal structure.
Search and recall relevant memories from past sessions. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge. Also use when you see '[memsearch] Memory available' hints.
- 📄 reference.md
- 📄 SKILL.md
Use when creating, modifying, or designing 2D virtual office scenes for the opensquad dashboard — room layouts, furniture placement, avatar integration, environment design, or any visual improvement. Also use when the dashboard looks empty, flat, lifeless, or lacks personality.
Performs initial binary triage by surveying memory layout, strings, imports/exports, and functions to quickly understand what a binary does and identify suspicious behavior. Use when first examining a binary, when user asks to triage/survey/analyze a program, or wants an overview before deeper reverse engineering.
Analyze codebase structure, dependencies, changes, cross-agent handoffs, and get code-aware intelligence. Use when user asks about project structure, where code is located, how files connect, what changed, how to resume work, before starting any coding task, when you need risk analysis and skill guidance, or when Codemap should tune project config before analysis.
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
Create new skills for FastClaw agents. Use when the user asks to create a skill, turn a workflow into a skill, or build reusable automation. Also use when discussing skill format, structure, or best practices.
Defines practical standards for implementation-focused coding agents. Use when creating or editing code, especially when reliability, clarity, and low-risk delivery are required.
Guides interactive module design via Q&A before writing. Use when the user wants to design a module, class, or feature together, or when they say "/spec-design".
