Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.
Metabase data apps
This skill is split into parts, one per task. Each part is a guide in its own folder, together with the files only that task uses. Paths in this skill are relative to <skill-dir>, the directory holding this SKILL.md.
Read only the parts the task needs
Every guide is long, and its rules apply only to its own task. Pick the parts from the user's request, read those guides, and leave the others unread.
| The task | Read |
|---|---|
| Create, scaffold, or remove an app; the dev preview and its diagnostics feed; syncing an app to Metabase; an app-wide error | setup/setup.md |
| Change an existing app's UI without new data or writes: layout, theme, SDK components, how a chart renders | setup/setup.md, from Source conventions on |
Show Metabase data: tables, metrics, segments, measures, saved questions, filters, charts, the generated metabase.data.ts | semantic-layer/semantic-layer.md |
| More than one page: routes, links between pages, the current path | routing/routing.md |
| A write: a form, a button that creates, updates, or deletes, running an action | actions/actions.md |
Metabase marks the app Outdated, the user asks to migrate it, or npm run typecheck or npm run build fails after an SDK upgrade | migrate/migrate.md |
- Don't read
routing/routing.mdunless the app needs more than one page. - Don't read
actions/actions.mdunless the app writes data. - Don't read
migrate/migrate.mdunless the app needs migrating as the table says. An app Metabase doesn't mark Outdated, and that builds, needs no migration. - A task can span parts: a new app that shows a metric needs
setup/setup.md, thensemantic-layer/semantic-layer.md. Read each part when the work reaches it, not all of them up front. - When a guide points to another part or to a file under its own
references/, read it only when you reach that step.

