html-game-parallel-builder
/html-game-parallel-builder
Use when the user requests a parallel multi-agent build or major workstream for a modular TypeScript browser game, including integrated serving, smoke testing, export, or Pages delivery.
- Author
- vosslab ↗
- Repository
- vosslab-skills ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 27
- Scripts
- 8
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 8 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: templates/build_github_pages.sh, templates/check_codebase.sh, templates/devel/setup_playwright.sh, templates/devel/setup_typescript.sh, templates/dist_clean.sh, templates/eslint.config.js, templates/export_single_file.sh, templates/run_web_server.sh
What it does and when to use it
Use when the user requests a parallel multi-agent build or major workstream for a modular TypeScript browser game, including integrated serving, smoke testing, export, or Pages delivery.
Original author description
Use when the user requests a parallel multi-agent build or major workstream for a modular TypeScript browser game, including integrated serving, smoke testing, export, or Pages delivery.
How it works
- Required routing
- Build and release identity
- Control loop
- Load-bearing safeguards
SKILL.md preview
--- name: html-game-parallel-builder description: Use when the user requests a parallel multi-agent build or major workstream for a modular TypeScript browser game, including integrated serving, smoke testing, export, or Pages delivery. --- # Web Game Parallel Build Use for a time-pressured, modular TypeScript browser-game build where multiple agents must author interacting modules and the live local preview is the immediate target. It is not for a simple edit, server application, heavyweight multi-page build, or work where one agent can finish promptly. Parallelism cuts wall time only when contracts and integration gates remain intact. ## Required routing Before contracts or dispatch, invoke `game-design-expert` to establish the shared design brief: intended experience, core actions and decisions, surprise and progression, visual identity and visible consequence, cross-module dependencies, and evidence. Keep that concise brief in the project's existing planning documentation. It is the creative source for contracts, assignments, and integrated review. Also invoke `delegate-manager-to-subagents` for ownership and evidence discipline, `parallel-plan` for lane sizing and ownership splits, and `typescript-engineer` for all type design. Read the TypeScript skill's game type, modular-type, strict-mode, and opaque-type references before defining cross-module contracts. This skill owns browser-game orchestration, not TypeScript design rules. Read [references/BATCH_DISPATCH.md](references/BATCH_DISPATCH.md) before file assignment. It owns the A0-E layout, batch-specific prompt requirements, exclusive file ownership, and the type-design pause-and-route procedure. Use [templates/agent_prompt_template.md](templates/agent_prompt_template.md) for every coding assignment. ## Build and release identity Default to a GitHub Pages-ready build in `dist/`. Use a portable single-file export in `output_single_file/` only when explicitly requested. Keep the three paths separate: `run_web_server.sh` serves the live preview, `build_github_pages.sh` produces the Pages build, and `export_single_file.sh` produces the optional portable artifact. Read [references/BUILD_ARTIFACTS.md](references/BUILD_ARTIFACTS.md) for ownership, starter-template parity, copied artifacts, and output constraints. Read [references/GITHUB_PAGES_DEPLOY.md](references/GITHUB_PAGES_DEPLOY.md) only when configuring or diagnosing deployment. ## Control loop 1. Establish the shared design brief without waiting for human input, define a first playable slice, and write real shared contracts in `src/types/` before any coding agent starts. The slice orders work; it does not reduce the requested game to a smaller final outcome. 2. Configure the supported scaffold and establish a clean `npx tsc --noEmit -p tsconfig.json` gate. 3. Run Batch 1 sequentially, then Batches 2-4 in the ownership order from [references/BATCH_DISPATCH.md](references/BATCH_DISPATCH.md). 4. After every batch, run the type-check and Playwright smoke described in [references/SMOKE_AND_GOTCHAS.md](references/SMOKE_AND_GOTCHAS.md). A failing check stops progression: repair the responsible module or contract, then rebuild and re-test. 5. After the final batch, run the full playthrough and use the proportional integrated-review and fix loop in [references/STEP_DETAILS.md](references/STEP_DETAILS.md) until clean. ## Load-bearing safeguards - Never dispatch coding agents before contracts exist. - Never define contracts or assignments before the shared design brief exists. - Never declare a batch green without the exact successful `tsc --noEmit` evidence and its required smoke result. - Never skip a between-batch smoke or proceed past its failure. - Never locally redeclare a cross-module shape; route it to the contract owner and `typescript-engineer`. - Keep coding ownership exclusive. The manager writes no game code except the documented Batch 1 foundation boundary. - Keep every milestone, prerequisite, assessment, correction, and final acceptance executable by the manager and subagents without waiting for a human. Scale independent assessment to the change's importance and uncertainty; do not add routine artwork bake-offs or extra reviewers for small, settled fixes. - Do not blend build identities, weaken type safety with casts, or replace browser evidence with a claim that the game is green. Read [references/QUALITY_GUARDRAILS.md](references/QUALITY_GUARDRAILS.md) for the complete red flags and rationale; read [references/SMOKE_AND_GOTCHAS.md](references/SMOKE_AND_GOTCHAS.md) when web platform behavior fails. Use [references/STEP_DETAILS.md](references/STEP_DETAILS.md) for conditional setup, scope, and repair detail. Definitions, naming, and capacity route respectively through [references/DEFINITIONS.md](references/DEFINITIONS.md), [references/NAMING_GUARDRAILS.md](references/NAMING_GUARDRAILS.md), [references/CAPACITY_AND_SIZING.md](references/CAPACITY_AND_SIZING.md). Read the target repository's `docs/FUN_VIBES_DESIGN_STYLE.md` and `docs/PLAYFUL_TRAINING_GAME_STYLE.md` when present. Their canonical sources live in `starter-repo-template/templates/typescript/docs/`; this skill bundles neither guide. When absent, use `game-design-expert` and the shared brief.
Files in this package (27)
- SKILL.md 5 KB
- agents/openai.yaml 1 KB
- references/BATCH_DISPATCH.md 8 KB
- references/BUILD_ARTIFACTS.md 5 KB
- references/CAPACITY_AND_SIZING.md 1 KB
- references/DEFINITIONS.md 1 KB
- references/GITHUB_PAGES_DEPLOY.md 12 KB
- references/NAMING_GUARDRAILS.md 1 KB
- references/QUALITY_GUARDRAILS.md 7 KB
- references/SMOKE_AND_GOTCHAS.md 2 KB
- references/STEP_DETAILS.md 9 KB
- templates/agent_prompt_template.md 3 KB
- templates/build_github_pages.sh 3 KB
- templates/check_codebase.sh 2 KB
- templates/deploy_pages_workflow.yml 1 KB
- templates/dist_clean.sh 1 KB
- templates/eslint.config.js 1 KB
- templates/export_single_file.sh 1 KB
- templates/gitignore 1 KB
- templates/package.json 1 KB
- templates/playwright_smoke_test.md 2 KB
- templates/run_web_server.sh 3 KB
- templates/src_index.html 1 KB
- templates/src_layout.md 3 KB
- templates/tsconfig.json 1 KB
- templates/devel/setup_playwright.sh 1 KB
- templates/devel/setup_typescript.sh 1 KB
Versions
The database has no other skills named html-game-parallel-builder.
Database snapshot: 13.11.2026 · package version f28d2e760ece (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90local-game-playtest-358edd6e
Run browser-game playtests and frontend QA. Use when the user asks for smoke tests, screenshot-based verification, browser automation, HUD or overlay review, or structured issue-finding in a browser game. - 100custom-game-builder
Build or revise a specified playable browser game from a user's brief, including mechanics, art direction, testing and source delivery. Also prepare a game brief or implementation plan when explicitly requested. Use for custom games across genres, rather than only reskinning the Italia Uno example. - 100threejs-game
Build 3D browser games with Three.js using event-driven modular architecture. Use when creating a new 3D game, adding 3D game features, setting up Three.js scenes, or working on any Three.js game project. - 100world-builder
Create and manage generative game zones for Dorothy's Pokemon-style world. Use this skill when creating, updating, or designing game worlds via MCP tools. - 90build-full-game
End-to-end pipeline for building a complete, playtested browser game from a one-line idea with the studio's subagents. Use when the user asks to make, build or create a game ("make me a game where...", "oyun yarat", "oyun düzəlt") and no /new-game command is available in the host. - 100game-architecture
Game architecture patterns and best practices for browser games. Use when designing game systems, planning architecture, structuring a game project, or making architectural decisions about game code.