Loading...
Loading...
Found 21 Skills
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.
Strapi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Strapi data.
Implement and improve the integration of Next.js and microCMS based on official information. Used for SDK setup, App Router data fetching and dynamic routes, cache/ISR/Webhook, Draft Mode, next/image implementation, and troubleshooting. For framework-independent API specifications and content design only, prioritize microcms-guide.
Storyblok integration. Manage Stories, Spaces. Use when the user wants to interact with Storyblok data.
Payload CMS v3 — TypeScript-native headless CMS with code-first collections, hooks, access control, Local/REST/GraphQL APIs, admin panel, and database adapter pattern
Explain core Contentful concepts and route users to the right implementation skill or documentation. Use when users ask conceptual questions, need terminology clarified, want help choosing between APIs (CDA/CMA/CPA/GraphQL), or need guidance on the Contentful MCP server. Also triggers on "Contentful 101", "which Contentful API", "how do I get started", "which skill should I use", "what does X mean in Contentful", "Contentful glossary", "CDA vs CPA", "CDA vs GraphQL", "how does Contentful work", "Contentful architecture", "explain environments", "what are aliases", "content model design", "headless CMS", "Contentful MCP", "MCP server", "set up MCP", "Remix Contentful", "Astro Contentful", "Gatsby Contentful", "SvelteKit Contentful", "Nuxt Contentful". Not for framework-specific implementation (contentful-nextjs), migrations (contentful-migration), personalization (contentful-personalization), or hands-on REST/GraphQL request examples (contentful-api).
Interactively design a Prepr CMS content model before anything is built. Use this skill whenever the user wants to figure out what their content model should be, says they want to design, plan, scope, or think through a schema, asks "how should I model X in Prepr", is starting a new Prepr project without a clear model in mind, is unsure whether something should be a model, component, or enum, or hands over a vague brief ("a marketing site", "a webshop", "our blog") that is not yet specific enough to build. For adding a field or one small model to an existing schema, the create-schema skill applies directly.
Hilft einer Person ohne Vorwissen zu entscheiden, ob ihre Webseite ein System zur Inhaltspflege (CMS) braucht, und richtet es bei Bedarf ein, z. B. Strapi in Docker auf dem Albatros-Server, erreichbar über einen sicheren Tunnel. Erklärt CMS mit dem Bild der Pinnwand. Nutze den Skill bei «CMS», «Strapi», «Inhalte selbst ändern ohne Code», «Blog», «News», «Veranstaltungen pflegen», «meine Kollegin soll Texte ändern können», «WordPress», «Admin-Bereich».
Orchestrator for the Hostinger Headless build flow — build and deploy a real website on the user's Hostinger account from a single prompt that names a domain. Holds the stage flow and the state contract, and drives each stage in sequence: connect, check state, refine, provision, content model, design, frontend, validate, deploy, done. Triggers: build a headless site for <domain>, build me a site, create a website, make me a website, deploy this to Hostinger, host this on Hostinger, connect this project to Hostinger.