edit-fluentplayer-doc

스타0

포크0

업데이트2026년 6월 12일 11:40

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).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

WPManageNinja

WPManageNinja/fluentplayer-user-docs

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Edit a Fluent Player Doc

Modify an existing page in place. The slug, file path, and sidebar link stay the same. Canonical conventions live in CLAUDE.md — this skill is the procedure for safe edits.

Agent Behavior Rules

DO locate the exact file before editing and confirm it with the user.
DO preserve all conventions on every edit: full /guide/<category>/<slug> links, **term** bold (no inner spaces), no support boilerplate, "(Pro)" markers for Pro features.
DO keep the H1 as line 1 (or immediately after optional frontmatter); if the H1 display title changes, update the matching sidebar text in guideGroups (the link stays the same).
DO put any new/replacement images in the doc's existing image folder guide/public/<category>/<slug>/.
DO end on a green npm run docs:build.
DO NOT change the slug, rename, or move the file — that is restructure work.
DO NOT introduce relative links (./slug, ../slug) — always use full /guide/... paths.
DO NOT add closing support boilerplate; link [How to Get Support](/guide/support).
DO NOT touch unrelated docs.
DO Before editing, map the target doc's position in the site: which category folder it lives in, which sidebar group it belongs to, and which sections need updating — so every change matches the user journey.

Phase 1: Setup (Interactive)

1.1 Target page

Which doc? (title, slug, or URL)

Resolve to a file:

find guide -name '<slug>.md' | grep -v '/public/'

If ambiguous or not found, ask. Record TARGET_PATH, SLUG, CATEGORY.

1.2 The change

What should change? (new wording, add/remove a section, update steps, swap image…)

Record as CHANGE.

1.3 Images & title

Does this change involve images? and Does the page title (H1) change?

Record TOUCHES_IMAGES and TITLE_CHANGES.

1.4 Confirm

Parameter	Value
File	...
Change	...
Touches images	...
Title changes	...

Wait for confirmation.

Phase 2: Context

Read TARGET_PATH fully.
Read CLAUDE.md for conventions.
If TITLE_CHANGES: read .vitepress/config.mts and find the entry in guideGroups whose link matches /guide/<CATEGORY>/<SLUG> (or /guide/<SLUG> for flat items). Its text must be updated to match the new H1 (the link stays the same).
Read 1 neighbor doc in the same CATEGORY if matching house style for new content.

Phase 3: Procedure

1. EDIT     - Apply CHANGE to TARGET_PATH using Edit.
              Enforce conventions on touched lines: full /guide/... links, **term** bold,
              "(Pro)" markers, no boilerplate.
              Pro features: wrap with ::: info Pro feature callout.

2. IMAGES   - If TOUCHES_IMAGES: add/replace files in
              guide/public/<CATEGORY>/<SLUG>/ and update the
              ![alt](/guide/public/<CATEGORY>/<SLUG>/<file>.webp) refs.
              Remove image refs whose files you deleted.

3. SIDEBAR  - If TITLE_CHANGES: update the matching entry's "text" in guideGroups
              inside .vitepress/config.mts. Do NOT change its "link". Keep valid TypeScript.

4. BUILD    - npm run docs:build ; fix warnings; rebuild until clean.

Phase 4: Verify & Report

Report:

File edited: TARGET_PATH
Summary of what changed
Images touched? (added/replaced/removed)
Sidebar text updated? (yes/no — link unchanged)
Build: pass / fail

Quick Reference

Locate

File by slug:   find guide -name '<slug>.md' | grep -v '/public/'
Sidebar entry:  grep -n '/guide/<category>/<slug>' .vitepress/config.mts
Image folder:   guide/public/<category>/<slug>/

Formats (unchanged from site rules)

Cross-link:  [Text](/guide/<category>/<slug>)   (full path — never relative)
Image ref:   ![Alt](/guide/public/<category>/<slug>/<name>.webp)
Bold:        **term**                            (no inner spaces)
Pro callout: ::: info Pro feature
             <Feature> is available only with **FluentPlayer Pro**.
             :::

Key Principles

In place only — same slug, same path, same sidebar link.
Conventions survive edits — don't regress links/bold/boilerplate.
Title change ⇒ sidebar text change (link stays).
Images live in the doc's own folder.
Green build or it's not done.

이 저장소의 다른 Skills

같은 저장소

audit-fluentplayer-docs

WPManageNinja/fluentplayer-user-docs

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).

2026-06-120

restructure-fluentplayer-docs

WPManageNinja/fluentplayer-user-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).

2026-06-120

write-fluentplayer-doc

WPManageNinja/fluentplayer-user-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.

2026-06-120

fluentplayer-add-doc-page

WPManageNinja/fluentplayer-user-docs

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.

2026-06-050

fluentplayer-changelog

WPManageNinja/fluentplayer-user-docs

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.

2026-06-050

fluentplayer-manage-screenshots

WPManageNinja/fluentplayer-user-docs

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.

2026-06-050

name	edit-fluentplayer-doc
description	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).
license	MIT
compatibility	VitePress repo using guide/<category>/<slug>.md layout. Sidebar defined in .vitepress/config.mts (guideGroups const). Images stored at guide/public/<category>/<slug>/. Requires Node + npm to run docs:build.
metadata	{"project":"fluentplayer-user-docs","canonical-rules":"CLAUDE.md"}

Edit a Fluent Player Doc

Modify an existing page in place. The slug, file path, and sidebar link stay the same. Canonical conventions live in CLAUDE.md — this skill is the procedure for safe edits.

Agent Behavior Rules

DO locate the exact file before editing and confirm it with the user.
DO preserve all conventions on every edit: full /guide/<category>/<slug> links, **term** bold (no inner spaces), no support boilerplate, "(Pro)" markers for Pro features.
DO keep the H1 as line 1 (or immediately after optional frontmatter); if the H1 display title changes, update the matching sidebar text in guideGroups (the link stays the same).
DO put any new/replacement images in the doc's existing image folder guide/public/<category>/<slug>/.
DO end on a green npm run docs:build.
DO NOT change the slug, rename, or move the file — that is restructure work.
DO NOT introduce relative links (./slug, ../slug) — always use full /guide/... paths.
DO NOT add closing support boilerplate; link [How to Get Support](/guide/support).
DO NOT touch unrelated docs.
DO Before editing, map the target doc's position in the site: which category folder it lives in, which sidebar group it belongs to, and which sections need updating — so every change matches the user journey.

Phase 1: Setup (Interactive)

1.1 Target page

Which doc? (title, slug, or URL)

Resolve to a file:

find guide -name '<slug>.md' | grep -v '/public/'

If ambiguous or not found, ask. Record TARGET_PATH, SLUG, CATEGORY.

1.2 The change

What should change? (new wording, add/remove a section, update steps, swap image…)

Record as CHANGE.

1.3 Images & title

Does this change involve images? and Does the page title (H1) change?

Record TOUCHES_IMAGES and TITLE_CHANGES.

1.4 Confirm

Parameter	Value
File	...
Change	...
Touches images	...
Title changes	...

Wait for confirmation.

Phase 2: Context

Read TARGET_PATH fully.
Read CLAUDE.md for conventions.
If TITLE_CHANGES: read .vitepress/config.mts and find the entry in guideGroups whose link matches /guide/<CATEGORY>/<SLUG> (or /guide/<SLUG> for flat items). Its text must be updated to match the new H1 (the link stays the same).
Read 1 neighbor doc in the same CATEGORY if matching house style for new content.

Phase 3: Procedure

1. EDIT     - Apply CHANGE to TARGET_PATH using Edit.
              Enforce conventions on touched lines: full /guide/... links, **term** bold,
              "(Pro)" markers, no boilerplate.
              Pro features: wrap with ::: info Pro feature callout.

2. IMAGES   - If TOUCHES_IMAGES: add/replace files in
              guide/public/<CATEGORY>/<SLUG>/ and update the
              ![alt](/guide/public/<CATEGORY>/<SLUG>/<file>.webp) refs.
              Remove image refs whose files you deleted.

3. SIDEBAR  - If TITLE_CHANGES: update the matching entry's "text" in guideGroups
              inside .vitepress/config.mts. Do NOT change its "link". Keep valid TypeScript.

4. BUILD    - npm run docs:build ; fix warnings; rebuild until clean.

Phase 4: Verify & Report

Report:

File edited: TARGET_PATH
Summary of what changed
Images touched? (added/replaced/removed)
Sidebar text updated? (yes/no — link unchanged)
Build: pass / fail

Quick Reference

Locate

File by slug:   find guide -name '<slug>.md' | grep -v '/public/'
Sidebar entry:  grep -n '/guide/<category>/<slug>' .vitepress/config.mts
Image folder:   guide/public/<category>/<slug>/

Formats (unchanged from site rules)

Cross-link:  [Text](/guide/<category>/<slug>)   (full path — never relative)
Image ref:   ![Alt](/guide/public/<category>/<slug>/<name>.webp)
Bold:        **term**                            (no inner spaces)
Pro callout: ::: info Pro feature
             <Feature> is available only with **FluentPlayer Pro**.
             :::

Key Principles

In place only — same slug, same path, same sidebar link.
Conventions survive edits — don't regress links/bold/boilerplate.
Title change ⇒ sidebar text change (link stays).
Images live in the doc's own folder.
Green build or it's not done.