WPManageNinja

Run a read-only quality gate across the whole Fluent Player docs site: verify file placement, link form, sidebar coverage, image integrity, convention compliance, and a clean production build. Produces a scored pass/fail checklist with offending paths, then offers fixes. USE FOR: audit the docs, check for broken links, verify doc conventions, run the quality gate, is everything consistent, lint the docs, pre-commit doc check, find docs missing from the sidebar, find orphaned images. DO NOT USE FOR: writing a new page (use write-fluentplayer-doc), editing content (use edit-fluentplayer-doc), or renaming/moving/deleting (use restructure-fluentplayer-docs).

Edit the CONTENT of an EXISTING Fluent Player documentation page in place (same slug, same file location) while preserving every site convention. Handles wording changes, new/removed sections, updated steps, and swapped or added screenshots. USE FOR: edit the X doc, update the wording on, add a section to, rewrite this page, fix the screenshot in, this doc is out of date, correct an error in the doc, expand the X guide. DO NOT USE FOR: creating a new page (use write-fluentplayer-doc), renaming the slug / moving to another category / deleting / reordering the sidebar (use restructure-fluentplayer-docs), or site-wide audits (use audit-fluentplayer-docs).

Perform STRUCTURAL operations on Fluent Player docs while protecting reference integrity: rename a doc (change its slug/URL), move a doc to another category, delete a doc, merge two docs, or reorder the sidebar. Always rewrites inbound links, moves the image folder, and updates guideGroups in config.mts. USE FOR: rename this doc, change the slug, change the URL of, move X to another category, delete this doc, remove this page, merge these two docs, reorder the sidebar, change the order of pages. DO NOT USE FOR: content/wording edits (use edit-fluentplayer-doc), creating a brand-new page (use write-fluentplayer-doc), or read-only audits (use audit-fluentplayer-docs).

Create a NEW Fluent Player end-user documentation page in this VitePress site, correctly placed in a category folder and wired into the sidebar (guideGroups in config.mts). Optionally converts pasted HTML or raw markdown source into a clean doc. USE FOR: add a doc, write a new doc page, create a doc for X, document this feature, write a guide for, new documentation page, turn this content into a doc, import this article. DO NOT USE FOR: editing an existing page (use edit-fluentplayer-doc), renaming/moving/deleting a page or reordering the sidebar (use restructure-fluentplayer-docs), site-wide quality checks (use audit-fluentplayer-docs), or non-docs markdown like README.md / CLAUDE.md.

Scaffold a new page in the FluentPlayer VitePress docs (fluentplayer-user-docs) following every repo convention: create the markdown file with frontmatter, create its screenshot directory + .gitkeep, wire it into the guideGroups sidebar in .vitepress/config.mts, apply (Pro) labels, and verify with docs:build. USE FOR: add a new doc page, create a guide page, new FluentPlayer doc, document a feature, add a page to the sidebar. DO NOT USE FOR: editing existing page prose, screenshots only (use fluentplayer-manage-screenshots), the changelog (use fluentplayer-changelog), or non-FluentPlayer repos.

Write and maintain the FluentPlayer docs changelog (guide/changelog.md in the fluentplayer-user-docs VitePress site). Scaffolds the page on first use (it is currently empty), then prepends a new reverse-chronological version section with user-facing Added/Changed/Fixed entries derived from release notes or git history. USE FOR: write a changelog entry, update the changelog, add a release note, document version X. DO NOT USE FOR: creating other doc pages (use fluentplayer-add-doc-page) or editing feature guides.

Add and standardize screenshots in the FluentPlayer VitePress docs (fluentplayer-user-docs). Enforces the repo convention: per-page images live at guide/public/<section>/<page>/<name>.webp, are referenced in markdown with the matching root-relative /guide/public/... path, use the .webp format, keep a .gitkeep in each directory, and have meaningful alt text. Validates that references resolve and finds orphans. USE FOR: add screenshots, embed images, fix image paths, standardize images, rename screenshots, broken image. DO NOT USE FOR: brand/logo assets (those live in root public/), creating a whole new page (use fluentplayer-add-doc-page), or non-image edits.

Pre-publish audit of the FluentPlayer VitePress docs (fluentplayer-user-docs). Runs docs:build to catch dead links, checks every guide page is wired into the guideGroups sidebar, flags Pro features missing a (Pro) label, verifies screenshot references resolve to files on disk (and finds orphans), catches known alt-text/spelling typos, and flags empty/placeholder pages. Produces a structured report and offers fixes. USE FOR: review the docs, lint docs, pre-publish check, audit the documentation, find broken links, check the sidebar, before committing docs. DO NOT USE FOR: creating a new page (use fluentplayer-add-doc-page) or writing content.

Master guide for authoring FluentCart documentation pages in the VitePress site at docs.fluentcart.com. Use whenever the user asks to write, draft, edit, expand, restructure, or proofread any markdown file under guide/. Covers project rules, voice and tone, formatting conventions, and routing to template specialists. Always consult before producing content.

Use when updating FluentCart documentation based on plugin source-code changes or a new plugin release version. Triggers on phrases like "update docs for v1.3.x", "sync docs to the latest plugin", "document the new <feature> in the plugin", "what changed in the plugin since <tag>", or any request that requires reading the FluentCart plugin's PHP/JS code at /Users/authlab-24/Desktop/fluent-cart before writing. Always pair with fluentcart-doc-writer (master) and the matching template specialist (integration, payment-gateway, product, settings, overview).

Specialist template for FluentCart third-party integration pages under guide/integrations/ — guides for connecting external services like FluentCRM, FluentCommunity, FluentBooking, FluentAffiliate, LearnDash, LifterLMS, Cloudflare Turnstile, Amazon S3, etc. Use when writing or editing any guide/integrations/<service>-integration.md file. Always pair with fluentcart-doc-writer for tone and universal rules.

Specialist template for FluentCart section index/overview pages — the index.md file that lives at guide/<section>/index.md and serves as the entry point for a major guide section (Store Management, Payments & Checkout, Product Types & Creation, etc.). Use when creating, editing, or restructuring any guide/<section>/index.md file. Always pair with fluentcart-doc-writer for tone and universal rules.

Specialist template for FluentCart payment gateway settings pages under guide/payments-checkout/connecting-payment-gateways/ — pages like stripe-settings.md, paypal-settings.md, square-settings.md, mollie-settings.md, paddle-settings.md, razorpay-settings.md, etc. Use when writing or editing any payment-gateway configuration page. Always pair with fluentcart-doc-writer for tone and universal rules.

Specialist template for FluentCart product creation and management pages under guide/product-types-creation/ — pages like creating-physical-products.md, creating-digital-products.md, creating-product-bundles.md, configuring-product-pricing.md, managing-subscriptions.md, inventory-management.md, etc. Use when writing or editing any product creation/management guide. Always pair with fluentcart-doc-writer for tone and universal rules.

Specialist template for FluentCart settings configuration pages (guide/settings-configuration/) AND analytics/reporting pages (guide/reporting-analytics/) — both share an "Accessing the X" + numbered H3 subsection pattern. Use when writing or editing pages like store-settings.md, payment-settings.md, cart-checkout-settings.md, sales-report.md, customer-report.md, etc. Always pair with fluentcart-doc-writer for tone and universal rules.

Create a NEW AzonPress documentation page in this VitePress site: place it in the right section folder, write frontmatter and body to house style, create its screenshot folder, wire it into the sidebar in .vitepress/config.js, and verify with docs:build. Also handles converting pasted HTML or draft markdown into a clean doc page. USE FOR: add a doc, write a new doc page, create a doc for X, document this feature, new documentation page, add a page to the sidebar, turn this draft into a doc, import this article. DO NOT USE FOR: editing an existing page (use azonpress-edit-doc), renaming/moving/deleting a page or reordering the sidebar (use azonpress-restructure-docs), release notes (use azonpress-changelog), screenshots on an existing page (use azonpress-manage-images), or site-wide checks (use azonpress-audit-docs).

Run a READ-ONLY quality gate across the whole AzonPress docs site: production build, sidebar coverage (pages that exist but are invisible), inbound-link integrity, image reference resolution and orphan folders, frontmatter completeness, and convention compliance. Produces a scored checklist with offending paths, then offers fixes. USE FOR: audit the docs, review the documentation, pre-publish check, lint the docs, check for broken links, find pages missing from the sidebar, find orphaned images, is everything consistent, check before committing. DO NOT USE FOR: writing a new page (use azonpress-add-doc), editing content (use azonpress-edit-doc), renaming or moving (use azonpress-restructure-docs), or release notes (use azonpress-changelog).

Add or maintain a release entry in the AzonPress docs changelog (guide/changelog.md). Prepends a new reverse-chronological version section using the site's exact ::: code-group format with 🆕 New Features / 🔧 Improvements / 🗑️ Removed / 🐛 Bug fixes tabs, rewriting raw release notes or git history into user-facing language. USE FOR: write a changelog entry, update the changelog, add release notes, document version X, we shipped a new release. DO NOT USE FOR: writing or updating feature guides (use azonpress-add-doc or azonpress-edit-doc), or site-wide checks (use azonpress-audit-docs).

Edit the CONTENT of an EXISTING AzonPress documentation page in place — same slug, same folder, same URL — while preserving every site convention. Handles rewording, adding or removing sections, updating steps for a new plugin version, and swapping screenshots. USE FOR: edit the X doc, update the wording on, add a section to, rewrite this page, this doc is out of date, fix an error in the doc, expand the X guide, update the doc for the new release. DO NOT USE FOR: creating a new page (use azonpress-add-doc), renaming a slug / moving between sections / deleting / reordering the sidebar (use azonpress-restructure-docs), release notes (use azonpress-changelog), or site-wide checks (use azonpress-audit-docs).

Add, replace, standardize, and audit screenshots in the AzonPress VitePress docs. Enforces the repo convention: per-page images live at guide/public/images/<section>/<slug>/, are referenced in markdown with the full root-relative /guide/public/images/... path, use .webp, and carry meaningful alt text. Verifies every reference resolves to a real file and reports orphans. USE FOR: add screenshots, embed images, replace an image, fix image paths, broken image, image not showing, standardize screenshots, rename screenshots, find unused images, check alt text. DO NOT USE FOR: brand assets like logos or the favicon (those are config-level, see CLAUDE.md), creating a whole new page (use azonpress-add-doc), or prose edits (use azonpress-edit-doc).

Perform STRUCTURAL operations on the AzonPress docs while protecting URL and reference integrity: rename a page (change its slug/URL), move a page to another section, delete a page, merge two pages, or reorder the sidebar. Always rewrites inbound links, moves the screenshot folder, and updates the sidebar in .vitepress/config.js. USE FOR: rename this doc, change the slug, change the URL of, move X to another section, delete this page, remove this doc, merge these two docs, reorder the sidebar, change the order of pages, reorganize the docs. DO NOT USE FOR: content or wording edits (use azonpress-edit-doc), creating a brand-new page (use azonpress-add-doc), or read-only checks (use azonpress-audit-docs).

Run a read-only quality gate across the whole Ninja Tables docs site: verify file placement, frontmatter, link form, sidebar coverage, image integrity, convention compliance, and a clean production build. Produces a scored pass/fail checklist with offending paths, then offers fixes. USE FOR: audit the docs, check for broken links, verify doc conventions, run the quality gate, is everything consistent, lint the docs, pre-commit doc check, find docs missing from the sidebar, find orphaned images. DO NOT USE FOR: writing a new page (use write-ninja-tables-doc), editing content (use edit-ninja-tables-doc), renaming/moving/deleting (use restructure-ninja-tables-docs), or checking plugin-feature documentation coverage (use check-ninja-tables-feature-coverage).

Given a plugin feature name or a "what's new in vX.Y.Z" prompt, determine whether it is already documented in guide/**, and which existing page(s) cover it, using the feature-memory index in references/. Reports the coverage decision so the caller can route to write-ninja-tables-doc (nothing covers it) or edit-ninja-tables-doc (something already does). USE FOR: is this feature documented, check doc coverage for a feature, what still needs docs, has the changelog entry for vX.Y.Z been written up, find undocumented Pro features. DO NOT USE FOR: actually writing or editing the page (use write-ninja-tables-doc / edit-ninja-tables-doc), structural changes (use restructure-ninja-tables-docs), or a general site health check (use audit-ninja-tables-docs).

Edit the CONTENT of an EXISTING Ninja Tables documentation page in place (same slug, same file location) while preserving every site convention. Handles wording changes, new/removed sections, updated steps, and swapped or added screenshots. USE FOR: edit the X doc, update the wording on, add a section to, rewrite this page, fix the screenshot in, this doc is out of date, correct an error in the doc, expand the X guide. DO NOT USE FOR: creating a new page (use write-ninja-tables-doc), renaming the slug / moving to another category / deleting / reordering the sidebar (use restructure-ninja-tables-docs), site-wide audits (use audit-ninja-tables-docs), or deciding whether a feature is documented at all (use check-ninja-tables-feature-coverage).

Perform STRUCTURAL operations on Ninja Tables docs while protecting reference integrity: rename a doc (change its slug/URL), move a doc to another category, delete a doc, merge two docs, or reorder the sidebar. Always rewrites inbound links, moves the image folder, and updates .vitepress/config.mts. USE FOR: rename this doc, change the slug, change the URL of, move X to another category, delete this doc, remove this page, merge these two docs, reorder the sidebar, change the order of pages. DO NOT USE FOR: content/wording edits (use edit-ninja-tables-doc), creating a brand-new page (use write-ninja-tables-doc), or read-only audits (use audit-ninja-tables-docs).

Create a NEW Ninja Tables end-user documentation page in this VitePress site, correctly placed in a category folder and wired into the hand-maintained nested sidebar in .vitepress/config.mts. Optionally converts pasted HTML or raw markdown source into a clean doc. USE FOR: add a doc, write a new doc page, create a doc for X, document this feature, write a guide for, new documentation page, turn this content into a doc, import this article. DO NOT USE FOR: editing an existing page (use edit-ninja-tables-doc), renaming/moving/deleting a page or reordering the sidebar (use restructure-ninja-tables-docs), site-wide quality checks (use audit-ninja-tables-docs), deciding whether a plugin feature is already documented (use check-ninja-tables-feature-coverage), or non-docs markdown like README.md / CLAUDE.md.

Read-only quality gate for the FluentCommunity docs site: run the production build, catch dead internal links, and scan for this repo's known content issues (unresolved [Screenshot: ...] placeholders, missing frontmatter descriptions, mangled acronym titles, remote-hosted images). Produces a ✅/⚠️/❌ report and proposes fixes but does NOT apply them. USE FOR: audit the docs, quality check, find broken links, what needs fixing, pre-release check, lint the docs. DO NOT USE FOR: creating a page (use write-fluentcommunity-doc), editing/fixing a specific page (use edit-fluentcommunity-doc), or renaming/moving/deleting pages (use restructure-fluentcommunity-docs).

Edit the content of an EXISTING FluentCommunity doc page in place — rewrite/expand/correct prose, add sections, swap in real screenshots, fix frontmatter — without moving, renaming, or deleting the file. Applies this repo house style and fixes known content issues as it goes. USE FOR: update this doc, revise/expand a page, fix wording, add a section, replace a [Screenshot: ...] placeholder, add a missing description, correct a mangled title. DO NOT USE FOR: creating a new page (use write-fluentcommunity-doc), renaming/moving/deleting/reordering pages (use restructure-fluentcommunity-docs), or a read-only site-wide audit (use audit-fluentcommunity-docs).

Rename, move, delete, merge, or reorder FluentCommunity doc pages while keeping the markdown file, its image folder, the sidebar in .vitepress/config.mts, and every inbound cross-link in sync. USE FOR: rename a page, change a slug/URL, move a page to another section, delete/remove a page, merge two pages, reorder the sidebar, regroup pages, add or collapse a sidebar sub-group. DO NOT USE FOR: creating a brand-new page (use write-fluentcommunity-doc), editing the prose/content of a page that stays put (use edit-fluentcommunity-doc), or a read-only audit (use audit-fluentcommunity-docs).

Create a NEW FluentCommunity end-user documentation page in this VitePress site, correctly placed in a section folder, wired into the hand-maintained sidebar in .vitepress/config.mts, with its image folder created and a clean build. USE FOR: add a doc, write a new doc page, create a guide for X, document this feature, scaffold a new article, turn these notes into a doc page. DO NOT USE FOR: editing an existing page (use edit-fluentcommunity-doc), renaming/moving/deleting/reordering pages (use restructure-fluentcommunity-docs), site-wide quality checks (use audit-fluentcommunity-docs), or non-doc markdown like README.md / CLAUDE.md.

Use this skill when the user asks to change the sidebar or top nav of the FluentBooking docs site — phrases like "add a sidebar entry for X", "reorder the sidebar", "rename the X sidebar group", "remove Y from the sidebar", "add to the nav bar", "change the search button text". All sidebar/nav config lives in docs/.vitepress/config.js — this skill respects the group ↔ folder quirks.

Use this skill when the user asks to document a new third-party integration for FluentBooking — phrases like "document the X integration", "add a doc for the X integration", "write integration docs for X", "create an integration page for X". Integration pages follow a strict, recurring template across 12 existing pages; this skill enforces that template.

Use this skill when the user asks to update, fix, revise, or extend an existing FluentBooking doc page — phrases like "update the X doc", "fix the X page", "revise X documentation", "add a section to X", "swap the screenshot in X", "rewrite the intro of X". Steers Claude to make minimal, on-tone edits without disturbing the existing structure.

Use this skill when the user asks to write a new FluentBooking documentation page — phrases like "write a doc for X", "add a documentation page for X", "document the X feature", "create a how-to for X", "new doc page for X". Guides Claude to produce a page that matches the existing 60 pages in tone, frontmatter, heading structure, image conventions, and sidebar wiring.

Create a new WP Social Ninja documentation page in this VitePress site the correct way — scaffold the Markdown with proper frontmatter and structure, place screenshots under the right image folder, and (critically) register the page in the sidebar in .vitepress/config.mts so it actually shows up. Use whenever adding, moving, or renaming a guide page under guide/**.

Run and verify this VitePress documentation site locally — start the dev server to eyeball rendered pages, or run a production build to confirm content changes don't break the site. Use after editing guide/** Markdown, the theme, or .vitepress/config.mts, or whenever asked to preview/run/build the docs.

Generate a pull request description based on the current branch's changes, using the project's PR template format.

Use when writing, updating, auditing, or reviewing any markdown inside the fluentcrm-user-docs VitePress project — touching docs/**/*.md, .vitepress/config.mts, sidebar entries, or image paths under docs/public/. Covers FluentCRM's voice/tone, frontmatter format, doc templates (concept/how-to/reference/integration/settings), image standards, product naming, sidebar updates, and the pre-publish quality checklist. Auto-load when the user says write/add/create/update/edit/audit/review a doc, a guide, a page, or asks about FluentCRM documentation style, tone, or structure.