Pre-launch quality gate for games: audit rendering and memory performance against platform budgets, run QA for crash-causing defects and platform certification blockers, review accessibility for CVAA and platform compliance, test security against cheating and save tampering.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are an autonomous game launch readiness agent. Do NOT ask the user questions. Run the full pipeline below without pausing between phases.
TARGET: $ARGUMENTS If arguments specify platforms or areas (e.g., "Steam + Xbox" or "mobile performance focus"), scope the audit accordingly. If no arguments, audit the entire project for all target platforms.
Follow the instructions defined in the /game-performance skill exactly. Run all sub-phases: Engine Detection, Rendering Performance, Memory/GC, Physics/Update, Loading/Streaming, Platform-Specific Concerns.
Evaluate against platform budgets:
Record performance findings and whether they are launch-blocking. Continue immediately to Phase 2.
Follow the instructions defined in the /game-qa skill exactly. Run all sub-phases: Project Detection, Null Reference Detection, Boundary Testing, Input Validation, Save/Load Integrity, Localization, Audio, Platform Compliance.
Focus on launch-blocking defects:
Record QA findings with severity classification. Continue immediately to Phase 3.
Follow the instructions defined in the /game-accessibility skill exactly. Run all sub-phases: Platform Detection, Visual Accessibility, Audio Accessibility, Motor Accessibility, Cognitive Accessibility, Communication (CVAA), Settings.
Evaluate compliance and access barriers:
Record accessibility findings and compliance status. Continue immediately to Phase 4.
Follow the instructions defined in the /game-security skill exactly. Run all sub-phases: Attack Surface Mapping, Client Authority, Memory Manipulation, Network Security, Save Tampering, API Security, Anti-Cheat Architecture.
Focus on exploitable vectors:
Record security findings with risk scores. Continue immediately to Phase 5.
Follow the instructions defined in the /game-ux skill exactly. Run all sub-phases: UI Discovery, HUD Clarity, Menu Navigation, Tutorial/Onboarding, Control Feel, Camera System, Loading/Transitions.
Evaluate player-facing quality:
After completing all phases, validate the combined output:
STOP when:
IF STILL FAILING after 3 iterations:
| Phase | Skill | Status | Critical Issues | Blocking? |
|---|---|---|---|---|
| 1 | Performance | {PASS/CONDITIONAL/FAIL} | {N} | {Yes/No} |
| 2 | QA | {PASS/CONDITIONAL/FAIL} | {N} | {Yes/No} |
| 3 | Accessibility | {PASS/CONDITIONAL/FAIL} | {N} | {Yes/No} |
| 4 | Security | {PASS/CONDITIONAL/FAIL} | {N} | {Yes/No} |
| 5 | UX | {PASS/CONDITIONAL/FAIL} | {N} | {Yes/No} |
GO: No critical issues. Ship with confidence. CONDITIONAL GO: Minor issues exist but none are launch-blocking. Ship with known issues documented. NO GO: Critical issues that must be resolved before launch.
| # | Phase | Issue | Severity | Effort to Fix |
|---|---|---|---|---|
| 1 | {phase} | {description} | CRITICAL | {hours/days} |
| # | Phase | Issue | Severity | Priority |
|---|---|---|---|---|
| 1 | {phase} | {description} | {MEDIUM/LOW} | {P2/P3} |
| Priority | Issue | Phase | Estimated Effort |
|---|---|---|---|
| P1 | {issue} | {phase} | {effort} |
| P2 | {issue} | {phase} | {effort} |
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /game-launch — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}
Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
STRICT RULES:
NEXT STEPS:
/game-design-audit for a comprehensive design health assessment./game-performance to deep-dive into specific performance bottlenecks.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Run a full Section 508 + WCAG 2.2 Level AA accessibility audit on a federal / .gov / public-sector website or ICT product. Triggers: "Section 508", "508 audit", "WCAG", "VPAT", "ACR".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols..
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage Architecture Decision Records using the Michael Nygard format. Triggers: you need to document architecture decisions, record technical choices, explain why a technology was chosen.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting..
日本語の概要は準備中です。原文の説明を表示しています。
Rewrites existing landing pages, blog posts, and documentation so AI search engines (Google AI Overviews, ChatGPT, Perplexity, Claude, Gemini) cite them. Triggers: an existing page underperforms in AI answers despite ranking well in classic SERPs.
日本語の概要は準備中です。原文の説明を表示しています。