القائمة
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.
التثبيت باستخدام 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.
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.
| name | recipes-design-first |
| description | 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. |
Product specs → API/data contracts → failing tests → code. Modeled on ScreenShotComposer / PhotoCollage doc-driven development, adapted for this React + static JSON app.
| Concern | Skill |
|---|---|
| This workflow | recipes-design-first (you are here) |
| Product docs | product-docs-specs, page-specs, feature-catalog |
| Data contracts | api-specs (loaders + JSON), recipes-static-api |
| Import recipe from URL | recipes-import-recipe |
| Scrape non-YouTube URLs | recipes-enrich-from-url |
| YouTube video recipes | recipes-youtube-recipe |
| Implementation | recipes-project, recipes-components, recipes-design-system |
| Tests | recipes-tdd |
docs/product-specs/application.md if vision/personas changeplanned row in docs/product-specs/pages/<page>.mddocs/api-specs/ (see api-specs)docs/feature-catalog.mdcomplete, bidirectional links, README rollupsdocs/
product-specs/ # pages, components, services
api-specs/ # JSON + loader contracts (not HTTP)
feature-catalog.md # roll-up index
architecture.md # code layers
React 19 + Vite + Vitest + RTL. Data: src/static-api/ only — see recipes-static-api and AGENTS.md.
recipe-list.md, prefix RL-)recipes-catalog.mdnpm run test:run green for touched tests