Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

html-game-parallel-builder

/html-game-parallel-builder

Prowadzi równoległe budowanie modularnej gry w TypeScript przez kilku agentów: serwowanie, testy dymne i publikację na Pages.

Repozytorium
vosslab-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
22.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
27
Skrypty
8
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 8 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: 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

Co robi i kiedy

Prowadzi równoległe budowanie modularnej gry w TypeScript przez kilku agentów: serwowanie, testy dymne i publikację na Pages.

Oryginalny opis (EN)

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.

Jak działa

  1. Required routing
  2. Build and release identity
  3. Control loop
  4. Load-bearing safeguards
Sekcje z nagłówków SKILL.md, w oryginale · 95 linii, 591 słów
Podgląd SKILL.md
---
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.
Pliki w paczce (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

Wersje

W bazie nie ma innych skilli o nazwie html-game-parallel-builder.

Migawka bazy z 13.11.2026 · wersja paczki f28d2e760ece (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90local-game-playtest-358edd6e
    Przeprowadza testy gry w przeglądarce: dymne, zrzuty ekranu, automatyzację i wyszukiwanie problemów w interfejsie.
  • 100custom-game-builder
    Buduje lub poprawia grę przeglądarkową według opisu użytkownika: mechanikę, styl graficzny, testy i dostarczenie kodu.
  • 100threejs-game
    Buduje gry 3D w przeglądarce w Three.js z modularną architekturą opartą na zdarzeniach, od sceny po mechanikę rozgrywki.
  • 100world-builder
    Tworzy i zarządza strefami gry w stylu Pokémon przez narzędzia MCP i projektuje świat gry.
  • 90build-full-game
    Prowadzi przez budowę kompletnej gry przeglądarkowej z jednego pomysłu, z testowaniem rozgrywki przez zespół subagentów.
  • 100game-architecture
    Pomaga projektować architekturę gry w przeglądarce: wzorce systemów, strukturę projektu i decyzje architektoniczne.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.