family-recipes

Scrape non-YouTube sourceUrl into the catalog (JSON-LD/HTML parser or browser). Subskill of recipes-import-recipe — use the parent skill first to route YouTube vs web. Use for blog/recipe-site URLs with empty ingredients or placeholder steps.

Add or refresh a recipe in the static catalog from a URL. Simplifies noisy titles, always fetches ingredients/steps/images from the source, and delegates to recipes-youtube-recipe when sourceUrl is YouTube. Use when the user asks to add a recipe, import from a link, or fill the database from a bookmark.

Starred cook queue and meal-type tags on recipes. Use when changing the starred queue, starred order, or tagging recipes for breakfast/lunch/dinner/etc.

Subskill of recipes-import-recipe for YouTube URLs. Timestamped video recipes, simplified titles, ingredients from description RECIPE blocks or linked blogs. Use when sourceUrl is youtube.com or youtu.be — not as the top-level import entry.

Entry point for Recipes — design docs, static API contracts, design system, component-first UI, and TDD. Use when starting work, planning features, writing specs, or onboarding to this repo.

Document static JSON and loader contracts under docs/api-specs/ before changing src/static-api/. Use when adding recipes, loaders, types, filters, or data the UI depends on; pairs with recipes-static-api, page-specs, and recipes-tdd.

Maintain a complete inventory of user-visible features across page and API specs. Use when adding features, auditing documentation coverage, or the user asks to document every feature.

Keep page specs in docs/product-specs/pages/ complete and accurate. ALWAYS read before adding, changing, or removing UI or page behavior; update feature tables and code maps in the same change.

Keep product docs current for pages, components, and services under docs/product-specs/. ALWAYS use before adding, changing, or removing user-visible behavior, reusable UI, or background product behavior; update specs, dependency tables, and folder README status rollups in the same change.

Component-first design for the recipes React app — layers, composition, props, and file structure. Use when building UI, splitting components, or deciding page vs feature vs shared component boundaries.

Design system for the recipes app — tokens, primitives, theming, and CSS module rules. Use when styling UI, adding buttons/cards/typography, or preventing one-off styles in feature code.

Recipes React app conventions — static API, design system, component-first layout, and TDD. Use when bootstrapping, adding features, or unsure where code belongs in the recipes repository.

Static JSON API for recipe data — schemas, loaders, types, and tests without a backend. Use when adding recipes, fetching by slug/tag, or wiring data into React hooks.

Test-driven development for the recipes React app. Use when adding behavior, fixing bugs, or the user mentions TDD, tests first, red-green-refactor, or Vitest/React Testing Library. Pair with page-specs and api-specs for doc-first work.

Alias for recipes-tdd in this repo. Use recipes-tdd skill for full instructions.