storybloklisted

# Storyblok Engineering **Model:** Sonnet for schema authoring, script writing, component implementation, and debugging. Opus only when designing a content model from scratch — the taxonomy and content-type split is the one decision that is expensive to reverse once editors have made content. Storyblok engineering mechanics for Next.js and Astro. Brand, design-system, and project-specific compliance rules live in their own scoped skills and project rules — do not pull them in here. ## Read first, before writing anything Storyblok's own docs lag the shipping packages, sometimes by a major version. **When the docs and the installed package disagree, the package wins.** Check `node_modules/@storyblok/*/package.json` and the actual exports before following a doc example. Two of the traps in this skill exist because a doc sample was correct for the previous major. ## The one distinction everything hangs on Storyblok is two separate APIs with separate hosts, separate auth, and separate rate limits. Conflating them is the most common source of wasted time. | | Delivery (CDA) | Management (MAPI) | |---|---|---| | Host | `api.storyblok.com/v2/cdn` | `mapi.storyblok.com/v1/spaces/<id>` | | Purpose | Read content to render | Read/write schemas, stories, assets | | Auth | `token=` query param | `Authorization: <token>` header, **no `Bearer`** | | Tokens | public (published only) / preview (reads drafts) | personal access token | | Rate limit | tiered by query shape | ~6 req/s (pla