Skill: mike007jd/game-backend-selector (version 1.0.0)

--- name: game-backend-selector description: Choose or compare backend profiles based on required capabilities, project state, and quality target. Stay stack-neutral at the top level while still giving sharp recommendations and tradeoffs. license: MIT compatibility: Claude Code and Codex. Best results with file read/write access. metadata: author: game-superpowers version: "1.1.1" domain: game-development --- # Game Backend Selector ## Goal Select the backend profile that best serves the requested outcome. Use `./shared/reference/backend-profiles.md`. ## Deliverable Write `docs/game-studio/backend-decision.md`. ## Rules - Prefer capabilities over brand or fandom. - If the project already has a workable backend, bias toward it unless it is the blocker. - Optimize for the chosen quality target, not just the fastest toy result. - Respect project state: live iteration and greenfield do not deserve the same backend decision policy. ## Compare mode Use compare mode only when: - the backend choice is genuinely uncertain, - or the user explicitly requests comparison. When compare mode is used: - warn that it will usually cost more tokens and time, - keep the comparison narrow, - define the winner criteria before exploring. ## Specialist follow-through After choosing a backend profile, route to a concrete specialist when needed: - `game-web-2d-specialist` for `web-2d-ui-first` or `web-2d-world-first` - `game-web-3d-specialist` for `web-3d-preview` Top-level planning remains stack-neutral. Implementation guidance should still become concrete once a backend family is chosen.

path: CHANGELOG.md
content: # Changelog

## 1.1.1 — 2026-03-30

- Initial ClawHub publish bundle generated from `skills/game-backend-selector/SKILL.md`.
- Added bundle metadata, README, and MANIFEST for OpenClaw / ClawHub distribution.


path: MANIFEST.yaml
content: bundle: game-backend-selector
bundle_version: 1.1.1
bundle_date: 2026-03-30
description: >
  Choose or compare backend profiles based on required capabilities, project state, and quality target. Stay stack-neutral at the top level while still giving sharp recommendations and tradeoffs.
compatibility:
  designed_for:
    surfaces:
      - chat
      - cli
      - ide
    capabilities:
      - local filesystem access
      - markdown skill bundles
      - reusable game-development workflows
  tested_on:
    - platform: OpenClaw
      surface: ClawHub
      status: pending
      date: 2026-03-30
    - platform: Claude Code
      surface: CLI
      status: pass
      date: 2026-03-30
    - platform: Codex
      surface: CLI
      status: pass
      date: 2026-03-30
  spec_version: agentskills.io/1.0
  frontmatter_mode: metadata
dependencies:
  - game-web-2d-specialist
  - game-web-3d-specialist
files:
  - path: CHANGELOG.md
    role: reference
    version: 1
    hash: sha256:08aa94e996f17e3e988bbc874236c90a4c5017cc29a238fcd4d76cca6dc45046
    note: Bundle release notes
  - path: README.md
    role: reference
    version: 1
    hash: sha256:40da23135635fd8275c8e95c6643898dbe91a655758a6b5511e70b8e5f687090
    note: ClawHub-facing usage and context
  - path: SKILL.md
    role: skill
    version: 1
    hash: sha256:d3919ba281e90253000245e07f0a614738b3f9b96dbb2de16eb3da2104cac218
    note: Canonical skill definition for this publish bundle
  - path: examples/usage.md
    role: reference
    version: 1
    hash: sha256:7fc449c0b4023704a27763f8ed65213be454032ceb64c99cb403aadeb6865c90
    note: Referenced support file: examples/usage.md
  - path: shared/reference/backend-profiles.md
    role: reference
    version: 1
    hash: sha256:f43e18e5844678d050ebf34c561caab2efe5049a9775e86790ad7b84a8eb6e1d
    note: Referenced support file: shared/reference/backend-profiles.md
  - path: tests/smoke.md
    role: reference
    version: 1
    hash: sha256:60b4bf6f6048ad160ac0a5e075d1935f1b5574e93554afaa09e2cd2edb01ef60
    note: Referenced support file: tests/smoke.md


path: README.md
content: # game-backend-selector

Part of the **Game Superpowers** skill system.

## Summary

Choose or compare backend profiles based on required capabilities, project state, and quality target. Stay stack-neutral at the top level while still giving sharp recommendations and tradeoffs.

## Recommended usage

- Use `game-backend-selector` for this game project and keep the output evidence-based.
- Apply `game-backend-selector` to improve or assess an existing browser game in a focused way.
- Use `game-backend-selector` as part of a larger Game Superpowers workflow when the request clearly matches game backend selector.

## Companion skills

- `game-web-2d-specialist`
- `game-web-3d-specialist`

## Source of truth

This publish bundle is derived from the Game Superpowers source repository.
Canonical authoring lives in:

```text
skills/game-backend-selector/SKILL.md
```

## Notes

- This bundle is published for OpenClaw / ClawHub distribution.
- The Game Superpowers repository also supports Claude Code and Codex distributions.
- If a workflow references companion skills, install those companion skills as separate bundles.


path: examples/usage.md
content: # Usage Examples

## Example prompts

- Use `game-backend-selector` for this game project and keep the output evidence-based.
- Apply `game-backend-selector` to improve or assess an existing browser game in a focused way.
- Use `game-backend-selector` as part of a larger Game Superpowers workflow when the request clearly matches game backend selector.

## Expected behavior

- Load the skill instructions from `SKILL.md`.
- Use any packaged `shared/` references when the skill body points to them.
- If the workflow calls for companion skills, tell the user which companion skills should be installed or invoked next.


path: shared/reference/backend-profiles.md
content: # Backend Profiles (Capability-Driven)

Use these as neutral archetypes. Start from capability fit, not library fandom.

## web-2d-ui-first
Best when:
- menus / HUD / overlays dominate
- input clarity matters more than simulation complexity
- web delivery is primary

Strengths:
- fast iteration
- excellent UI layering
- easy shareability

Risks:
- can drift into app-like architecture unless game state is explicit

Specialist follow-through:
- `game-web-2d-specialist`

## web-2d-world-first
Best when:
- the playfield dominates
- simulation, collisions, and moment-to-moment action matter most

Strengths:
- game loop stays central
- good for action, arcade, puzzle, bullet-hell

Risks:
- UI can become an afterthought without an explicit HUD plan

Specialist follow-through:
- `game-web-2d-specialist`

## web-3d-preview
Best when:
- 3D presentation matters
- fast preview and browser delivery are still important

Strengths:
- quick sharing
- strong preview loops
- good for stylized 3D or hybrid UI-heavy products

Risks:
- easy to overbuild visuals before gameplay proves out
- performance budgets matter earlier

Specialist follow-through:
- `game-web-3d-specialist`

## engine-embedded-2d
Best when:
- the project already lives in a full engine ecosystem
- or stronger editor/runtime conventions are clearly worth it

Strengths:
- mature tooling
- many built-in systems

Risks:
- can be too heavy for rapid AI-native iteration

## engine-embedded-3d
Best when:
- the product clearly needs deeper engine systems from the start

Strengths:
- mature 3D systems
- existing production workflows

Risks:
- large surface area for agent-driven work
- expensive when the brief is vague

## custom-shader-lab
Best when:
- procedural visuals or graphics R&D are the point

Strengths:
- expressive
- great for visual experiments

Risks:
- UX and core loop can be underbuilt if not actively protected

## Selection rules
- Choose the narrowest profile that satisfies the spec.
- Prefer the profile with the shortest path to the chosen quality target.
- If the repo is already committed to a viable backend, bias toward that unless the current backend is the problem.
- Use compare mode only when uncertainty is real or the user explicitly asks for it.
- Compare mode usually costs more tokens and time; warn the user when enabling it.


path: tests/smoke.md
content: # Smoke Test

Bundle: `game-backend-selector`
Version: `1.1.1`

## Prompt

Use `game-backend-selector` on a fitting game-development task.

## Expected checks

- The agent recognizes the skill's stated purpose.
- The agent uses packaged references when `SKILL.md` points to `./shared/...`.
- The agent does not claim companion skills are bundled implicitly when they are separate installs.
- Companion skills referenced in this bundle: game-web-2d-specialist, game-web-3d-specialist


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)