payload-plugins

Use when a developer adds a new page block to this CMS and needs to wire up semantic search indexing for it. Triggers on: "add block to search", "index new block", "wire up extractor", or any mention of a new block needing search support.

Fallback skill for when the uploadImage MCP tool fails because it cannot read a local file path (e.g., Payload is hosted on Vercel and cannot access the developer's local filesystem). Use ONLY after receiving such an error from uploadImage tool from payload mcp — not proactively. Stages one or more files through Vercel Blob as a temporary transfer layer to work around the local filesystem access limitation.

Use when working in a Next.js project with `cacheComponents: true` in next.config — writing or reviewing React Server Components, adding `'use cache'`, configuring `cacheLife()`/`cacheTag()`, invalidating with `updateTag()`/`revalidateTag()`, debugging Partial Prerendering, or deciding static vs cached vs dynamic boundaries.

Use when adding or publishing a new plugin package in this monorepo, or when CI fails with "cannot publish over previously published versions" after a first manual publish.

Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes.

Use this skill for anything involving the payload-plugin-ab Payload CMS plugin. Triggers include: installing payload-plugin-ab, configuring its options, asking what it does, troubleshooting errors, upgrading versions, setting up A/B testing, configuring storage adapters, writing Next.js middleware for variant routing, setting up analytics tracking, and answering questions about its API. If the user mentions "payload-plugin-ab", "A/B testing plugin", "variant routing", "ab testing", "abTestingPlugin", or "variant manifest" in any Payload CMS context, always use this skill.

Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Use this skill for anything involving the payload-plugin-presets Payload CMS plugin. Triggers include: installing payload-plugin-presets, configuring its options, asking what it does, troubleshooting errors, upgrading versions, writing blocks or fields that use it, and answering questions about its API. If the user mentions "payload-plugin-presets", "presets plugin", "block presets", "reusable presets", "save preset", or "apply preset" in any Payload CMS context, always use this skill.

Use this skill for anything involving the payload-plugin-comments Payload CMS plugin. Triggers include: installing payload-plugin-comments, configuring its options, asking what it does, troubleshooting errors, upgrading versions, writing collections or fields that use it, and answering questions about its API. If the user mentions "payload-plugin-comments", "comments plugin", "field-level comments", "document comments", or "@mention" in any Payload CMS context, always use this skill.

Use this skill for anything involving the payload-plugin-scheduling Payload CMS plugin. Triggers include: installing payload-plugin-scheduling, configuring its options, asking what it does, troubleshooting errors, upgrading versions, setting up cron jobs for it, and answering questions about its API. If the user mentions "payload-plugin-scheduling", "schedule publication", "scheduled publish", "scheduled publishing", or "schedule plugin" in any Payload CMS context, always use this skill.