ClawHub

Game Build Strategy

v1.0.0

Decide the AI-native development mode, quality target, task granularity, and refactor policy based on project state and user intent. This skill prevents both...

⭐ 0· 121·0 current·0 all-time
by@mike007jd

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mike007jd/game-build-strategy.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Game Build Strategy" (mike007jd/game-build-strategy) from ClawHub.
Skill page: https://clawhub.ai/mike007jd/game-build-strategy
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install game-build-strategy

ClawHub CLI

Package manager switcher

npx clawhub@latest install game-build-strategy
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description ask for a build strategy writer; the bundle only contains templates and references and asks the agent to write docs under docs/game-studio—these are coherent and proportionate to the stated purpose.
✓
Instruction Scope
SKILL.md instructs the agent to read packaged shared/ references and write two markdown files (build-strategy and quality-target). This stays within the declared purpose. It does note that best results require file read/write access, which aligns with the instruction to write docs.
✓
Install Mechanism
No install spec and no code files—instruction-only. Nothing is downloaded or executed, so there is low install risk.
✓
Credentials
The skill declares no required environment variables, no credentials, and no config paths. That is proportionate to its simple doc-generation role.
✓
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It does not modify other skills or system settings.
Assessment
This skill is an instruction-only helper that reads bundled templates and writes two markdown files into docs/game-studio. It does not request credentials or install code, but it does expect file read/write access—so only enable it for projects where you trust the agent to create or modify repository files. Review any generated docs before committing them to source control. If you prefer an agent that cannot write files automatically, run the skill in a read-only mode (have it produce content in the chat and paste or save manually).

Like a lobster shell, security has layers — review code before you run it.

latestvk977as89rx1jreexc5x26jgpmh83x9x1
121downloads
0stars
1versions
Updated 4w ago
v1.0.0
MIT-0
@mike007jd
latest
Download

Game Build Strategy

Goal

Choose the right build strategy for the project. Write docs/game-studio/build-strategy.md and docs/game-studio/quality-target.md.

Use:

  • ./shared/reference/development-modes.md
  • ./shared/reference/quality-targets.md
  • ./shared/templates/build-strategy.md
  • ./shared/templates/quality-target.md

Development modes

  • yolo-super
  • guided-build
  • refactor-open
  • surgical-live

Quality targets

  • first-playable
  • polished-prototype
  • production-feature
  • live-patch

Selection rules

  • greenfield + narrow mechanic spike -> yolo-super + first-playable
  • greenfield + serious showcase build -> usually yolo-super or guided-build + polished-prototype
  • existing product-facing feature work -> usually guided-build or refactor-open + production-feature
  • shipped or live-risky -> surgical-live + live-patch

Planning policy

Match task size to the mode:

  • aggressive modes can use large coherent implementation chunks
  • production-feature work can use medium coherent chunks
  • live work should use smaller changes with tighter verification

Guardrail

Do not let “safe” planning ruin the result on low-risk greenfield work. Do not let “fast” planning justify broad rewrites on live products.

Comments

Loading comments...