Storyblok Build Frontend
Use when generating frontend components for Storyblok blocks — writing, registering and validating the framework code that renders a space's content. E.g. "generate components for my blocks", "build an Astro + Storyblok landing page".
Install
/plugin marketplace add storyblok/agent-pluginThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add storyblok/agent-plugin --skill storyblok-build-frontendgit clone --depth 1 https://github.com/storyblok/agent-plugin.git /tmp/agent-plugin
mkdir -p ~/.claude/skills
cp -r /tmp/agent-plugin/skills/storyblok-build-frontend ~/.claude/skills/storyblok-build-frontendPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Build a Storyblok frontend Write 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. ## Inputs to collect **Which blocks to implement** — all of them, or a named subset. **Load `storyblok-use-storyblok` before the first Storyblok call.** It covers whether the MCP server or the CLI fits the job, names the skill carrying that tool's mechanics, and resolves the space and region. ## Where to start If the project is already detected, start at step 2 and use what is in hand — verified block field names, a section inventory in design order, design values, code-owned chrome, asset filenames, a story slug — re-deriving only what is missing and never re-modeling an existing schema; otherwise start at step 1. ## Workflow Do not finish with a step unaccounted for; if you skip one, say so and why. ``` - [ ] 1. Detect the project - [ ] 2. Establish the schema - [ ] 3. Load the setup and mechanics resources - [ ] 4. Generate the components - [ ] 5. Register the blocks - [ ] 6. Validate - [ ] 7. Report ``` ### 1. Detect the project Detect, do not assume. Inspect these in one pass: - **Project state** — first, is there a project here at all? A `package.json` in the working directory or an obvious app root decides it. This is the one detection that changes what every later step does:
Details
- Skill name
storyblok-build-frontend- Repository
- storyblok/agent-plugin
- Path
skills/storyblok-build-frontend/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Storyblok Build Frontend skill do?
Use when generating frontend components for Storyblok blocks — writing, registering and validating the framework code that renders a space's content. E.g. "generate components for my blocks", "build an Astro + Storyblok landing page".
How do I install the Storyblok Build Frontend skill?
Claude Code plugin: /plugin marketplace add storyblok/agent-plugin. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Storyblok Build Frontend popular?
It lives in storyblok/agent-plugin, which has 9 GitHub stars and 0 forks.
Related skills
Storyblok Build Plugin
9storyblok/agent-plugin
Use when extending Storyblok with plugins to enhance what editors can do — custom field inputs, Visual Editor panels, pages inside a space, integrations with external systems — including choosing, building, or deploying one. E.g. "editors need a map location picker", "build a field plugin", "deploy our plugin".
Storyblok Implement Figma
9storyblok/agent-plugin
Use when turning a Figma design into frontend components backed by Storyblok blocks. E.g. "figma to storyblok", "build this Figma design".
Storyblok Model Content
9storyblok/agent-plugin
Use when creating or modifying Storyblok components/blocks, content types, or fields, or modeling a content schema from multi-modal input. E.g. "model content for a blog", "add an image field to the teaser", "set up blocks for this landing page design".
Robodk Shape Builder
9RoboDK/RoboDK-Agent-Skills
Build parametric RoboDK visual components — primitives (box, sphere, cone), fixtures (table, pedestal, fence), and mechanisms (conveyor, linear rail, T-bot/H-bot gantry, 1/2/3-axis turntable/positioner) — using RoboDK's own bundled Components Add-in library instead of hand-rolled mesh geometry. Use whenever a station needs one of these shapes; prefer this over generating raw triangle meshes for anything it covers.
Canvas Modern Controls
5elipousson/canvas-modern-controls
Use before writing, editing, reviewing, or debugging any Power Apps canvas app source - .pa.yaml, screen/component .yml, or App Formulas .fx - so only current Modern* controls and property names are used (no Label@, Form@, Classic/*, Rectangle@, or pre-2026 Text@/Button@/TextInput@ versions). Also use for errors pasting YAML into Studio (PA1001, PA2108, PA2231), Studio's Accessibility checker, galleries, data grids, forms, toolbars, navigation, themes/App.Theme, Fluent icon names, responsive layout, and component definitions - even a one-control tweak or when the user only says "fix this Power
Robodk Addin
9RoboDK/RoboDK-Agent-Skills
Create, edit, validate, package, inspect and extract RoboDK Add-ins (also called RoboDK Apps) — a folder of Python action scripts plus AppConfig.ini that adds menus, toolbar buttons, context-menu entries and settings dialogs to RoboDK, distributed as an .rdkp package. Use this skill whenever the user mentions RoboDK add-ins, RoboDK apps, .rdkp files, AppConfig.ini, the AppLoader or Add-in Manager, roboapps/AppSettings, or wants to add a button, menu, toolbar action, right-click action or custom UI to RoboDK, package/unpack an .rdkp, inspect an existing Add-in, or automate a RoboDK workflow tha
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.