Game Development
Design and ship browser-playable games from no-build Three.js prototypes to advanced architectures with workflows, budgets, and playtest loops.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ivangdavila/game-developmentSetup
On first use, read setup.md silently and align game scope, delivery target, and technical constraints before proposing implementation.
When to Use
Use this skill when users want to create playable games with agents, especially instant browser games with Three.js that run without a compile step. It also supports advanced projects with multiple systems, larger content pipelines, multiplayer plans, and live operations.
Architecture
Memory lives in ~/game-development/. See memory-template.md for setup and status fields.
~/game-development/
|-- memory.md # Current project state, scope, and delivery profile
|-- concept-briefs.md # Game concepts, target audience, and pillar ideas
|-- user-preferences.md # User taste, constraints, and style preferences
|-- system-decisions.md # Technical decisions and tradeoffs
|-- playtest-log.md # Session findings, issues, and balancing actions
|-- roadmap.md # Milestones and release checkpoints
`-- release-notes.md # What changed between iterations
Quick Reference
Use the smallest relevant file for the current task.
| Topic | File |
|---|---|
| Setup flow | setup.md |
| Memory template | memory-template.md |
| Genre and loop selection | game-types-and-loops.md |
| No-build browser path with Three.js | browser-threejs-fast-path.md |
| Project folder blueprints | project-structure-blueprints.md |
| Systems architecture and state design | systems-and-state.md |
| Asset/content pipeline and tooling | content-pipeline.md |
| Multiplayer and live operations | multiplayer-and-live-ops.md |
| QA, balancing, and launch checklist | qa-balance-launch.md |
Requirements
- Runtime for local preview scripts:
node - Optional tools for offline asset processing:
python3 - Browser target for quick iterations: Chrome, Edge, Safari, or Firefox
Prefer local and static workflows first. Move to backend dependencies only when the user explicitly needs multiplayer authority, persistence, or commerce.
Data Storage
Local notes stay under ~/game-development/ and should capture:
- the current game concept and loop assumptions
- the user preferences and non-negotiable constraints
- technical architecture choices with reasons
- playtest findings, balancing deltas, and release decisions
Keep notes concise and operational. Store decisions and outcomes, not long transcripts.
Core Rules
1. Lock the Delivery Profile First
Choose one profile before coding:
- Browser Instant: no-build HTML/CSS/JS delivery, fastest iteration, easiest sharing
- Browser Structured: TypeScript or bundler workflow with modular architecture
- Engine Path: Unity, Unreal, or Godot when editor tooling and content scale justify it
Do not mix profiles in one milestone unless the user asks for migration.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ivangdavila-game-development": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Animations
Create performant web animations with proper accessibility and timing.
Arduino
Develop Arduino projects avoiding common wiring, power, and code pitfalls.
Bulgarian
Write Bulgarian that sounds human. Not formal, not robotic, not AI-generated.
Arabic
Write Arabic that sounds human. Not formal, not robotic, not AI-generated.
Assistant
Manage tasks, communications, and scheduling with proactive and organized support.