hybridindie

Scan a project, interview the user about unknowns, and generate a complete AI harness (Copilot + Claude + Opencode) with Constitutional Articles I–IX

Scan a project, interview the user about unknowns, and generate a complete AI harness (Copilot + Claude + Opencode) with Constitutional Articles I–IX

Scaffold a {{DB_PROVIDER}} SQL migration compliant with sql-standards.md

Scan E2E tests for no-op assertions and overly permissive checks that provide false confidence

Generate a contract test skeleton for a backend or frontend service following TDD Article III

Triage hardcoded dates, AsyncMock misuse, cross-tier truncates, and envelope assertion bugs in the test suite

Scan a project, interview the user about unknowns, and generate a complete AI harness (Copilot + Claude + Opencode) with Constitutional Articles I–IX

Scaffold a {{DB_PROVIDER}} SQL migration compliant with sql-standards.md

Generate an image with ComfyUI from a text prompt

Show recent ComfyUI generation history

List available ComfyUI models, optionally filtered by type

Show execution progress for a ComfyUI job

Show ComfyUI queue status with running and pending jobs

Troubleshooting guide for ComfyUI MCP connection issues, model errors, workflow failures, and security warnings. Use when users encounter errors or unexpected behavior.

Create a ComfyUI workflow from a template

Knowledge about ComfyUI workflow API format, node connections, and common patterns. Use when helping users build, modify, or understand workflows.

Build or edit a Godot scene through the godot-mcp server — create/open a scene, add and position nodes, attach GDScript, add collision, then save and verify. Use when the user wants to scaffold or modify a Godot .tscn scene via godot-mcp. Triggers on "build a Godot scene", "add a node in Godot", "create a scene", "attach a script to a node", "set up a player scene", "edit the scene tree".

Connect to and drive a Godot editor through the godot-mcp server. Use at the start of any Godot task via godot-mcp — it teaches the toolset-gating model (enable a toolset before its tools exist), the dry_run/confirm safety convention, and how to verify the bridge. Triggers on "use godot-mcp", "drive Godot", "control the Godot editor", "godot-mcp tools aren't showing up", "unknown tool from godot", "set up godot-mcp".

Run, inspect, and debug a live Godot game through the godot-mcp server — play a scene in the editor, read the running scene tree, sample properties, simulate input, assert state, and diagnose errors. Use when the user wants to play-test, reproduce a bug, or debug runtime behavior in Godot via godot-mcp. Triggers on "play-test in Godot", "run the game and check", "simulate input in Godot", "why does my Godot game crash", "debug the running scene", "inspect the live game".