From cookbook
Updates recipes already installed in a repo to the plugin's current versions — reads .recipes/lock.json, diffs locked versions against the catalog, and applies each change as a semantic 3-way merge (old template vs. the repo's current file vs. new template) on a branch with a PR, never blind-overwriting local adaptations. Use when asked to update/upgrade recipes, sync a repo with new recipe versions, or after the recipe catalog ships a new release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cookbook:update-recipesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The lock is what makes updates possible: it records which recipe **version**
The lock is what makes updates possible: it records which recipe version rendered each file and with which answers. An update is a merge, not a re-install — the repo's copy is canonical-for-that-repo, and local adaptations are usually deliberate. The model is Copier-style: re-apply the new version by reasoning about three texts, and let a human approve the result via PR.
<target>/.recipes/lock.json → for each entry:
name, locked version, tier, answers. No lock → stop; this repo needs
adopt-recipes first.${CLAUDE_PLUGIN_ROOT}/recipes/<name>/recipe.yaml's version. Equal →
skip. Report the update set before touching anything.chore/update-recipes) from the
default branch; never update on the default branch directly.provides.files, filtered by the locked tier and when conditions):
git -C ${CLAUDE_PLUGIN_ROOT} show <locked-tag-or-rev>:recipes/<name>/<template>);
if history is unavailable, reconstruct the best approximation and say so
in the PR.installedAt). The lock change rides the same branch.${CLAUDE_PLUGIN_ROOT}/recipes/<name>/scripts/doctor.sh <target> and the
repo's own gates if available. Doctors must not be worse than before
the update.chore: update recipes (<name> a.b.c -> x.y.z, …).
Body: per-file merge summary — upstream changes applied, local
adaptations preserved, collisions needing a human decision. Never
auto-merge; never push to the default branch.adopt-recipes (a tier graduation is an adoption decision, not an update).recipe-doctor owns that; this
skill runs doctors only to verify its own merge.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub dotts-h/claude-skills --plugin cookbook