Loading...
Loading...
Found 171 Skills
Scaffold brand-new DatoCMS plugin projects with datocms-plugin-sdk and connect(). Use when users want to create a new plugin folder from scratch, bootstrap the Vite/React package structure, choose initial plugin surfaces such as field extensions, config screens, sidebars, pages, asset sources, or dropdown actions, and wire the first hook implementation. Prefer `datocms-plugin-builder` for edits to an existing plugin project.
Design or restyle DatoCMS plugins so they look and feel native to the DatoCMS UI. Use when users ask to make a plugin match the DatoCMS dashboard, polish plugin config screens, pages, sidebars, panels, modals, forms, tables, empty states, or overall plugin layout structure. This skill owns DatoCMS plugin design-system work, native-look restyling, and UI density or spacing cleanup. Prefer `datocms-react-ui` when a public component exists, and otherwise use raw React and CSS that reproduce DatoCMS spacing, typography, density, color, and interaction patterns without importing private CMS classes.
Modify existing DatoCMS plugins built with datocms-plugin-sdk and connect(). Use when users ask to patch or maintain an existing plugin project: config screen edits, hook additions, field extension tweaks, sidebar/page/outlet changes, validation updates, settings cleanup, dependency fixes, or other day-to-day plugin maintenance. Prefer `datocms-plugin-scaffold` when starting a new plugin from scratch.
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.
Bootstrap new Hugo sites with Sveltia CMS and Basecoat UI, or convert existing sites (any SSG or CMS) to Hugo + Sveltia CMS. Use this skill whenever the user mentions Hugo, Sveltia CMS, Decap CMS migration, TinaCMS migration, static site CMS setup, headless CMS for Hugo, or wants to add a content management interface to a Hugo site. Also trigger when converting WordPress, Jekyll, Eleventy, TinaCMS, or other sites to Hugo, or when setting up Git-based content management. Covers the full workflow from scaffolding through Cloudflare Pages deployment with GitHub OAuth authentication.
Patch, extend, or explain DatoCMS front-end integration code inside an existing web project (Next.js App Router, Nuxt, SvelteKit, Astro, plus React/Vue/Svelte component usage). Use for targeted, per-concern work — adding a draft mode endpoint, wiring Preview Links / Visual Editing flows, fixing Content Link overlays, tuning real-time preview updates/subscriptions, setting up cache-tag invalidation/revalidation flows (Next.js revalidateTag or CDN purge by tags), adding robots/sitemap wiring, or hooking up crawler-safe search integration. Also the go-to skill for framework component/hook wiring with react-datocms, vue-datocms, @datocms/svelte, and @datocms/astro: Image/SRCImage/datocms-image, StructuredText, VideoPlayer (React/Vue/Svelte), SEO/meta helpers (renderMetaTags/toHead/Seo), QuerySubscription/QueryListener realtime patterns, ContentLink components, and Site Search (React/Vue). Prefer this skill whenever the user is modifying a live codebase one concern at a time, asking a framework-specific API question, or mixing several front-end concerns in the same patch.
Build content-heavy sites with Git-backed TinaCMS. Provides visual editing for blogs, documentation, and marketing sites. Supports Next.js, Vite+React, and Astro with TinaCloud or Node.js self-hosting. Prevents 10 documented errors. Use when setting up CMS with non-technical editors or troubleshooting ESbuild compilation, module resolution, package manager compatibility, edge runtime limitations, or media upload timeouts.
Expert guidance on Webflow CMS architecture and best practices. Use when planning collections, setting up relationships, optimizing content structure, or troubleshooting CMS issues.
Generate Umbraco CMS installation scripts using the Package Script Writer CLI
Sveltia CMS Git-backed content management (Decap/Netlify CMS successor). 5x smaller bundle (300 KB), GraphQL performance, solves 260+ issues. Use for static sites (Hugo, Jekyll, 11ty, Gatsby, Astro, Next.js), blogs, docs, i18n, or encountering OAuth errors, TOML/YAML issues, CORS problems, content listing errors.
Craft CMS 5 front-end Twig development — atomic design, template architecture, component patterns, Vite buildchain. Covers the full site template surface: atoms, molecules, organisms, props/extends/block pattern, layout chains, view routing, content builders, image presets, Tailwind named-key collections, multi-brand CSS tokens, JavaScript boundaries (Alpine/DataStar/Vue), Vite asset loading. Triggers on: {% include ... only %}, {% embed %}, _atoms/, _molecules/, _organisms/, _views/, _builders/, _boilerplate/, component--variant.twig, _component--props.twig, image presets, Tailwind class collections, collect({}), utilities prop, multi-brand theming, data-brand, hero sections, card components, content builders, Matrix block rendering, craft.vite.script, vite.php, vite.config.ts, nystudio107, buildchain, asset loading, per-page scripts. Always use when creating, editing, or reviewing any Craft CMS front-end Twig template, component, layout, view, builder, or buildchain configuration.
Write programmatic Node.js or TypeScript scripts that drive the DatoCMS Content Management API using @datocms/cma-client, @datocms/cma-client-node, or @datocms/cma-client-browser — the code-first companion for content-heavy and automation work. Prefer this skill whenever the task needs real code for records, uploads, or project automation — including short mid-conversation asks like "publish them", "fix those slugs", "delete all drafts", or "bulk import this CSV", and longer checked-in scripts. Covers four areas: (1) content operations — create/update/delete/publish records, bulk import/export and CSV pipelines, pagination over large record sets, asset uploads from URL or local files with metadata, structured text and block payload edits; (2) environment and project governance — fork/promote environments, webhooks and build triggers, project settings and maintenance mode, scheduled publish/unpublish workflows, audit logs, usage analytics, subscription limits; (3) access control and typed flows — roles and API tokens, upload tracks and tags, generated CMA schema types for type-safe record operations; (4) schema and UI configuration when the user explicitly bypasses the migrations workflow or wants schema mutations embedded in a larger script — models, fields, blocks, saved filters, dashboard and schema menus, plugin install and configuration. For ordinary schema changes inside a project with a migrations workflow or a secondary environment, prefer `datocms-cli` migrations as the safe default; reach for this skill only when the user opts out or the mutation is part of a broader automation. Works for both one-off execution via `cma:call` / `cma:script` and checked-in `buildClient()` scripts for reusable or unattended code.