@iamdangavin/claude-skill-vitepress-docs 1.1.0 → 1.5.0

package/README.md

@@ -1,70 +1,2 @@
-# @iamdangavin/claude-skill-vitepress-docs
+# claude-skill-vitepress-docs
 
-A [Claude Code](https://claude.ai/code) skill that handles the full VitePress documentation lifecycle — setup, generation, screenshots, and sync.
-
-## Install
-
-```bash
-npx @iamdangavin/claude-skill-vitepress-docs
-```
-
-Installs the skill to `~/.claude/skills/vitepress-docs/`. Invoke it inside Claude Code with:
-
-```
-/vitepress-docs
-```
-
-## Modes
-
-### `setup`
-Wires up VitePress and GitHub Actions for GitHub Pages deployment. Handles custom domains and subdomains, PostCSS conflicts from parent projects (e.g. Next.js or Laravel roots), and generates the workflow file at the correct git root.
-
-### `generate`
-Analyzes a codebase and writes full documentation — user-facing guides, developer reference, or both. Proposes a doc structure for approval before writing, accumulates gaps for batch review, and generates placeholder screenshots for later capture.
-
-### `screenshot`
-Captures real browser screenshots via Playwright and replaces all placeholders. Supports auth-gated screens using in-session credentials (never written to disk). Rewrites surrounding doc prose to match each captured image.
-
-### `sync`
-Detects doc drift since the last sync via git diff or full re-analysis. Reports affected pages before making changes, updates only what drifted, and flags screenshots that may need recapture.
-
----
-
-## Features
-
-### Stack detection
-Auto-detects WordPress, Next.js, Node, and static sites before asking any questions. Confirms the finding with the user and accepts corrections.
-
-### WordPress support
-- Identifies project type: traditional theme, block theme, headless WP, plugin, or full site
-- Asks about page builder (Gutenberg, Elementor, Divi, ACF Blocks)
-- Auto-suggests the active theme or plugin from scanning `wp-content/`
-- Handles being invoked from the WP install root — correctly scopes everything to the theme or plugin folder
-- Accepts multiple focus paths (e.g. a theme + a plugin that work together)
-
-### Multi-path and token scope
-- **Single path:** analysis strictly isolated to that directory — WP core, other themes, and other plugins are never read
-- **Multiple paths:** cross-reading allowed only between declared paths; nothing outside the declared set is touched
-- Each path must be its own git repository — the skill halts with a clear message if `.git` is missing from any path
-
-### Git root awareness
-Detects `.git` at the exact focus path rather than walking up to parent folders. Correctly handles the common pattern where the git repo lives inside a theme or plugin subfolder of a larger WP install. The GitHub Actions workflow is always placed at the correct git root, even when docs live deeper inside it.
-
-### Manifest
-Tracks every doc page alongside its source file mappings, screenshot placeholder status, and a sync hash. Local-only (`.gitignore`d) — each environment generates its own. Used by `screenshot` and `sync` modes to know precisely what needs updating.
-
-### Deployment
-- Generates a GitHub Actions workflow scoped to the correct git root per path
-- Supports push-to-branch, tag-based (`v*`), and manual-only triggers
-- Uses `actions/upload-pages-artifact` + `actions/deploy-pages`
-- Always includes `workflow_dispatch` for manual deploys
-
----
-
-## Updating
-
-```bash
-npx @iamdangavin/claude-skill-vitepress-docs
-```
-
-Re-running the install command always pulls the latest version.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamdangavin/claude-skill-vitepress-docs",
-  "version": "1.1.0",
+  "version": "1.5.0",
   "description": "Installs the vitepress:docs Claude Code skill — VitePress docs setup, generation, screenshots, and sync.",
   "type": "module",
   "bin": {
@@ -17,5 +17,8 @@
     "vitepress",
     "docs"
   ],
-  "license": "MIT"
+  "license": "MIT",
+  "publishConfig": {
+    "access": "public"
+  }
 }

package/skill/SKILL.md

@@ -76,6 +76,8 @@ Add this line if not already present:
 
 Use AskUserQuestion for each choice below. For freeform text inputs (repo URL, domain name, docs path) ask as plain text immediately after the relevant choice is made.
 
+**Multiple focus paths:** if more than one path was established in Step 0, ask Q2 through Q6 once per path — fully completing all questions for the first path before starting the second. Never present questions for two paths at the same time.
+
 **Q1 — VitePress status:**
 - header: "VitePress"
 - question: "Is VitePress already installed in this project?"
@@ -83,7 +85,14 @@ Use AskUserQuestion for each choice below. For freeform text inputs (repo URL, d
   - "Already installed"
   - "Starting from scratch"
 
-**Q2 — Docs folder** (plain text): Ask — "Where do the docs live (or where should they go)? e.g. `docs/` at project root, or the repo root itself."
+**Q2 — Docs folder:**
+- header: "Docs location"
+- question: "Where should the docs folder be created? I found your repo at `[GIT_ROOT_PATH]`."
+- options:
+  - "Here → `[GIT_ROOT_PATH]/docs/`"
+  - "Somewhere else — I'll type the path"
+
+If "Somewhere else": ask as plain text — "What path should I use? (Full path or relative to `[GIT_ROOT_PATH]`)"
 
 **Q3 — GitHub repo** (plain text): Ask — "What is the GitHub repo? (full URL or `owner/repo`)"
 
@@ -385,7 +394,25 @@ This matters because the GitHub Actions workflow file must go in `.github/workfl
 
 **Q3 — Codebase root** (plain text): Ask — "Where is the codebase root? (Press enter to use the current directory.)" — **Skip for WordPress; already established by WP-Q6.**
 
-**Q4 — Docs output** (plain text): Ask — "Where should docs be written? (Default: `docs/` inside [FOCUS_PATH].)" — For WordPress, default to `docs/` inside the theme/plugin folder from WP-Q6, not the WP install root.
+**Q4 — Docs output:** Before asking, check whether `setup` has already been run by looking for `.vitepress/config.mjs` anywhere inside the focus path:
+
+```bash
+find FOCUS_PATH -name "config.mjs" -path "*/.vitepress/*" 2>/dev/null
+```
+
+**If found:** docs location is already established — skip this question, infer the docs folder from the found path, and tell the user: "I found an existing VitePress config at `[PATH]` — using that as the docs folder."
+
+**If not found:** ask:
+
+- header: "Docs location"
+- question: "Where should the docs folder be created? I found your repo at `[GIT_ROOT_PATH]`."
+- options:
+  - "Here → `[GIT_ROOT_PATH]/docs/`"
+  - "Somewhere else — I'll type the path"
+
+If "Somewhere else": ask as plain text — "What path should I use? (Full path or relative to `[GIT_ROOT_PATH]`)"
+
+Always show the full resolved path — never use abstract terms like "project root."
 
 **Q5 — Skip anything:**
 - header: "Exclusions"