kitchen-library

Documents data layout, storage keys, and workflows for a GitHub Pages recipe library.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/KuschiKuschbert/recipelibrary --skill kitchen-library-kuschikuschbert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kitchen-library
Source: https://github.com/KuschiKuschbert/recipelibrary/tree/main/.cursor/skills/kitchen-library
Command: npx skills add https://github.com/KuschiKuschbert/recipelibrary --skill kitchen-library-kuschikuschbert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents editing the Kuschi kitchen library need to know where recipe data lives, which localStorage keys hold user data, and which scripts must run before committing, or they risk breaking the static site. ## Core Features & Use Cases - Data layout reference: Maps recipe_detail/ as the single source of truth, alpha_catalog/ merged shards, and rebuild scripts like rebuild_catalog_from_detail.py. - Client-side storage guide: Documents every localStorage and sessionStorage key for kitchen recipes, Riviera recipes, kitchen books, order lists, and master ingredients. - Shipping workflow: Defines the test-commit-push routine with Conventional Commits after any code change. - Use Case: An agent asked to add a Riviera recipe field reads this Skill to learn the dedupe logic in assets/user-recipes.js, the built-in catalog sync script, and the required rebuild step before pushing. ## Quick Start Read the kitchen-library skill before making any edits to the recipe HTML pages or JSON data files.

Frequently Asked Questions about kitchen-library

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update recipe data in a static GitHub Pages recipe library?

Edit the source-of-truth files in recipe_detail/, then run scripts/rebuild_catalog_from_detail.py to regenerate alpha_catalog/ and claude_index/ shards. Commit with Conventional Commits and push to main so the live site reflects the changes.

Where are user recipes stored in a browser-only recipe app?

User recipes live in localStorage, not in JSON files. Kitchen recipes use the key kuschi_user_recipes_kitchen_v1 and Riviera recipes use kuschi_user_recipes_riviera_v1, managed by helpers in assets/user-recipes.js.

How does the Riviera order list group ingredients by storage zone?

The order list groups ingredients by freezer, coldroom, drystore, or other zones using assets/order-list.js. Lines merge on a canonical name key, and master ingredients in kuschi_master_ingredients_v1 supply default zones for matching names.

What must run before committing recipe data changes?

Run node --check on edited assets JavaScript files and rebuild catalog shards with the rebuild script after recipe_detail edits. Then commit with a Conventional Commits message and push the current branch.

Can kitchen books share data with the Riviera recipe set?

No, each kitchen book is fully isolated with its own localStorage keys for recipes, order overrides, extras, and master ingredients. Riviera storage keys are separate, so edits in one area never affect the other.