Craft Plugins

Original name

Original description

Index and router for plugin-specific Craft CMS 5 guidance — configuration, Twig API, PHP/programmatic API, migrations, deployment, and pitfalls for the third-party plugins this pack documents. This skill exists so a plugin task is discoverable regardless of altitude: front-end (Twig/styling), back-end (PHP, content migrations, events), content modeling, or deployment all route here. Triggers whenever a task names one of these plugins in ANY context — build, configure, style, render, query, import, migrate, deploy, translate, cache, or debug: Formie (forms, form builder, submissions, File Upload field, form in a migration, form notifications), SEOmatic (meta, sitemaps, JSON-LD, SEO field), Blitz (static/page caching, purge, refresh), Feed Me (import XML/JSON/CSV feeds, scheduled import), Imager-X (image transforms, srcset, optimizers), ImageOptimize (OptimizedImages field, responsive images), CKEditor (rich text field, nested entries), Sprig (reactive components, htmx), Element API (JSON API endpoints), Retour (redirects, 404 tracking), Navigation (nav menus, nodes), Hyper (link field), Colour Swatches (colour palette field), Password Policy (password rules, HIBP), Typogrify (typography filters), Cache Igniter (cache warming), Knock Knock (staging password), Elements Panel (debug toolbar, N+1), Sherlock (security scanning), Amazon SES (email transport, SES, SNS bounce), Embedded Assets (oEmbed assets), Timeloop (recurring dates), Vite (craft.vite.*, asset bundling). Always use when a task mentions one of these plugins by name, even when the work is PHP/migration/deployment rather than Twig — read references/<plugin>.md before implementing. Do NOT trigger for Craft core APIs with no plugin named (craftcms), front-end template architecture in general (craft-site), or content modeling in general (craft-content-modeling) — those skills cross-link here when a specific plugin is involved.