Inttegro integration builder

Route integration-building requests through Inttegro's live, versioned guidance instead of assembling an architecture from memory.

Start with the design tool

Search the connected Inttegro MCP tools for the exact name design_integration and call it before proposing architecture or code.
Pass every choice already stated by the user: integration goal, trusted server runtime, SDK preference, and checkout approach.
If choices are missing, let MCP elicitation collect them when the host supports it. Otherwise ask only for the missing choices and call design_integration with the completed arguments.
If the exact tool is unavailable, stop and report that the Inttegro MCP connection or commerce.mcp permission needs attention. Do not fabricate its result or silently replace it with generic advice.

Preserve plan_version, selections, recommended_path, required_operations, implementation_steps, documentation, test_plan, and agent_brief without inventing fields.
Treat the returned Studio links as the current API contract. Do not guess request fields, response shapes, lifecycle states, currencies, or minor-unit values.
Keep Inttegro credentials in trusted server-side secret storage. Never request an API key in this skill, send one to an MCP tool, or place one in browser, mobile, source, logs, or chat.
When the user authorizes implementation and repository access is available, inspect the application before applying the returned brief. Stop and report any mismatch between the brief, Studio contract, SDK, and repository.