examples

This skill should be used when the user asks "show me a complete Payload example", "give me a working Payload blog", "Payload ecommerce example", "Payload auth-only API example", "Payload jobs worker example", "Payload multi-tenant example", or wants end-to-end scenario walkthroughs instead of isolated snippets.

Jump to install Review files

Repository: Agents-Store/opencode-plugins
Last source activity: October 3, 2026 at 23:16
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with an AI assistant

Copy this prompt into the AI assistant you're using.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/Agents-Store/opencode-plugins/tree/main/payloadcms-dev/.opencode/skills/examples.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Agents-Store/opencode-plugins --skill examples

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

name: examples
description: This skill should be used when the user asks "show me a complete Payload example", "give me a working Payload blog", "Payload ecommerce example", "Payload auth-only API example", "Payload jobs worker example", "Payload multi-tenant example", or wants end-to-end scenario walkthroughs instead of isolated snippets.

# PayloadCMS — Complete Examples Index of end-to-end scenario walkthroughs. Each scenario lives in `references/scenarios/` as a fully runnable reference — collections, hooks, access rules, frontend pages — copy/paste ready. | Scenario | What it shows | File | | --- | --- | --- | | Blog CMS | Posts with drafts, autosave, live preview, Lexical content, tags, categories, public frontend with ISR + revalidation | `references/scenarios/blog-cms.md` | | E-commerce product catalog | Products, variants via blocks, inventory, Stripe price IDs, customer auth, Resend confirmation email queued as a job | `references/scenarios/ecommerce-product-catalog.md` | | Auth-only API (headless) | User/role/permission model, custom endpoints, no admin UI for clients, JWT + API-key auth, rate-limited login | `references/scenarios/auth-only-api.md` | | Jobs worker | Background image resize on upload + nightly cleanup workflow + Vercel cron trigger | `references/scenarios/jobs-worker.md` | | Multi-tenant SaaS | `tenants` collection, `tenant`-scoped access on every collection, sub-domain routing, per-tenant settings global | `references/scenarios/multi-tenant-saas.md` | ## When to Use This Skill vs Others | Want | Use | | --- | --- | | Smallest reproducible example for one feature | This skill — open the right scenario file | | Reference for a specific method signature | `api-reference` | | Idiomatic patterns explained | `collections` / `fields` / `hooks` / `access-control` / `queries` | | Building 3rd-party plugins | `plugin-development` | | Why something is broken | `troubleshoot` | | Moving content from another CMS | `cms-migration` | ## Reading Order if You're New to Payload 1. `references/scenarios/blog-cms.md` — covers ~60% of typical Payload usage. 2. `references/scenarios/auth-only-api.md` — see auth + custom endpoints without admin distraction. 3. `references/scenarios/ecommerce-product-catalog.md` — fields composition, jobs, email. 4. `references/scenarios/multi-tenant-saas.md` — access control at scale. 5. `references/scenarios/jobs-worker.md` — background processing. Each scenario is self-contained — you can lift any single file into a fresh project and adapt.

View on GitHub

Back to search Back to installation

documents

This skill should be used when the user asks to "create the macstack folder", "set up project docs", "where do user cases live", "add a screen", "add a trigger", "standardize the project documents", "repair the macstack folder", "migrate docs into macstack", mentions `macstack/`, OVERVIEW, USER-CASES, UX-UI, AUTOMATION, HANDBOOK, OPEN-QUESTIONS, DECISIONS, the client inbox or the document log — and BEFORE any other skill reads or writes anything under `macstack/`. Defines the folder standard AND the document shape: layout, path resolution, ID spaces, the pointer bindings, the bullet-label form, the language rule, the immutability guardrails, rendering and migration.

2026-10-11

lint

This skill should be used when the user asks to "validate macstack.json", "lint macstack", "check the stack spec", "verify macstack.json integrity", "check the documents", "where are we", "what should I do next", "project status" — and after any skill of this plugin writes or edits macstack.json or a document under macstack/. Validates the spec against the JSON Schema and the referential-integrity rules, checks the document folder, and reports the same findings read-only as a status dashboard.

2026-10-11

admin-panel

This skill should be used when the user asks to "use the Vaultwarden admin API", "script the /admin panel", "disable or delete a Vaultwarden user", "reset a user's 2FA", "change Vaultwarden config", or mentions ADMIN_TOKEN or the VW_ADMIN cookie.

2026-10-07

View all from this repository

examples

Source facts

Install options

Install with an AI assistant

Review the source files

More from this repository

Install with an AI assistant

More from this repository