[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZJ7PE32M20CVEP7RC3J6J":3,"skill-same:01M72ZJ7PE32M20CVEP7RC3J6J":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M72ZJ7PE32M20CVEP7RC3J6J","gds-test-framework",null,"Initialize game test framework for Unity, Unreal, or Godot. Use when the user says \"test framework\" or \"set up testing\"","developAgent\u002Fbmad-start","developAgent","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F264530239?v=4","01M71J8X6CY24V5ZZHFGETRMSW","01M71J8X739FS28DGQAAY7V4QR",1,"MIT","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.windsurf\u002Fskills\u002Fgds-test-framework\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: gds-test-framework\ndescription: 'Initialize game test framework for Unity, Unreal, or Godot. Use when the user says \"test framework\" or \"set up testing\"'\n---\n\n# Game Test Framework Setup\n\n**Workflow ID**: `gds-test-framework`\n**Version**: 1.0 (BMad v6)\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Goal\n\nInitialize a production-ready game test framework for Unity, Unreal Engine, or Godot projects. This workflow scaffolds the complete testing infrastructure including unit tests, integration tests, and play mode tests appropriate for the detected game engine.\n\n## Role\n\nYou are a Game QA Architect specializing in test infrastructure. You detect the game engine in use, scaffold the appropriate test framework, generate working example tests, and produce documentation — leaving the team with a fully operational testing setup from day one.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow detects the game engine and creates all necessary test infrastructure files directly in the game project.\n\n**Primary Output**: `{test_dir}\u002FREADME.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n\n**Knowledge Base References**:\n- `knowledge\u002Funity-testing.md`\n- `knowledge\u002Funreal-testing.md`\n- `knowledge\u002Fgodot-testing.md`\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\ntest_dir: \"{project-root}\u002Ftests\"    # Root test directory\ngame_engine: \"auto\"                  # auto | unity | unreal | godot\ntest_framework: \"auto\"               # auto | gut (godot) | unity-test-framework | unreal-automation\n```\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\n**Critical:** Verify these requirements before proceeding. If any fail, HALT and notify the user.\n\n- Game project exists with identifiable engine\n- No test framework already configured (check for existing test directories)\n- Project structure is accessible\n\n---\n\n### Step 1: Detect Game Engine\n\n#### Actions\n\n1. **Identify Engine Type**\n\n   Look for engine-specific files:\n   - **Unity**: `Assets\u002F`, `ProjectSettings\u002FProjectSettings.asset`, `*.unity` scene files\n   - **Unreal**: `*.uproject`, `Source\u002F`, `Config\u002FDefaultEngine.ini`\n   - **Godot**: `project.godot`, `*.tscn`, `*.gd` files\n\n2. **Verify Engine Version**\n   - Unity: Check `ProjectSettings\u002FProjectVersion.txt`\n   - Unreal: Check `*.uproject` file for `EngineAssociation`\n   - Godot: Check `project.godot` for `config_version`\n\n3. **Check for Existing Test Framework**\n   - Unity: Check for `Tests\u002F` folder, `*.Tests.asmdef`\n   - Unreal: Check for `Tests\u002F` in Source, `*Tests.Build.cs`\n   - Godot: Check for `tests\u002F` folder, GUT plugin in `addons\u002Fgut\u002F`\n\n**Halt Condition:** If existing framework detected, offer upgrade path or HALT.\n\n---\n\n### Step 2: Scaffold Framework\n\n#### Unity Test Framework\n\n**Knowledge Base Reference**: `knowledge\u002Funity-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   Assets\u002F\n   ├── Tests\u002F\n   │   ├── EditMode\u002F\n   │   │   ├── EditModeTests.asmdef\n   │   │   └── ExampleEditModeTest.cs\n   │   └── PlayMode\u002F\n   │       ├── PlayModeTests.asmdef\n   │       └── ExamplePlayModeTest.cs\n   ```\n\n2. **Generate Assembly Definitions**\n\n   `EditModeTests.asmdef`:\n\n   ```json\n   {\n     \"name\": \"EditModeTests\",\n     \"references\": [\"\u003CGameAssembly>\"],\n     \"includePlatforms\": [\"Editor\"],\n     \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n     \"optionalUnityReferences\": [\"TestAssemblies\"]\n   }\n   ```\n\n   `PlayModeTests.asmdef`:\n\n   ```json\n   {\n     \"name\": \"PlayModeTests\",\n     \"references\": [\"\u003CGameAssembly>\"],\n     \"includePlatforms\": [],\n     \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n     \"optionalUnityReferences\": [\"TestAssemblies\"]\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   Edit Mode test example:\n\n   ```csharp\n   using NUnit.Framework;\n\n   [TestFixture]\n   public class DamageCalculatorTests\n   {\n       [Test]\n       public void Calculate_BaseDamage_ReturnsCorrectValue()\n       {\n           \u002F\u002F Arrange\n           var calculator = new DamageCalculator();\n\n           \u002F\u002F Act\n           float result = calculator.Calculate(100f, 1f);\n\n           \u002F\u002F Assert\n           Assert.AreEqual(100f, result);\n       }\n   }\n   ```\n\n   Play Mode test example:\n\n   ```csharp\n   using System.Collections;\n   using NUnit.Framework;\n   using UnityEngine;\n   using UnityEngine.TestTools;\n\n   public class PlayerMovementTests\n   {\n       [UnityTest]\n       public IEnumerator Player_WhenInputApplied_Moves()\n       {\n           \u002F\u002F Arrange\n           var playerGO = new GameObject(\"Player\");\n           var controller = playerGO.AddComponent\u003CPlayerController>();\n\n           \u002F\u002F Act\n           controller.SetMoveInput(Vector2.right);\n           yield return new WaitForSeconds(0.5f);\n\n           \u002F\u002F Assert\n           Assert.Greater(playerGO.transform.position.x, 0f);\n\n           \u002F\u002F Cleanup\n           Object.Destroy(playerGO);\n       }\n   }\n   ```\n\n---\n\n#### Unreal Engine Automation\n\n**Knowledge Base Reference**: `knowledge\u002Funreal-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   Source\u002F\n   ├── \u003CProjectName>\u002F\n   │   └── ...\n   └── \u003CProjectName>Tests\u002F\n       ├── \u003CProjectName>Tests.Build.cs\n       └── Private\u002F\n           ├── DamageCalculationTests.cpp\n           └── PlayerCombatTests.cpp\n   ```\n\n2. **Generate Module Build File**\n\n   `\u003CProjectName>Tests.Build.cs`:\n\n   ```csharp\n   using UnrealBuildTool;\n\n   public class \u003CProjectName>Tests : ModuleRules\n   {\n       public \u003CProjectName>Tests(ReadOnlyTargetRules Target) : base(Target)\n       {\n           PCHUsage = ModuleRules.PCHUsageMode.UseExplicitOrSharedPCHs;\n\n           PublicDependencyModuleNames.AddRange(new string[] {\n               \"Core\",\n               \"CoreUObject\",\n               \"Engine\",\n               \"\u003CProjectName>\"\n           });\n\n           PrivateDependencyModuleNames.AddRange(new string[] {\n               \"AutomationController\"\n           });\n       }\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   ```cpp\n   #include \"Misc\u002FAutomationTest.h\"\n\n   IMPLEMENT_SIMPLE_AUTOMATION_TEST(\n       FDamageCalculationTest,\n       \"\u003CProjectName>.Combat.DamageCalculation\",\n       EAutomationTestFlags::ApplicationContextMask |\n       EAutomationTestFlags::ProductFilter\n   )\n\n   bool FDamageCalculationTest::RunTest(const FString& Parameters)\n   {\n       \u002F\u002F Arrange\n       float BaseDamage = 100.f;\n       float CritMultiplier = 2.f;\n\n       \u002F\u002F Act\n       float Result = UDamageCalculator::Calculate(BaseDamage, CritMultiplier);\n\n       \u002F\u002F Assert\n       TestEqual(\"Critical hit doubles damage\", Result, 200.f);\n\n       return true;\n   }\n   ```\n\n---\n\n#### Godot GUT Framework\n\n**Knowledge Base Reference**: `knowledge\u002Fgodot-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   project\u002F\n   ├── addons\u002F\n   │   └── gut\u002F (plugin files)\n   ├── tests\u002F\n   │   ├── unit\u002F\n   │   │   └── test_damage_calculator.gd\n   │   └── integration\u002F\n   │       └── test_player_combat.gd\n   └── gut_config.json\n   ```\n\n2. **Generate GUT Configuration**\n\n   `gut_config.json`:\n\n   ```json\n   {\n     \"dirs\": [\"res:\u002F\u002Ftests\u002F\"],\n     \"include_subdirs\": true,\n     \"prefix\": \"test_\",\n     \"suffix\": \".gd\",\n     \"should_exit\": true,\n     \"should_exit_on_success\": true,\n     \"log_level\": 1,\n     \"junit_xml_file\": \"results.xml\"\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   `tests\u002Funit\u002Ftest_damage_calculator.gd`:\n\n   ```gdscript\n   extends GutTest\n\n   var calculator: DamageCalculator\n\n   func before_each():\n       calculator = DamageCalculator.new()\n\n   func after_each():\n       calculator.free()\n\n   func test_calculate_base_damage():\n       var result = calculator.calculate(100.0, 1.0)\n       assert_eq(result, 100.0, \"Base damage should equal input\")\n\n   func test_calculate_critical_hit():\n       var result = calculator.calculate(100.0, 2.0)\n       assert_eq(result, 200.0, \"Critical hit should double damage\")\n   ```\n\n---\n\n### Step 3: Generate Documentation\n\nCreate `tests\u002FREADME.md` with:\n\n- Test framework overview for the detected engine\n- Directory structure explanation\n- Running tests locally\n- CI integration commands\n- Best practices for game testing\n- Links to knowledge base fragments\n\n---\n\n### Step 4: Deliverables\n\n#### Primary Artifacts Created\n\n1. **Directory Structure** — Engine-appropriate test folders\n2. **Configuration Files** — Framework-specific config (asmdef, Build.cs, gut_config.json)\n3. **Sample Tests** — Working examples for unit and integration tests\n4. **Documentation** — `tests\u002FREADME.md`\n\n---\n\n## Output Summary\n\nAfter completing this workflow, provide a summary:\n\n```markdown\n## Game Test Framework Scaffold Complete\n\n**Engine Detected**: {Unity | Unreal | Godot}\n**Framework**: {Unity Test Framework | Unreal Automation | GUT}\n\n**Artifacts Created**:\n\n- Test directory structure\n- Framework configuration\n- Sample unit tests\n- Sample integration\u002Fplay mode tests\n- Documentation\n\n**Next Steps**:\n\n1. Review sample tests and adapt to your game\n2. Run initial tests to verify setup\n3. Use `test-design` workflow to plan comprehensive test coverage\n4. Use `automate` workflow to generate additional tests\n\n**Knowledge Base References Applied**:\n\n- {engine}-testing.md\n- qa-automation.md\n- test-priorities.md\n```\n\n---\n\n## Validation\n\nRefer to `checklist.md` for comprehensive validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n","# Game Test Framework Setup\n\n**Workflow ID**: `gds-test-framework`\n**Version**: 1.0 (BMad v6)\n\n## Conventions\n\n- Bare paths (e.g. `template.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fgds\u002Fconfig.yaml` and resolve:\n\n- `user_name`\n- `communication_language`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Goal\n\nInitialize a production-ready game test framework for Unity, Unreal Engine, or Godot projects. This workflow scaffolds the complete testing infrastructure including unit tests, integration tests, and play mode tests appropriate for the detected game engine.\n\n## Role\n\nYou are a Game QA Architect specializing in test infrastructure. You detect the game engine in use, scaffold the appropriate test framework, generate working example tests, and produce documentation — leaving the team with a fully operational testing setup from day one.\n\n---\n\n## WORKFLOW ARCHITECTURE\n\nThis workflow detects the game engine and creates all necessary test infrastructure files directly in the game project.\n\n**Primary Output**: `{test_dir}\u002FREADME.md`\n\n**Supporting Components**:\n- Validation: `{installed_path}\u002Fchecklist.md`\n\n**Knowledge Base References**:\n- `knowledge\u002Funity-testing.md`\n- `knowledge\u002Funreal-testing.md`\n- `knowledge\u002Fgodot-testing.md`\n\n\nLoad and resolve configuration from `{module_config}`:\n\n```yaml\noutput_folder: {from config}\nuser_name: {from config}\ncommunication_language: {from config}\ndocument_output_language: {from config}\ngame_dev_experience: {from config}\ndate: {system-generated}\n```\n\nResolve workflow variables:\n```yaml\ntest_dir: \"{project-root}\u002Ftests\"    # Root test directory\ngame_engine: \"auto\"                  # auto | unity | unreal | godot\ntest_framework: \"auto\"               # auto | gut (godot) | unity-test-framework | unreal-automation\n```\n\n---\n\n## EXECUTION\n\n### Preflight Requirements\n\n**Critical:** Verify these requirements before proceeding. If any fail, HALT and notify the user.\n\n- Game project exists with identifiable engine\n- No test framework already configured (check for existing test directories)\n- Project structure is accessible\n\n---\n\n### Step 1: Detect Game Engine\n\n#### Actions\n\n1. **Identify Engine Type**\n\n   Look for engine-specific files:\n   - **Unity**: `Assets\u002F`, `ProjectSettings\u002FProjectSettings.asset`, `*.unity` scene files\n   - **Unreal**: `*.uproject`, `Source\u002F`, `Config\u002FDefaultEngine.ini`\n   - **Godot**: `project.godot`, `*.tscn`, `*.gd` files\n\n2. **Verify Engine Version**\n   - Unity: Check `ProjectSettings\u002FProjectVersion.txt`\n   - Unreal: Check `*.uproject` file for `EngineAssociation`\n   - Godot: Check `project.godot` for `config_version`\n\n3. **Check for Existing Test Framework**\n   - Unity: Check for `Tests\u002F` folder, `*.Tests.asmdef`\n   - Unreal: Check for `Tests\u002F` in Source, `*Tests.Build.cs`\n   - Godot: Check for `tests\u002F` folder, GUT plugin in `addons\u002Fgut\u002F`\n\n**Halt Condition:** If existing framework detected, offer upgrade path or HALT.\n\n---\n\n### Step 2: Scaffold Framework\n\n#### Unity Test Framework\n\n**Knowledge Base Reference**: `knowledge\u002Funity-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   Assets\u002F\n   ├── Tests\u002F\n   │   ├── EditMode\u002F\n   │   │   ├── EditModeTests.asmdef\n   │   │   └── ExampleEditModeTest.cs\n   │   └── PlayMode\u002F\n   │       ├── PlayModeTests.asmdef\n   │       └── ExamplePlayModeTest.cs\n   ```\n\n2. **Generate Assembly Definitions**\n\n   `EditModeTests.asmdef`:\n\n   ```json\n   {\n     \"name\": \"EditModeTests\",\n     \"references\": [\"\u003CGameAssembly>\"],\n     \"includePlatforms\": [\"Editor\"],\n     \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n     \"optionalUnityReferences\": [\"TestAssemblies\"]\n   }\n   ```\n\n   `PlayModeTests.asmdef`:\n\n   ```json\n   {\n     \"name\": \"PlayModeTests\",\n     \"references\": [\"\u003CGameAssembly>\"],\n     \"includePlatforms\": [],\n     \"defineConstraints\": [\"UNITY_INCLUDE_TESTS\"],\n     \"optionalUnityReferences\": [\"TestAssemblies\"]\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   Edit Mode test example:\n\n   ```csharp\n   using NUnit.Framework;\n\n   [TestFixture]\n   public class DamageCalculatorTests\n   {\n       [Test]\n       public void Calculate_BaseDamage_ReturnsCorrectValue()\n       {\n           \u002F\u002F Arrange\n           var calculator = new DamageCalculator();\n\n           \u002F\u002F Act\n           float result = calculator.Calculate(100f, 1f);\n\n           \u002F\u002F Assert\n           Assert.AreEqual(100f, result);\n       }\n   }\n   ```\n\n   Play Mode test example:\n\n   ```csharp\n   using System.Collections;\n   using NUnit.Framework;\n   using UnityEngine;\n   using UnityEngine.TestTools;\n\n   public class PlayerMovementTests\n   {\n       [UnityTest]\n       public IEnumerator Player_WhenInputApplied_Moves()\n       {\n           \u002F\u002F Arrange\n           var playerGO = new GameObject(\"Player\");\n           var controller = playerGO.AddComponent\u003CPlayerController>();\n\n           \u002F\u002F Act\n           controller.SetMoveInput(Vector2.right);\n           yield return new WaitForSeconds(0.5f);\n\n           \u002F\u002F Assert\n           Assert.Greater(playerGO.transform.position.x, 0f);\n\n           \u002F\u002F Cleanup\n           Object.Destroy(playerGO);\n       }\n   }\n   ```\n\n---\n\n#### Unreal Engine Automation\n\n**Knowledge Base Reference**: `knowledge\u002Funreal-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   Source\u002F\n   ├── \u003CProjectName>\u002F\n   │   └── ...\n   └── \u003CProjectName>Tests\u002F\n       ├── \u003CProjectName>Tests.Build.cs\n       └── Private\u002F\n           ├── DamageCalculationTests.cpp\n           └── PlayerCombatTests.cpp\n   ```\n\n2. **Generate Module Build File**\n\n   `\u003CProjectName>Tests.Build.cs`:\n\n   ```csharp\n   using UnrealBuildTool;\n\n   public class \u003CProjectName>Tests : ModuleRules\n   {\n       public \u003CProjectName>Tests(ReadOnlyTargetRules Target) : base(Target)\n       {\n           PCHUsage = ModuleRules.PCHUsageMode.UseExplicitOrSharedPCHs;\n\n           PublicDependencyModuleNames.AddRange(new string[] {\n               \"Core\",\n               \"CoreUObject\",\n               \"Engine\",\n               \"\u003CProjectName>\"\n           });\n\n           PrivateDependencyModuleNames.AddRange(new string[] {\n               \"AutomationController\"\n           });\n       }\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   ```cpp\n   #include \"Misc\u002FAutomationTest.h\"\n\n   IMPLEMENT_SIMPLE_AUTOMATION_TEST(\n       FDamageCalculationTest,\n       \"\u003CProjectName>.Combat.DamageCalculation\",\n       EAutomationTestFlags::ApplicationContextMask |\n       EAutomationTestFlags::ProductFilter\n   )\n\n   bool FDamageCalculationTest::RunTest(const FString& Parameters)\n   {\n       \u002F\u002F Arrange\n       float BaseDamage = 100.f;\n       float CritMultiplier = 2.f;\n\n       \u002F\u002F Act\n       float Result = UDamageCalculator::Calculate(BaseDamage, CritMultiplier);\n\n       \u002F\u002F Assert\n       TestEqual(\"Critical hit doubles damage\", Result, 200.f);\n\n       return true;\n   }\n   ```\n\n---\n\n#### Godot GUT Framework\n\n**Knowledge Base Reference**: `knowledge\u002Fgodot-testing.md`\n\n1. **Create Directory Structure**\n\n   ```\n   project\u002F\n   ├── addons\u002F\n   │   └── gut\u002F (plugin files)\n   ├── tests\u002F\n   │   ├── unit\u002F\n   │   │   └── test_damage_calculator.gd\n   │   └── integration\u002F\n   │       └── test_player_combat.gd\n   └── gut_config.json\n   ```\n\n2. **Generate GUT Configuration**\n\n   `gut_config.json`:\n\n   ```json\n   {\n     \"dirs\": [\"res:\u002F\u002Ftests\u002F\"],\n     \"include_subdirs\": true,\n     \"prefix\": \"test_\",\n     \"suffix\": \".gd\",\n     \"should_exit\": true,\n     \"should_exit_on_success\": true,\n     \"log_level\": 1,\n     \"junit_xml_file\": \"results.xml\"\n   }\n   ```\n\n3. **Generate Sample Tests**\n\n   `tests\u002Funit\u002Ftest_damage_calculator.gd`:\n\n   ```gdscript\n   extends GutTest\n\n   var calculator: DamageCalculator\n\n   func before_each():\n       calculator = DamageCalculator.new()\n\n   func after_each():\n       calculator.free()\n\n   func test_calculate_base_damage():\n       var result = calculator.calculate(100.0, 1.0)\n       assert_eq(result, 100.0, \"Base damage should equal input\")\n\n   func test_calculate_critical_hit():\n       var result = calculator.calculate(100.0, 2.0)\n       assert_eq(result, 200.0, \"Critical hit should double damage\")\n   ```\n\n---\n\n### Step 3: Generate Documentation\n\nCreate `tests\u002FREADME.md` with:\n\n- Test framework overview for the detected engine\n- Directory structure explanation\n- Running tests locally\n- CI integration commands\n- Best practices for game testing\n- Links to knowledge base fragments\n\n---\n\n### Step 4: Deliverables\n\n#### Primary Artifacts Created\n\n1. **Directory Structure** — Engine-appropriate test folders\n2. **Configuration Files** — Framework-specific config (asmdef, Build.cs, gut_config.json)\n3. **Sample Tests** — Working examples for unit and integration tests\n4. **Documentation** — `tests\u002FREADME.md`\n\n---\n\n## Output Summary\n\nAfter completing this workflow, provide a summary:\n\n```markdown\n## Game Test Framework Scaffold Complete\n\n**Engine Detected**: {Unity | Unreal | Godot}\n**Framework**: {Unity Test Framework | Unreal Automation | GUT}\n\n**Artifacts Created**:\n\n- Test directory structure\n- Framework configuration\n- Sample unit tests\n- Sample integration\u002Fplay mode tests\n- Documentation\n\n**Next Steps**:\n\n1. Review sample tests and adapt to your game\n2. Run initial tests to verify setup\n3. Use `test-design` workflow to plan comprehensive test coverage\n4. Use `automate` workflow to generate additional tests\n\n**Knowledge Base References Applied**:\n\n- {engine}-testing.md\n- qa-automation.md\n- test-priorities.md\n```\n\n---\n\n## Validation\n\nRefer to `checklist.md` for comprehensive validation criteria.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n",{"name":5,"description":7},"main","1907bbe850fb749efa8b499b8da7ebb78a663519",".windsurf\u002Fskills\u002Fgds-test-framework",0,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start","https:\u002F\u002Fgithub.com\u002FdevelopAgent","2026-07-19 05:19:22",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add developAgent\u002Fbmad-start --skill gds-test-framework",{"tool":36,"command":37},"bunx","bunx skills add developAgent\u002Fbmad-start --skill gds-test-framework",{"tool":39,"command":40},"pnpm","pnpm dlx skills add developAgent\u002Fbmad-start --skill gds-test-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.windsurf\u002Fskills\u002Fgds-test-framework\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"checklist.md","REFERENCE","参考文档",2418,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.windsurf\u002Fskills\u002Fgds-test-framework\u002Fchecklist.md",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"customize.toml","OTHER","其他",1652,"https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002F.windsurf\u002Fskills\u002Fgds-test-framework\u002Fcustomize.toml",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M72ZN1RJ28HE3TG8CK5VMDZ0","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M72ZMZG4KQAFDEHG6KABQW8R","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fto-prd\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M72ZMWB9ZNA0Y5KGAHTW89E8","steve-jobs-perspective","史蒂夫·乔布斯(Steve Jobs)的思维框架与表达方式。基于Isaacson授权传记、Stanford演讲、\nLost Interview、D Conference系列、Make Something Wonderful、30+一手来源的深度调研，\n提炼6个核心心智模型、8条决策启发式和完整的表达DNA。\n用途：作为思维顾问，用乔布斯的视角分析产品、审视决策、提供反馈。\n当用户提到「用乔布斯的视角」「乔布斯会怎么看」「Jobs模式」「steve jobs perspective」时使用。\n即使用户只是说「帮我用乔布斯的角度想想」「如果乔布斯会怎么做」「切换到乔布斯」也应触发。","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fsteve-jobs-perspective\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M72ZMS3ZRQY9PCRPRVWY040M","pinme","Use this skill when the user mentions \"pinme\", or needs to upload files, store to IPFS, create\u002Fpublish\u002Fdeploy websites or full-stack services (including frontend pages, backend APIs, database storage, email sending, etc.), or any feature requiring backend database\u002Fserver support.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fpinme\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M72ZMPJHQ8NHC9WSH41DKV1F","pinme-share","Use this skill when the user wants to share, publish, or upload a static result through PinMe, especially by generating a static HTML share page for a PinMe project link, deployed full-stack app, Codex conversation summary, report, file, demo, or any 分享\u002F发布\u002F上传分享页 request that should end with `pinme upload`.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fpinme-share\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M72ZMM4QBVWMAW0YYM7H0Y6P","pinme-llm","Use this skill when a PinMe project (Worker TypeScript) needs to call OpenRouter-backed LLM APIs, including models, chat\u002Fcompletions, streaming, or OpenRouter web search. Guides AI to generate correct Worker TS code.","https:\u002F\u002Fgithub.com\u002FdevelopAgent\u002Fbmad-start\u002Fblob\u002Fmain\u002Fskills\u002Fpinme-llm\u002FSKILL.md",[],[]]