README.md- Add note on postinstall script to copy Claude folder

Author: srcdev

.claude/skills/index.md

@@ -26,6 +26,7 @@ Each skill is a single markdown file named `<area>-<task>.md`.
 ├── storybook-add-font.md       — add a new font to Storybook
 ├── testing-add-unit-test.md    — create a Vitest unit test with snapshots
 ├── testing-add-playwright.md   — create a Playwright visual regression test
+├── setup-postinstall.md             — automate nuxt prepare + Claude skills copy via postinstall so neither is forgotten after npm install
 ├── theming-override-default.md      — replace the entire default theme with a custom colour scale (full palette swap)
 ├── theming-partial-override.md      — override a specific token category (forms, buttons, colours) without a full theme replacement
 ├── colour-scheme-disable.md         — disable light/dark scheme support in a consumer app

.claude/skills/setup-postinstall.md

@@ -0,0 +1,45 @@
+# Automate nuxt prepare and Claude Skills with postinstall
+
+## Overview
+
+Prevent two common "forgot to run after install" problems in a consuming app:
+
+1. `nuxt prepare` — generates Nuxt type declarations. Skipping it causes TypeScript errors after install or package updates.
+2. `npm run setup:claude` — copies the latest `srcdev-nuxt-components` skills into `.claude/skills/srcdev-nuxt-components/`. Skipping it leaves Claude working from stale skill docs after a package update.
+
+A `postinstall` script runs both automatically after every `npm install`.
+
+## Steps
+
+### 1. Add the scripts to package.json
+
+```json
+"scripts": {
+  "setup:claude": "cp -r node_modules/srcdev-nuxt-components/.claude/skills .claude/skills/srcdev-nuxt-components",
+  "postinstall": "nuxt prepare && npm run setup:claude"
+}
+```
+
+### 2. Check whether your app needs an env flag for nuxt prepare
+
+Some apps set an env var to switch `nuxt.config.ts` behaviour when running outside the full dev server (e.g. `NUXT_STANDALONE=true`). Check your own `nuxt.config.ts` — if it gates any config behind such a variable, add it to the `postinstall` command:
+
+```json
+"postinstall": "NUXT_STANDALONE=true nuxt prepare && npm run setup:claude"
+```
+
+If your `nuxt.config.ts` has no such conditional, plain `nuxt prepare` is sufficient.
+
+### 3. Run once manually to bootstrap
+
+```bash
+npm run setup:claude
+```
+
+From this point on, `npm install` and `npm ci` trigger both steps automatically.
+
+## Notes
+
+- Skills land in `.claude/skills/srcdev-nuxt-components/` — safe to re-run without overwriting your own project's skills.
+- `postinstall` also fires on `npm ci`, so CI environments get the skills too if they have a `.claude/` directory in the project.
+- If you do not want `postinstall` running in CI, guard it: `"postinstall": "[ \"$CI\" = \"true\" ] || (nuxt prepare && npm run setup:claude)"`.

README.md

@@ -41,6 +41,19 @@ npm run setup:claude
 
 Skills are copied into `.claude/skills/srcdev-nuxt-components/` so they never conflict with or overwrite skills your own project defines. Re-running the script after a package update is safe.
 
+### Automate with postinstall (recommended)
+
+To ensure skills are always up to date and `nuxt prepare` is never forgotten, combine both into a `postinstall` script. npm runs this automatically after every `npm install`:
+
+```json
+"scripts": {
+  "setup:claude": "cp -r node_modules/srcdev-nuxt-components/.claude/skills .claude/skills/srcdev-nuxt-components",
+  "postinstall": "nuxt prepare && npm run setup:claude"
+}
+```
+
+> If your app uses a standalone env flag for `nuxt prepare` (e.g. `NUXT_STANDALONE=true`), include it in the `postinstall` command. This is project-specific — check your own `nuxt.config.ts` to confirm whether it is needed.
+
 ---
 
 ## Consumer App Configuration