opus-deployment-guide_skill

Overview

This skill documents deployment options for Opus-generated C# code in the Antigravity IDE and how to place NinjaTrader 8 strategies into the project and NinjaTrader bin. It presents three deployment paths—MCP Bridge (fully automated), Haiku handoff (fast, semi-automated), and manual file operations (fallback). The guide gives setup steps, decision criteria, costs, and verification steps for each option.

How this skill works

The skill explains what to inspect and execute after Opus generates a full strategy file. It checks for an MCP delegation_bridge to call_gemini_flash() for automatic Gemini Flash deployments, describes copying Opus output into Claude Code CLI to spawn Haiku for deployment, and outlines manual save/compile/update steps when automation is unavailable. It includes quick tests and troubleshooting for MCP, Haiku, and manual failures.

When to use it

• Use MCP Bridge when MCP is configured, you deploy frequently, and want near-zero cost and zero manual effort.
• Use Haiku handoff when MCP is unavailable but Claude Code CLI (Anthropic) is running and you accept a short copy/paste step.
• Use Manual file operations as an emergency fallback or for learning, offline, or air-gapped environments.
• Switch options based on availability: MCP → Haiku → Manual in that priority order.
• Choose manual when you need full control, to debug, or to verify compilation step-by-step.

Best practices

• Test each deployment option once so you understand the workflow and recovery path.
• Prefer Option 1 (MCP Bridge) for production: set GEMINI_API_KEY and monitor the delegation_bridge.
• Always verify files in both the project repo and NinjaTrader bin after deployment.
• Update CHANGELOG.md as part of every deployment to keep a clear history.
• Keep Claude Code CLI running and check Anthropic credits if relying on Haiku fallback.

Example use cases

• Automated CI deployment of UniversalORStrategyV8_9_MOMO.cs to project and NinjaTrader bin using call_gemini_flash().
• Quick 2-minute handoff: copy Opus output into Claude Code CLI to let Haiku deploy when MCP isn’t configured.
• Emergency offline deployment: save files manually to project and NinjaTrader folders, compile, and update CHANGELOG.
• Development loop: manual saves and sandbox testing for debugging large strategy changes before automating.
• Cost comparison planning: evaluate savings when moving frequent deploys from manual to MCP Bridge.