القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | page-specs |
| description | 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. |
Per-page docs in docs/product-specs/pages/ are the single source of truth for:
New page: copy docs/product-specs/pages/TEMPLATE.md. Register in the Page docs table below and in docs/product-specs/index.md.
| Page | Doc path | ID prefix |
|---|---|---|
| (add rows as pages are specced) |
| # | Feature | Description | Status | Tests |
|---|---------|-------------|--------|-------|
| XX-1 | Feature name | Behavior only (no test links here) | complete | [`getRecipes`](../../../src/static-api/loaders/getRecipes.test.ts) |
| XX-2 | Specced only | Brief requirement | planned | none |
complete | planned | not-workingnone, or markdown links to tests and/or API spec anchors| in cells as \|| Step | Action |
|---|---|
| Plan | Add planned row; link API spec sections if server-backed |
| Build | Implement page + API together |
| Cover | Link tests in Tests column |
| Verify | Status complete; update Decisions if drift |
| Regress | Status not-working until fixed |
TEMPLATE.md → pages/<name>.md; choose unique 2-letter prefixpages/README.md status table and docs/product-specs/index.mdPair with product-docs-specs and api-specs for every change.