agentsclimarketplace

Gsp super build

Skill mike007jd/game-superpowers/publish/clawhub/gsp-super-build

Use when orchestrating serious game work across concept, scope, build mode, quality target, and downstream routing.From its SKILL.md

Install
npx -y skills add mike007jd/game-superpowers --skill gsp-super-build

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.3 KB, 519 tokens by cl100k_base, as published. Nobody here has run it

Game Super Build

Lead game-production workflow. Choose the right strategy for project state and quality target instead of just producing the smallest thing that runs.

Outputs

Follow the gsp-orchestrator output strategy:

  • inline (default): keep all findings, plans, and decisions in conversation. Do not create docs/ files.
  • minimal: write only docs/game-studio/plan.md and docs/game-studio/quality-target.md for cross-session continuity.
  • full: create or update the relevant docs/game-studio/ records for project state, concept, requirements, scope, build strategy, backend, UX, feedback, architecture, plan, quality, and release safety.

Phase map

  1. Classify
    • Detect build, audit, or both.
    • Existing repo inspection routes to gsp-project-audit first.
    • Assess project state with gsp-project-state-assessment.
  2. Lock the brief
    • Use gsp-concept-brainstorm when the request is vague, weakly differentiated, archetype-ambiguous, or a one-prompt showcase build.
    • Use gsp-requirements-brainstorm.
    • Use gsp-scope-profile.
    • Use gsp-build-strategy.
  3. Choose implementation route
    • Use gsp-backend-selector.
    • Route explicit Douyin H5 delivery through gsp-douyin-h5 before deeper browser specialization.
    • Route chosen web 2D or browser 3D profiles to the matching specialist skill.
  4. Design the product
    • Use gsp-ux-flow-designer, gsp-feedback-design, and gsp-mechanics-systems-design.
    • Use gsp-production-code when the quality target needs product-grade implementation standards.
  5. Execute and verify
    • Use gsp-implementation-plan.
    • If subagents are available and the target is above throwaway-spike quality, prefer gsp-subagent-build-loop.
    • Review and verify with gsp-build-review, gsp-playability-verifier, and gsp-screenshot-critic.
  6. Escalate only when justified
    • Use compare or rolling-supervisor modes only when the task size or uncertainty warrants them.

Important

For browser games, stack-neutral does not mean implementation-vague. Do not confuse fewer questions with better workflow.

What ships with it: 5 files

4.9 KB alongside SKILL.md

examples/

tests/

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.