ワンクリックでManusで任意のスキルを実行

game-readiness

スター2

フォーク0

更新日2026年6月3日 22:10

Validates a game or interactive product for playability, clarity, feedback, and scale-readiness. Use at milestones, before large scope changes, or when the user asks if the product feels ready or is ready to scale.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

pbuckles22

pbuckles22/Rust_Julia_FFI_Flutter_Template

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Game Readiness — Project

Validates that the product feels ready (not just correct) and is ready to scale without costly rework. Apply at milestones or before major scope. Useful for games, puzzles, or any interactive product.

When to apply

User asks: "Is this ready?", "Ready to scale?", "Does this feel right?"
Before locking large UX or content scope.
At sprint or milestone boundaries when "done" needs a playability/readiness check.

1. Clarity and feedback

Goal visible — User can understand the primary goal quickly (e.g. first 30 seconds).
Feedback — Every meaningful action has clear feedback (visual and/or haptic).
Fairness — No dead ends or confusing failure modes.

2. Feel (not dry or academic)

Responsiveness — Input → reaction feels immediate.
Reward on success — Success state feels like a win, not "dialog closed."
No clutter — UI supports the core experience.

3. Scale-readiness

Pipeline — Content/levels (if any) are validated (e.g. solvability, consistency).
Performance — No blocking on UI thread; acceptable frame time.
Progress & persistence — Progress (if applicable) is persisted and visible.

Output format

Produce a short report: Clarity PASS/WARN/FAIL, Feedback PASS/WARN/FAIL, Scale-readiness PASS/WARN/FAIL, plus Actions (concrete fixes for each WARN/FAIL).

このリポジトリの他の Skills

同じリポジトリ

code-quality-gate

pbuckles22/Rust_Julia_FFI_Flutter_Template

Change-aware quality pass: diff scope, readability, function size and control flow, comments where non-obvious, and alignment with project linting. Use before merge or with handoff when the user wants industry-style maintainability beyond what tests assert.

2026-06-032

code-reviewer

pbuckles22/Rust_Julia_FFI_Flutter_Template

Review code changes for correctness, security, project conventions, and maintainability. Use when reviewing a diff, before commit, or when the user asks for a code review.

2026-06-032

context-bootstrapper

pbuckles22/Rust_Julia_FFI_Flutter_Template

Receiving-agent protocol. Boots a new agent into the minimum correct context (select + isolate) and produces a clear next-step plan without guessing.

2026-06-032

eval-engineer

pbuckles22/Rust_Julia_FFI_Flutter_Template

Define and maintain lightweight evaluations (acceptance criteria, regression checks, golden tests) so "green" is objective and repeatable.

2026-06-032

github-feature-workflow

pbuckles22/Rust_Julia_FFI_Flutter_Template

Short-lived feature branches; TDD + lint + merge-ready command as exit criteria before commit; push and merge to main (or user-directed flow). Do not default to asking the user to open a PR. Use when implementing a feature or non-trivial fix, when the user asks for branch/git workflow, or after substantial edits that should not stay uncommitted.

2026-06-032

green-and-clean

pbuckles22/Rust_Julia_FFI_Flutter_Template

Operating model for disciplined agent work: stay on scope, avoid guessing, decompose work into verifiable chunks, and keep context lean and durable.

2026-06-032

name	game-readiness
description	Validates a game or interactive product for playability, clarity, feedback, and scale-readiness. Use at milestones, before large scope changes, or when the user asks if the product feels ready or is ready to scale.

Game Readiness — Project

When to apply

User asks: "Is this ready?", "Ready to scale?", "Does this feel right?"
Before locking large UX or content scope.
At sprint or milestone boundaries when "done" needs a playability/readiness check.

1. Clarity and feedback

Goal visible — User can understand the primary goal quickly (e.g. first 30 seconds).
Feedback — Every meaningful action has clear feedback (visual and/or haptic).
Fairness — No dead ends or confusing failure modes.

2. Feel (not dry or academic)

Responsiveness — Input → reaction feels immediate.
Reward on success — Success state feels like a win, not "dialog closed."
No clutter — UI supports the core experience.

3. Scale-readiness

Pipeline — Content/levels (if any) are validated (e.g. solvability, consistency).
Performance — No blocking on UI thread; acceptable frame time.
Progress & persistence — Progress (if applicable) is persisted and visible.

Output format

Produce a short report: Clarity PASS/WARN/FAIL, Feedback PASS/WARN/FAIL, Scale-readiness PASS/WARN/FAIL, plus Actions (concrete fixes for each WARN/FAIL).