Integration Decision Tree

This page is the authority for choosing an integration path.

If you only remember one rule, remember this:

• use generator-sdk for platform capabilities
• use generator-workbench for the official shell
• use Generator Runtime Contract for host/runtime protocol
• use MCP + skill for AI-assisted development

Five Questions To Answer First

1. Do you need platform capabilities such as login, credits, billing, export, or Studio import?
2. Do you want the official shell or your own custom shell?
3. Does the generator need both full and embed behavior?
4. Will you build manually or through AI-assisted workflow?
5. Does the generator need template-page support?

Decision Flow

Recommended Combinations

Option 1: SDK Only

Use this when:

• you already have a strong custom shell
• you only need platform APIs
• you want to control all shell behavior yourself

Read next:

• SDK Overview
• Installation
• Authentication

Option 2: SDK + Workbench

Use this when:

• you want the fastest path to a standard generator shell
• you want platform-consistent login, export, billing, and template shell behavior
• you do not want to rebuild the host frame

Read next:

• Generator Workbench
• Runtime Contract

Option 3: SDK + Runtime Contract + Custom Shell

Use this when:

• you need a non-standard product shell
• you need full control over embedding behavior
• your layout cannot fit the official shell

Option 4: AI Path

Use this when:

• you want AI to scaffold or refactor the generator
• you want documentation lookup through MCP
• you want the output to converge to the platform-standard model

Read next:

• AI Vibe Coding Workflow
• Generator Onboarding

When Runtime Contract Becomes Required

Treat Generator Runtime Contract as required when:

• the generator must run in both full and embed modes
• the host mounts canvas and parameters separately
• template-page scenarios exist
• you want long-term standardization instead of partial compatibility

Common Mistakes

• Treating generator-sdk as if it were a shell
• Treating generator-workbench as if it replaced runtime logic
• Treating MCP as a production runtime dependency
• Claiming “standard integration complete” after only partial SDK or bridge work

Next Step

• Read Developer Journey for the full delivery sequence.
• Read Guide Overview if you still need the page map.