Dreamlight Valley Cooking, Gathering, and Inventory Management

This skill has several modes. Pick the matching mode, then read its reference file for the full procedure — don’t execute from memory.

When the user’s intent is ambiguous, ask one short routing question rather than guessing.

Bundled data

• references/recipes.json — 472 recipes. Each: name, course (appetizer/entree/dessert), star_rating, energy, sale_price, ingredients. An ingredient slot is either fixed ({"name": "..."}) or a category slot ({"name": "spice", "category": true}) accepting any ingredient of that category. Category slots are the single most important nuance in DDV cooking.
• references/gatherables.json — master catalog under categories:
  • ingredients (188) — name, category (vegetable, fruit, grain, spice, sweets, seafood, dairy, meat, ice, fish), method (gardening/foraging/fishing/purchase), energy, sale_price, locations. Fish live here with category: "fish" — recipes with a fish category slot resolve to these.
  • flowers (86) — name, sale_price, locations, optional availability (abundant/average/rare/ultra-rare; event/seasonal flowers intentionally omit it).
  • collectables (62) — name, method (string or array, e.g. Bones is ["digging","fishing"]), locations, optional event.
  • gems (50) — name, locations, optional sale_price. Locations include biome + sub-area (e.g. "Glittering Dunes (The Wastes)"). "All Biomes" is valid (Stone, Coal Ore). Shop-source values like "Kristoff's Stall" mean the item is purchasable there.
• references/categories.md — what each cooking category slot accepts.
• references/icon-cues.md — reading storage screenshots and disambiguating icons (two-pass read, 99-skip, gem regular/shiny, color-family pitfalls, event-item floor convention, crafted-not-gathered exclusions).
• references/sprites/*.png — labeled canonical art:
  • 13 per-category gatherable sheets (gems.png, flowers.png, collectables.png, plus one ingredients-<category>.png per cooking category)
  • one full-catalog recipes.png (472 dishes, 1056×9734 px) All use the same 8-column alphabetical grid with captions. Open the matching sheet to confirm a thumbnail by eye.
• references/sprite-coords.json — companion index mapping every gatherable item AND every recipe to its (sheet, row, col, x, y, w, h) plus the shared grid layout. Use it to jump straight to a known item/recipe’s icon without scanning the whole sheet, and to verify whether a name exists in the catalog. Regenerated by yarn workspace @allons-y/skill-dreamlight-valley build:sprites.

Do not recite this data from memory — read the files. The bundled data is authoritative; your memory isn’t.

Configuration

This skill is for a single player’s saved game, so the config is a small plain-text file the user edits by hand. Check these paths in order and use the first one that exists:

1. ./dreamlight-valley.md
2. ~/.config/dreamlight-valley.md

config.example.md (next to this SKILL.md) is the starter. Read the file at the start of each mode and interpret it generously — it’s prose, not JSON. Users can express: floor (single or per-category), /cook objective, top-N recipe count, secondary-payout callout, extra fields shown by /recipe, and /restock toggles. Command-line flags from the user always win over the config. No config file present → use built-in defaults silently (don’t mention the config unless asked).

What this skill does NOT do

• Track which expansion a recipe belongs to (the field was removed). If the user wants an expansion-specific list, fall back to filtering by ingredient origin where reasonable, or say it’s unsupported.
• Account for the “Well Fed” bonus, seasonal modifiers, or Goofy’s-stall price fluctuations — sale_price is the standard base sell value.
• Guess item locations. A handful of fish/seafood ingredients and event critters have empty locations arrays — say so rather than fabricating one.