Stage the remaining recommended skills for Sprint 0 adoption

.github/skills/README.md

@@ -13,6 +13,8 @@ This directory contains the repository-local skills that Copilot can use for Spa
 
 ## Intake flow for additional skills
 
+Currently staged from the recommendation set: `changelog-generator`, `webapp-testing`, `gh-fix-ci`, `codebase-migrate`, `game-designer`, `gameplay-programmer`, `level-designer`, and `game-artist`.
+
 1. Drop raw or draft material into `.github/skills/incoming/`.
    - If the raw source currently lives in `dodatki/skills/`, copy or adapt only the selected skill instead of treating the whole folder as active.
 2. Review whether it fits the repo rules, stack, and current gate.

.github/skills/incoming/README.md

@@ -10,6 +10,17 @@ Use this directory as the staging area for additional skills before they become
 - partially adapted skill packages,
 - notes about source, purpose, and gate.
 
+## Currently staged recommended skills
+
+- `changelog-generator` — release and milestone summaries (`CI/release` gate)
+- `webapp-testing` — browser/PWA validation support (`app scaffold` gate)
+- `gh-fix-ci` — GitHub Actions diagnostics (`CI` gate)
+- `codebase-migrate` — larger refactors after the app exists (`app scaffold` gate)
+- `game-designer` — design framing without blocked mechanics (`Sprint 0 docs` gate)
+- `gameplay-programmer` — implementation support after `mechanika/` and app scaffold (`app scaffold` gate)
+- `level-designer` — sector/beacon pacing support (`Sprint 0 docs` gate)
+- `game-artist` — later visual direction support (`design pipeline` gate)
+
 ## Required note for each incoming skill
 
 Include at least:

.github/skills/incoming/changelog-generator/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: changelog-generator
+description: 'Stages release and milestone changelog work for SpaceshipGame without inventing unsupported delivery steps.'
+---
+
+# Changelog Generator
+
+Use this staged skill when the repository needs structured milestone summaries, release notes, or visible progress updates.
+
+## Intended SpaceshipGame use
+
+- summarize shipped documentation, feature, or workflow milestones,
+- draft `CHANGELOG.md` or release-note sections,
+- help keep README progress notes readable once the project starts moving beyond Sprint 0.
+
+## Files it may touch
+
+- `CHANGELOG.md`,
+- `README.md`,
+- release summary docs under `docs/`,
+- PR or milestone notes when that workflow exists.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (`ComposioHQ/awesome-codex-skills` shortlist),
+- adapted locally for SpaceshipGame instead of copied verbatim.
+
+## Current gate
+
+- `CI/release` for routine use,
+- can be promoted earlier only if the repo adopts a durable changelog workflow.
+
+## Current blockers / open questions
+
+- no release workflow yet,
+- no `CHANGELOG.md` yet,
+- no app milestone cadence yet.
+
+## Adaptation notes
+
+- keep output concise and beginner-friendly,
+- summarize only repo reality; do not invent shipped features,
+- if milestones are still vague, write open questions instead of fake release notes.

.github/skills/incoming/codebase-migrate/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: codebase-migrate
+description: 'Stages larger repository refactors and structural migrations once SpaceshipGame has a real app tree.'
+---
+
+# Codebase Migrate
+
+Use this staged skill for future bulk refactors, folder moves, API migrations, or architecture-aligned restructuring.
+
+## Intended SpaceshipGame use
+
+- help move files safely as `src/`, tests, and data assets grow,
+- support future refactors after mechanic specs harden,
+- keep documentation and architecture notes synchronized during structural changes.
+
+## Files it may touch
+
+- `src/`,
+- `.github/` workflow or prompt files,
+- tests,
+- architecture and migration docs.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (`ComposioHQ/awesome-codex-skills` shortlist),
+- adapted locally instead of imported wholesale.
+
+## Current gate
+
+- `app scaffold`.
+
+## Current blockers / open questions
+
+- no production code tree yet,
+- no migration pressure yet,
+- real value starts after the first playable loop exists.
+
+## Adaptation notes
+
+- preserve serializable save-state assumptions,
+- avoid mixing migration work with speculative mechanics changes,
+- keep docs and README updated during every future migration.

.github/skills/incoming/game-artist/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: game-artist
+description: 'Stages later-phase visual and UI art direction support for SpaceshipGame.'
+---
+
+# Game Artist
+
+Use this staged skill when the project moves beyond placeholders and needs stronger visual direction, UI art consistency, or asset-pipeline planning.
+
+## Intended SpaceshipGame use
+
+- support pixel-art direction and UI overlay cohesion,
+- help document placeholder-to-final art transitions,
+- assist later art-pipeline planning without forcing tool adoption too early.
+
+## Files it may touch
+
+- `docs/` art-direction notes,
+- UI or asset guidance under `public/` and `src/ui/` once they exist,
+- future art-pipeline ADRs.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (MCP Market skills shortlist),
+- adapted into a local staged definition.
+
+## Current gate
+
+- `design pipeline`.
+
+## Current blockers / open questions
+
+- no production UI or asset pipeline yet,
+- final art polish is out of MVP scope,
+- any Figma/Blender workflow remains optional and later.
+
+## Adaptation notes
+
+- preserve pixel-art and mobile-first rules,
+- do not treat visual polish as a blocker for the first playable loop,
+- prefer documenting art direction before introducing new tools or dependencies.

.github/skills/incoming/game-designer/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: game-designer
+description: 'Stages a design-focused skill for loops, events, pacing, and player-facing decisions without inventing blocked mechanics.'
+---
+
+# Game Designer
+
+Use this staged skill when working on player-facing design inside approved docs or `mechanika/` sections.
+
+## Intended SpaceshipGame use
+
+- refine event structure, pacing, and loop clarity,
+- review mission and progression intent at the design-document level,
+- strengthen player-facing choices without hardcoding formulas too early.
+
+## Files it may touch
+
+- `docs/GDD.md`,
+- `docs/GAME_BRIEF.md`,
+- `mechanika/`,
+- event-design notes in `docs/`.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (MCP Market skills shortlist),
+- adapted into a local staged skill outline for SpaceshipGame.
+
+## Current gate
+
+- `Sprint 0 docs` for high-level design discussion,
+- promotion should wait until the repo decides it needs this as a standard local skill.
+
+## Current blockers / open questions
+
+- final mechanics authority still belongs to `mechanika/`,
+- this skill must never invent combat, trait, morale, XP, faction, or quest-chain rules.
+
+## Adaptation notes
+
+- use it for design framing, not implementation authority,
+- convert unclear ideas into open questions instead of invented systems,
+- keep story canon in `docs/FABULA.md` separate from mechanics details.

.github/skills/incoming/gameplay-programmer/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: gameplay-programmer
+description: 'Stages implementation-oriented gameplay guidance for when approved mechanics start turning into systems.'
+---
+
+# Gameplay Programmer
+
+Use this staged skill when approved mechanic specs need to be translated into clean systems and scene integration.
+
+## Intended SpaceshipGame use
+
+- map approved `mechanika/` rules into `src/systems/`,
+- keep gameplay logic data-driven and testable,
+- support integration between systems, schemas, and scenes once the app exists.
+
+## Files it may touch
+
+- `src/systems/`,
+- `src/data/`,
+- `src/models/` and `src/types/`,
+- tests for gameplay logic.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (MCP Market skills shortlist),
+- adapted locally as a staged skill definition.
+
+## Current gate
+
+- `app scaffold`,
+- approved mechanic specs in `mechanika/` for any non-stub behavior.
+
+## Current blockers / open questions
+
+- no `src/` tree yet,
+- no gameplay systems yet,
+- pending mechanic approval for combat, traits, progression, morale, factions, and quest logic.
+
+## Adaptation notes
+
+- scenes orchestrate; systems own business logic,
+- keep saves serializable and data-driven,
+- if a mechanic is still blocked, generate only a stub and stop.

.github/skills/incoming/gh-fix-ci/SKILL.md

@@ -0,0 +1,41 @@
+---
+name: gh-fix-ci
+description: 'Stages future GitHub Actions failure diagnosis and repair workflow for SpaceshipGame.'
+---
+
+# GH Fix CI
+
+Use this staged skill when GitHub Actions exist and the repository needs targeted diagnosis of failed workflows.
+
+## Intended SpaceshipGame use
+
+- inspect failing build, lint, or test jobs,
+- triage workflow regressions,
+- keep CI fixes small and aligned with the repo architecture.
+
+## Files it may touch
+
+- `.github/workflows/`,
+- test or config files directly causing CI failure,
+- docs that describe required validation commands.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (`ComposioHQ/awesome-codex-skills` shortlist),
+- adapted locally for GitHub-first diagnostics rather than copied as-is.
+
+## Current gate
+
+- `CI`.
+
+## Current blockers / open questions
+
+- no GitHub Actions workflows yet,
+- no build/test pipeline yet,
+- current repo state is Sprint 0 docs-only.
+
+## Adaptation notes
+
+- always inspect actual workflow logs before editing,
+- never guess the failure root cause from memory alone,
+- avoid adding CI complexity before the app exists.

.github/skills/incoming/level-designer/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: level-designer
+description: 'Stages map-flow and encounter-structure guidance for sectors, beacons, and pacing.'
+---
+
+# Level Designer
+
+Use this staged skill when the project starts formalizing sector flow, beacon pacing, encounter distribution, or layout-driven progression.
+
+## Intended SpaceshipGame use
+
+- shape sector/map progression,
+- review beacon pacing and event density,
+- support encounter distribution without drifting into unsupported combat systems.
+
+## Files it may touch
+
+- `mechanika/01-game-flow.md`,
+- `mechanika/02-screens-and-scenes.md`,
+- `mechanika/07-events.md`,
+- future map or beacon data docs.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (MCP Market skills shortlist),
+- adapted into a repo-staged skill instead of treated as an active engine-specific package.
+
+## Current gate
+
+- `Sprint 0 docs` for pacing notes,
+- practical use expands after map/beacon systems are specified.
+
+## Current blockers / open questions
+
+- map progression rules are not finalized yet,
+- reserved beacon types such as `combat` and `quest` are still blocked by `mechanika/`.
+
+## Adaptation notes
+
+- focus on pacing, structure, and readability,
+- keep combat and quest-chain details out until approved,
+- prefer simple sector-flow language over premature numeric balancing.

.github/skills/incoming/webapp-testing/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: webapp-testing
+description: 'Stages browser and PWA validation guidance for the future Phaser/Vite app shell.'
+---
+
+# Webapp Testing
+
+Use this staged skill when SpaceshipGame has a runnable browser app and needs repeatable smoke, UI, or PWA checks.
+
+## Intended SpaceshipGame use
+
+- validate Phaser scene boot flow in the browser,
+- review mobile viewport behavior and installability,
+- support future Playwright-based smoke tests and regression checks.
+
+## Files it may touch
+
+- `package.json`,
+- Playwright or Vitest test files,
+- `.github/workflows/` when browser validation enters CI,
+- `docs/` notes for QA or PWA checks.
+
+## Source
+
+- recommendation source: `SKILLS_RECOMMENDATIONS.txt` (`ComposioHQ/awesome-codex-skills` shortlist),
+- adapted locally for a Phaser 4 + Vite + PWA workflow.
+
+## Current gate
+
+- `app scaffold` now,
+- `test/PWA` once the project can actually boot in a browser.
+
+## Current blockers / open questions
+
+- no `package.json`,
+- no `src/` tree,
+- no runnable Phaser shell,
+- no Playwright setup yet.
+
+## Adaptation notes
+
+- prefer validating existing repo commands instead of inventing a test stack,
+- keep testing focused on browser-first and Android-PWA behavior,
+- avoid assuming desktop-only UI patterns.

README.md

@@ -31,6 +31,7 @@ Pre-initialization / Sprint 0. No production code has been scaffolded yet. The `
 - `docs/ADRs/ADR-001-stack.md` — stack decision record.
 - `SKILLS_RECOMMENDATIONS.txt` — curated good-plus set of recommended skills and MCP servers for the repo.
 - `docs/skills-adoption/README.md` — expanded research and adoption order for skills/MCP rollout.
+- `.github/skills/incoming/` — staged recommended skills that are not active yet because they still depend on app, CI, or design-pipeline gates.
 - `dodatki/research/` — creative scientific research pack and prompt flow for later mechanika work.
 - `dodatki/skills/` — raw external skill library to review before adapting items into `.github/skills/incoming/`.
 - `.github/prompts/skills-adoption.prompt.md` — autonomous prompt for executing the skills/MCP adoption plan.
@@ -41,7 +42,7 @@ Pre-initialization / Sprint 0. No production code has been scaffolded yet. The `
 
 Ta część ma być aktualizowana na bieżąco, tak aby kolejna osoba mogła przejąć projekt bez wcześniejszego kontekstu.
 
-Aktualnie projekt jest w Sprint 0: porządkowana jest dokumentacja, workflow Copilota i materiały wejściowe. Nie ma jeszcze `package.json`, katalogu `src/` ani uruchamialnej wersji gry.
+Aktualnie projekt jest w Sprint 0: porządkowana jest dokumentacja, workflow Copilota i materiały wejściowe. Nie ma jeszcze `package.json`, katalogu `src/` ani uruchamialnej wersji gry. Zestaw rekomendowanych skillów został już rozdzielony na aktywne lokalne skille i staged intake w `.github/skills/incoming/`, żeby przed dalszą pracą nad fabułą było jasne, co jest gotowe teraz, a co czeka na kolejne bramki.
 
 Najbliższe kroki:
 
@@ -58,7 +59,7 @@ Najbliższe kroki:
    - `/gdd` — utrzymanie dokumentu projektowego w zgodzie z briefem i fabułą,
    - `/skills-adoption` — wdrażanie zatwierdzonych skillów i MCP z dokumentacji,
    - `/investigate`, `/new-scene`, `/new-system`, `/new-event`, `/data-schema`, `/pwa-check`, `/mobile-ux`, `/code-review`.
-4. W Sprint 0 trzymaj kolejność pracy: `/game-dev` → `/game-brief` → `/fabula` → `/gdd` → `/skills-adoption`.
+4. W Sprint 0 trzymaj kolejność pracy: `/game-dev` → `/game-brief` → `/fabula` → `/gdd` → `/skills-adoption`. Skill packages wymagające aplikacji, CI albo pipeline'u art nadal zostają w `.github/skills/incoming/` do czasu odblokowania tych bramek.
 5. Nie wymyślaj jeszcze szczegółowych mechanik walki, traitów, morale, progresji, frakcji ani łańcuchów questów. Te reguły mają trafić do `mechanika/`, gdy zostaną zatwierdzone.
 6. Traktuj `dodatki/research/` i `dodatki/skills/` jako biblioteki wejściowe. Zatwierdzone wnioski przenoś do `docs/`, `mechanika/` albo `.github/skills/`.
 7. Dopiero po ustabilizowaniu dokumentacji i assetów `.github/` scaffolduj projekt Vite + Phaser 4.