05-game-technical-implementation-specification
/05-game-technical-implementation-specification
Zamienia zatwierdzone wymagania gry w pakiety prac dla Unity, Godot, Unreal i platform Apple, z kontraktami kodu, zasobów i telemetrii.
- Autor
- peterbamuhigire ↗
- Repozytorium
- chwezi-sdlc-documentation ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.09.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 29.09.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Zamienia zatwierdzone wymagania gry w pakiety prac dla Unity, Godot, Unreal i platform Apple, z kontraktami kodu, zasobów i telemetrii.
Oryginalny opis (EN)
Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts.
Jak działa
- Use When
- Do Not Use When
- Required Inputs
- Workflow
- Outputs
- Evidence Produced
- Capability and permission boundaries
- Degraded mode
- Decision Rules
- Quality Standards
Podgląd SKILL.md
---
name: 05-game-technical-implementation-specification
description: "Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts."
metadata: {portable: true, compatible_with: [claude-code, codex]}
---
# Game Technical Implementation Specification
<!-- dual-compat-start -->
## Use When
- Game architecture needs module, scene, data, asset, protocol, build and test seams.
## Do Not Use When
- Architecture or authority is undecided.
- Do not copy legacy tutorial code without version verification.
## Required Inputs
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| `GREQ-*`, `GARCH-*`, ADRs, toolchain locks and acceptance tests | Architecture, engineering and QA | Yes | Stop the work package and return missing contracts. |
| Asset/UI handoff, data/ads/privacy schemas, adapters, protocol and build interface | Design and specialist owners | Conditional | Exclude or mark integration blocked. |
## Workflow
1. Decompose modules, scenes/worlds, data, assets and adapters with owners.
2. Define responsibilities, interfaces, events, lifetime and dependency rules.
3. Specify save/content/protocol versions, migrations, identifiers and idempotency.
4. Add engine-specific notes only for the pinned version.
5. Make every `GIMPL-*` consume `GREQ-*`, `GARCH-*`, relevant `VCLAIM-*`, approved game-design handoff, exact files/modules/assets or a bounded discovery task, and named exclusions.
6. Specify unit, integration, network, asset/UI, ad/privacy, accessibility/localisation, performance, security and device evidence per work package, including retained failed paths.
7. Define instrumentation purpose, errors, config, secrets, migrations, rollback/kill switches, owner role, estimate range/confidence and recalibration trigger.
8. Stop on an untestable interface, unresolved child/culture/privacy/ad decision or absent build target; recover with a spike and exit criteria.
## Outputs
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Game technical implementation specification | Client, backend, content, build and QA engineers | Packages have interfaces, versions, failures, tests and traces. |
## Evidence Produced
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
| `GIMPL-*` trace | Technical lead | Packages map requirements and architecture to code/assets, tests and build evidence. |
## Capability and permission boundaries
Read and search are allowed. Source edits, installs, services and releases require explicit authority.
## Degraded mode
Return qualified interface stubs, mark validation `not assessed`, and do not claim buildability.
## Decision Rules
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| Pure logic uses engine objects | Invert dependency. | Fragile tests. |
| Import is manual | Define presets and validation. | Content drift. |
| Schema is incompatible | Add migration or recovery rejection. | Stranded state. |
## Quality Standards
- No invented packages, hidden globals or placeholder methods; require failed-path evidence.
## Anti-Patterns
- Rules in scene components. Fix: isolate domain logic.
- Singleton sprawl. Fix: scoped composition.
- Manual import folklore. Fix: presets and validators.
- Editor test as completion. Fix: packaged evidence.
- Unbounded frame work. Fix: frequency budgets.
- Visual handoff reduced to a screenshot. Fix: consume states, tokens, content, input/access rules and binary acceptance from the design engine.
## References
- [Work-package schema](references/game-work-package-schema.md)
<!-- dual-compat-end -->
Pliki w paczce (2)
- SKILL.md 4 KB
- references/game-work-package-schema.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie 05-game-technical-implementation-specification.
Migawka bazy z 13.11.2026 · wersja paczki be2b23810c84 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95game-development
Wspiera tworzenie gier w Unity, Unreal Engine i Godot: mechaniki, fizykę i AI w silnikach gier. - 100gds-test-framework
Inicjuje szkielet testów gry w Unity, Unreal lub Godot, gotowy do pisania i uruchamiania testów. - 100gds-test-framework
Inicjalizuje framework testowy gier dla Unity, Unreal lub Godot. - 90engine-router
Kieruje projekt gry od fazy projektowej do implementacji w wybranym silniku: Godot, Unity, Unreal albo Three.js. - 100game-dev
Prowadzi studio gier w Godot, Unity i Unreal: projekt, programowanie, grafika, audio, QA, produkcja i orkiestracja zespołu agentów w sprintach i wydaniach. - 100gamedev-multiplayer
Wspiera dodawanie multiplayera do gry: klient-serwer czy P2P, autorytet serwera, replikacja stanu, predykcja, kompensacja opóźnień i integracja w Godot 4, Unity NGO oraz Unreal.