metabase full app to modular embedding upgrade

Engineering Community

Skill notes

Execution contract

Follow the workflow steps in order — do not skip any step. Create the checklist first, then execute each step and explicitly mark it done with evidence. Each step's output feeds into the next, so skipping steps produces wrong migrations. If you cannot complete a step due to missing info or tool failure, you must: record the step as ❌ blocked, explain exactly what is missing / what failed, stop (do not proceed to later steps).

Required output structure

Your response should contain these sections in this order: Step 0: Metabase Version Detection Step 0.1: Migration Plan Checklist Step 1: Project Scan Step 2: iframe Analysis & Web Component Mapping

Evidence requirements

Step 0: Metabase version detected (source: Docker tag, env var, or user answer). Step 1: every matched file path, every iframe location, SSO endpoint, layout/head file, Metabase config variables. Step 2: per iframe — parsed URL, content type, ID, hash params, mapped web component with attributes. Step 3: the complete file-by-file change plan with exact old/new code. Step 4: per file — what was changed and exact diffs applied.

Architectural conformance

Follow the app's existing architecture, template engine, layout/partial system, code style, and route patterns. Do not switch paradigms (e.g., templates to inline HTML or vice versa). If the app has middleware for shared template variables, prefer that over duplicating across route handlers.

Performance

Maximize parallelism within each step. Use parallel Grep/Glob/Read calls in a single message wherever possible. Do not use sub-agents for project scanning — results need to stay in the main context for cross-referencing in later steps. Do not parse repo branches, commits, PRs, or issues.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@metabase · no license declared
Token usage
Heavy
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview metabase-full-app-to-modular-embedding-upgrade.preview
# Required output structure

1. **Step 0: Metabase Version Detection**
2. **Step 0.1: Migration Plan Checklist**
3. **Step 1: Project Scan**
4. **Step 2: iframe Analysis & Web Component Mapping**
5. **Step 3: Migration Plan**
6. **Step 4: Applied Code Changes**

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.