All authors
Claude Skills by storyblok
github.com/storyblok6 skills0 installs8 views
- Storyblok Build FrontendWrite the frontend code that renders a Storyblok space's blocks: one component per block, registered with the framework's Storyblok integration, styled with the project's own mechanism, and validated against a build and a rendered page.Votes: 0GitHub stars: 2
- Storyblok Implement Figma1. **Figma URL** (required) — or a `fileKey` + `nodeId` pair. 2. Whether a story should be created — see step 6. Do not ask up front; offer it once the blocks exist.Votes: 0GitHub stars: 2
- Storyblok Model ContentDesign a content model and set it up in a Storyblok space: components (nestable blocks and content types), component groups, and datasources. This skill **changes the space schema**. It never edits story content — with one narrow, explicitly-approved exception: a component rename may pass `update_content: true` so existing story references follow the new name (see the rename notes below). It can also delete components, datasources, and datasource entries — deletions are **destructive**: alway...Votes: 0GitHub stars: 2
- Storyblok Use CliResolve the binary once: `node_modules/.bin/storyblok`, else the package manager's exec (`pnpm exec`, `npx`), else a global `storyblok`. A one-off in a project that does not depend on it can run through `pnpm dlx storyblok` or `npx -y storyblok` — no install needed.Votes: 0GitHub stars: 2
- Storyblok Use Mcp`space_id` (integer) is required on nearly every operation, and it is all you need — the server derives the region from it.Votes: 0GitHub stars: 2
- Storyblok Use StoryblokTake stock, pick the tool, pick the skill. In that order. Load no other skill until §1 has run and §2 has picked the tool — otherwise you are working through a tool you never chose. What you check along the way — tools, sessions, config, project files — decides how you work; it is not news for the user. Mention it only when the user has to act on it or needs it to trust the result.Votes: 0GitHub stars: 2