Loading...
Loading...
Found 8 Skills
Create a new CMS collection in Webflow with specified fields and relationships. Use when setting up blog posts, products, team members, portfolios, or other content types with custom fields.
Comprehensive Storyblok CMS development best practices for agency developers. Covers content modeling, SDK integration (React, Vue, Nuxt, Next.js), Visual Editor configuration, field plugins, API usage, internationalization, webhooks, and deployment patterns. Triggers on tasks involving Storyblok components, Visual Editor setup, content fetching, field plugin development, or headless CMS integration.
Expert guidance on creating Content Elements, Record Types, Page Types, and File Types using TYPO3 Content Blocks extension - the single source of truth for content modeling. Use when working with content-blocks, content-element, record-type, page-type, file-type, make:content-block, friendsoftypo3/content-blocks, irre.
Use when a task involves Prismic setup, repository configuration, content modeling, content type or slice changes, localization, previews, API tokens, webhooks, syncing local models, or reading Prismic documentation.
Load when building or restructuring a Quilium CMS site — architecture (page-types, content-types, ItemSets, global fields), YAML schemas, routes and detail pages, Liquid templates, porting an HTML prototype, images, the 404, the CLI loop (init, run, push, dictionary), and content from the shell (bulk imports, long fields edited as files). Triggers on "new Quilium site", "build this site", "design the architecture", "create a content type", "add a page type", "scaffold a template", "port this prototype", "detail page", "the links point to the wrong page", "images are missing", "the 404 doesn't work", "set up the project", "quilium init", "quilium push", "quilium content", "quilium item", "import this into the CMS", "the site doesn't render", "wysiwyg or repeat", "custom wysiwyg styles", "editor style palette". Load quilium-webmaster ALONGSIDE this skill — every build ends with a content phase (step 5). For content work on a site that already runs, quilium-webmaster alone is enough.
Operate Payload CMS (Next.js-native headless CMS) in repo workflows: bootstrap a Payload app, configure collections/globals, run local dev + migrations, and ship safe content-model changes. Use when the request mentions Payload CMS, payload config, collection schema, admin panel, or Next.js + headless CMS integration.
Build or change a Prepr CMS content model, either live in an environment through the MCP server or as JSON schema files in prepr/schema/ for Git sync. Use this skill whenever the user wants to create or modify a model, component, enum, or field, turn an agreed content model plan into a working schema, add a content type to an existing Prepr environment or schema files, or apply a fix from a schema review. For deciding what the model should be from a vague brief, the design-schema skill applies first.
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton implementation or a third-party singleton plugin (e.g. sanity-plugin-singleton-management) to the first-class API.