flame-harness-contract

Generate a binding contract with verifiable completion criteria for Flutter Flame game projects.

54|5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/tjdrhs90/flutter-flame-harness --skill flame-harness-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flame-harness-contract
Source: https://github.com/tjdrhs90/flutter-flame-harness/tree/main/skills/flame-harness-contract
Command: npx skills add https://github.com/tjdrhs90/flutter-flame-harness --skill flame-harness-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in game development by enforcing a rigorous, verifiable contract between the project requirements and the implementation phase, preventing scope creep and ensuring technical quality.

Core Features & Use Cases

  • Mandatory Hard Gates: Automatically enforces 8 non-negotiable technical standards, including test coverage, analysis, and asset management.
  • Platform-Robustness Verification: Validates critical game-specific requirements like audio safety, haptics, lifecycle management, and durable save persistence.
  • Negotiation Workflow: Supports both standard and strict modes to ensure functional criteria are concrete, measurable, and fully aligned with the PRD.

Quick Start

Invoke the flame-harness-contract skill to generate the formal agreement document based on the current project configuration and design documentation.

Frequently Asked Questions about flame-harness-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce test coverage and code quality gates for a Flutter Flame game project?

Enforce test coverage and code quality gates for a Flutter Flame game project by generating a binding contract that mandates eight non-negotiable technical standards before development begins. This ensures all game mechanics are measurable and documented.

What is the best way to prevent scope creep in Flutter game development?

Prevent scope creep in Flutter game development by formalizing verifiable completion criteria and mandatory technical gates into a binding contract. This eliminates ambiguity between project requirements and the implementation phase.

How do I validate platform robustness for Flutter Flame game mechanics?

Validate platform robustness for Flutter Flame game mechanics by mandating verification of audio safety, haptics, lifecycle management, and durable save persistence. This ensures critical game-specific requirements pass technical quality checks.

Can I negotiate functional completion criteria if my game requirements are not fully measurable?

Negotiate functional completion criteria for game requirements using standard or strict workflow modes. This ensures all criteria are concrete, measurable, and fully aligned with the project requirements document before the generator phase begins.

When do I need to generate a formal contract for my Flutter Flame game?

Generate a formal contract for your Flutter Flame game during the transition from planning to development. This step orchestrates the generation of a binding agreement that mandates code quality, platform robustness, and functional test coverage.