@iamdangavin/claude-skill-vitepress-docs 1.6.0 → 1.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iamdangavin/claude-skill-vitepress-docs",
-  "version": "1.6.0",
+  "version": "1.9.0",
   "description": "Installs the vitepress:docs Claude Code skill — VitePress docs setup, generation, screenshots, and sync.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -105,6 +105,29 @@ If "Somewhere else": ask as plain text — "What path should I use? (Full path o
 
 If custom domain: ask as plain text — "What is the domain? (e.g. `docs.myapp.com`)"
 
+**Q4b — Search engine visibility:**
+- header: "Search visibility"
+- question: "Should these docs be visible to search engines and bots?"
+- options:
+  - "Yes — index these docs publicly"
+  - "No — block all search engines and bots"
+
+If "No": add the following to the VitePress config's `head` array and write a `robots.txt` to the public folder:
+
+`head` entry in `config.mjs`:
+```js
+head: [
+  ['meta', { name: 'robots', content: 'noindex, nofollow' }],
+]
+```
+If a `head` array already exists in the config, append to it — do not replace it.
+
+`DOCS_FOLDER/public/robots.txt`:
+```
+User-agent: *
+Disallow: /
+```
+
 **Q5 — Deploy trigger:**
 - header: "Deploy trigger"
 - question: "When should docs deploy?"
@@ -663,21 +686,49 @@ const formattedResponse = computed(() =>
 </style>
 ```
 
-**`.vitepress/theme/index.js`** — create if it doesn't exist, otherwise merge into existing:
+**Install `medium-zoom`** in the docs folder:
+
+```bash
+cd DOCS_FOLDER && npm install medium-zoom
+```
+
+**`.vitepress/theme/index.css`** — create if it doesn't exist, otherwise append:
+
+```css
+.medium-zoom-overlay {
+  z-index: 100;
+}
+
+.medium-zoom-image--opened {
+  z-index: 101;
+}
+```
+
+**`.vitepress/theme/index.js`** — create if it doesn't exist, otherwise merge into existing. This template includes both `ApiEndpoint` registration and medium-zoom. If `apiBase` was not collected, omit the `ApiEndpoint` lines:
 
 ```js
 import DefaultTheme from 'vitepress/theme'
+import { onMounted, watch, nextTick } from 'vue'
+import { useRoute } from 'vitepress'
+import mediumZoom from 'medium-zoom'
+import './index.css'
 import ApiEndpoint from '../components/ApiEndpoint.vue'
 
 export default {
   extends: DefaultTheme,
+  setup() {
+    const route = useRoute()
+    const initZoom = () => mediumZoom('.main img', { background: 'var(--vp-c-bg)' })
+    onMounted(initZoom)
+    watch(() => route.path, () => nextTick(initZoom))
+  },
   enhanceApp({ app }) {
     app.component('ApiEndpoint', ApiEndpoint)
   }
 }
 ```
 
-If the file already exists, add only the import and `app.component()` line — do not overwrite other registrations.
+If the file already exists, merge only the missing pieces — do not overwrite other registrations or setup logic.
 
 ### Step 6b — Update VitePress config sidebar
 
@@ -843,22 +894,29 @@ Use Playwright via Homebrew for all captures:
 import { chromium } from '/opt/homebrew/lib/node_modules/playwright/index.mjs';
 ```
 
-**⛔ Credential rule — NEVER write credentials to any file.** Do not write them to the capture script, a `.env` file, the manifest, a temp file, or anywhere else. Use them only as inline values passed directly to `page.fill()` calls in the script held in memory. Delete the script immediately after running it (`rm /tmp/screenshot.mjs`). If Playwright needs credentials in a reusable way, use a saved storage state file — but prompt the user for credentials fresh each time rather than caching them.
+**⛔ Credential rule — NEVER write credentials to any file.** Do not write them to a script file, `.env`, the manifest, or anywhere on disk. All Playwright scripts run as inline bash heredocs — credentials are passed directly as inline values to `page.fill()` calls within the heredoc and exist only in memory for the duration of the command. If Playwright needs credentials in a reusable way, use a saved storage state file — but prompt the user for credentials fresh each time rather than caching them.
 
 **For pages requiring auth:** if credentials were provided, drive a login flow before navigating to the target URL. If no credentials were given, skip auth-gated pages and list them in the final summary so the user can run screenshot mode again with credentials.
 
 **Standard capture script template:**
-```js
+
+Run inline via bash heredoc — no file is ever written to disk:
+
+```bash
+node --input-type=module << 'SCRIPT'
 import { chromium } from '/opt/homebrew/lib/node_modules/playwright/index.mjs';
 const browser = await chromium.launch({ channel: 'chrome', args: ['--no-sandbox'] });
 const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
 await page.goto('BASE_URL + captureUrl', { waitUntil: 'load', timeout: 60000 });
-await page.waitForTimeout(2000); // settle time for SPAs
+await page.waitForTimeout(SETTLE_MS);
 await page.screenshot({ path: 'OUTPUT_PATH', fullPage: false });
 await browser.close();
+SCRIPT
 ```
 
-Adjust settle time based on stack type. For WordPress/non-SPA sites use 500ms. For Next.js/SPA use 2000–4000ms.
+Adjust `SETTLE_MS` based on stack type: WordPress/non-SPA → `500`, Next.js/SPA → `2000`–`4000`.
+
+Never write the script to a file — always use the heredoc form above. This applies to auth flows too: inline all credential usage directly in the heredoc, never in a file.
 
 After each capture, display the image inline with the Read tool so the user can verify it before moving on.