Date: 2026-10-13. Status: design approved in chat by the owner, section by section; this spec awaits review.

Beasts should drop things, and heroes should craft with them, the way Animal Crossing does it: nothing can be made until its DIY recipe has been learned. The Kitchen cooks the 33 favorite foods; the Workbench makes battle goods, accessories, bag and storage upgrades and furniture. It must work with no setup: no Game Master writes drop tables.

The Workbench (MyCrafts) and the Kitchen (MyFoods) exist today with placeholder data (a remote accessory fetch and a mock food list). The bag already has a material kind (src/lib/services/inventory/Inventory.ts).

• Approach A: one built-in catalogue. Drops are a pure function of the beast's temple theme, the fight's difficulty and the beast's rank. Family-made beasts work because they carry a theme. No per-beast loot tables.
• Food is in-game only. Cooked food restores HP/MP; a hero's own favorite food restores double. Real treats stay GP shop items (the rewards-vs-powers rule).
• The Workbench makes all four: battle goods, accessories with stats, bag and storage upgrades, furniture. Placing furniture in My Home is a later epic with its own spec; furniture can be crafted and stored now.
• Recipes come from beast drops, region shops, and temple chests and boss first-clears. No starter recipes; instead a hero's first victory always drops a recipe card.
• Loot from a quest that waits for approval waits with it. Free fights drop commons and ingredients only.
• The Workbench tab "Weapons" is relabelled "Battle". The only tab change; every other tab keeps its label.

Every temple theme (TEMPLE_THEME_KEYS) has one common material (the fodder) and one rare.

Ingredients (the pantry, 10). Themed drops, and all ten are sold at the Home Town market for 5 GP each.

wind, light, moon and storm drop no ingredients.

Bag rows: { id: "<material-id>", name, kind: "material", qty, faIcon } (ingredients use the same kind, so the Pantry and My Goods' Materials tab both find them).

rollDrops(input, rng) in src/lib/services/crafting/drops.ts, pure, rng defaults to Math.random and tests pass a seeded one. Input: the defeated beasts (each { theme?, element?, isBoss, type, elite }), the fight kind (free or not), the difficulty, and whether this is the hero's first victory. Each beast rolls on its own; the results merge into stacks.

Theme. The beast's theme; without one, its art element: wind→wind, earth→earth, water→water, fire→fire, ice→ice, light→light, shadow→shadow, moon→moon, lightning→storm; anything else→wind.

Difficulty. A quest fight uses the quest's Fibonacci difficulty; a non-free fight with no quest uses 3.

First victory. When the hero knows no recipe and holds no recipe card, the fight drops one recipe card for sure, whatever its kind.

Which card. A random recipe whose sources include a drop of that theme, preferring ones the hero neither knows nor holds. When every one is known, any of them (a duplicate, sold for GP).

Where loot lands. The bag, then Storage; what fits nowhere is left behind and the victory line says so.

When loot pays.

• A fight with no approval wait: at the win, beside XP/GP/AP (useBattleOutcome.settleFight and settleQuestWin).
• A quest held for approval: the win stores the roll input on the pending claim (lootRoll: themes, ranks, difficulty, first-victory flag) and the Game Master's approval rolls and pays it, with a notification.
• Only battles drop. A quest completed off the battlefield drops nothing.

Enemies carry their theme. Enemy (src/lib/services/battle/battleService/types.ts) gains theme? and elite?, copied by the encounter loader from the beast (elite = the encounter used the beast's variantAvatar).

The victory dialog lists the loot under the rewards: "Wood ×2 · Egg · DIY: Pizza".

• knownRecipes: string[] on each hero (persisted with the profile). Old saves start empty.
• Recipe cards are bag rows { id: "recipe:<recipeId>", name: "DIY: <Name>", kind: "misc", type: "recipe", recipeId }. They list under Misc in My Goods (no new tab), with a Learn button.
• Learn: the card is used up and the id joins knownRecipes. A card already known shows Sell for N GP instead.
• Sell price: half the recipe's shop price; a recipe with no shop price sells for 20 GP (drop) or 60 GP (chest).
• Unknown recipe ids in knownRecipes are ignored. Unknown recipes are never shown on the stations.

src/lib/services/crafting/crafting.ts, pure:

• craftable(hero, recipe, qty): whether the materials are there, counted across the bag and Storage, and whether the output has room.
• craft(hero, recipeId, qty): new bag and Storage rows, or a refusal line. Materials come from the bag first, then Storage (reuse Storage.ts: rowsAfterTaking, canCarry). The output goes to the bag, else Storage, else refuse ("Your bag and storage are full.").
• Recipes need materials and ingredients only, never another crafted item.

Screen pattern for both stations:

• Rows of known recipes for the active tab: the product, then the needs line Wood 3/5 · Iron Nugget 1/2. Craftable rows are bright; the others dimmed.
• Tapping a row opens a bottom sheet (thumb reach): needs with have/need, a quantity stepper, Craft / Cook.
• The header meta reads 23 / 75 recipes. An empty station says where recipes come from: "Defeat beasts to find DIY recipes."
• Sounds through play$fx; toasts rpg-toast, position middle.

Tabs stay: All | Favorites | Meals | Snacks | Desserts | Pantry. Favorites pins the hero's own favoriteFood; Pantry lists the ingredients held. FOOD_OPTIONS stays the one list of foods; the catalogue adds each food's category and needs.

Source. Every food recipe drops from beasts of the theme of its first ingredient (Pizza: shadow, the kitchen).

Effects (src/lib/services/crafting/foodEffects.ts): snack +20 HP; meal +40 HP and +15 MP; dessert +30 MP; capped at max. The hero's own favoriteFood (matched on the singular name, as MyFoods already does) restores double. Cooked food is a consumable bag row; it can be eaten from My Goods and from the battle bag's Goods sheet (the same sheet that drinks potions, BattlePotions.ts).

Tabs: All | Furniture | Accessories | Battle (was Weapons) | Key. The remote xp_accessory fetch goes away.

Battle (8). Potions use the existing POTIONS rules. Bombs are one-shot goods with no MP cost: they run an existing BattleEffectId and are used up.

Accessories (9). Each needs its theme's rare; all come from chests of that theme.

Key (7): upgrades apply the moment they are crafted (no bag row). Tier n needs tier n-1; a tier the hero already has (bought or crafted) shows as built.

The bag size becomes per hero: bagTier (0 = 20 stacks, the old BAG_STACKS). Storage chests set the same storageTier the Gold Bank sells, so buying and crafting are two ways to one upgrade.

Furniture (18). Two per theme: a plain piece (drop of the theme) and a centrepiece with the rare (chest of the theme). Crafted furniture is a misc bag row { furniture: true } and is kept in the bag or Storage until the My Home epic lets it be placed.

Total: 33 foods + 8 battle + 9 accessories + 7 key + 18 furniture = 75 recipes.

Nothing applies Accessory.bonusStats today. Each hero gets one equipped accessory (the bag row moves into the slot; unequipping moves it back). Its bonus adds to the hero's strength, defense, speed, max HP and max MP wherever the battle reads them: one place, found in src/lib/services/stats/ (StatEffects / EngineStatsService), not per screen. The slot shows in the equipment modal beside the hands. No nav bar changes.

• Boss first-clear of a temple drops one recipe card whose sources include a chest of that temple's theme (unknown preferred), in the boss chest beside the usual reward.
• Temple creator: a chest's loot picker (RoomLootConfig) can also hold a recipe card or a material from the catalogue. Optional; nothing breaks when a GM never uses it.
• Shops: ShopItemType gains Recipe and Ingredient. Region shops are stocked from the catalogue's shop sources by merging into the defaults (ShopsDb.seedDefaults / syncWithRegistry): a family's own shelves are never removed. Buying a recipe puts the card in the bag; buying an ingredient puts it in the bag.

src/lib/services/crafting/
  catalog/materials.ts   MATERIALS (commons, rares, ingredients: id, name, kind, theme, faIcon)
  catalog/recipes.ts     RECIPES (id, name, station, tab, makes, needs, sources, shopPrice?), foods built from FOOD_OPTIONS
  drops.ts               rollDrops, themeOf
  recipeBook.ts          learn, sell, knownOf
  crafting.ts            craftable, craft
  foodEffects.ts         foodGain(food, hero)

user.ts gains knownRecipes, bagTier, accessory (persisted in profileFields.ts) and the actions addLoot, learnRecipe, sellRecipeCard, craftRecipe, equipAccessory.

• Catalogue integrity (jest): every need names a material; all 33 FOOD_OPTIONS have a recipe; every recipe has at least one source; every theme has at least one drop recipe; every shop source names a real shop id; 75 recipes.
• Drops: seeded rolls for each rank and kind; first-victory guarantee; unknown-first card choice; theme fallback.
• Recipe book and crafting: learn, duplicate sell, craft from bag then Storage, full bag refusal, tiered upgrades.
• Food: favorite doubles; caps at max.
• One Cypress run (--browser chrome): win a fight, a card drops, learn it, craft a Potion, drink it in battle.

1. Catalogue and integrity spec.
2. Drop engine.
3. Recipe book, crafting engine, hero state.
4. Loot on battle wins and on approvals (Enemy theme/elite, victory lines, lootRoll on held claims).
5. Chests, boss first-clears, shop stock.
6. Kitchen screen and food effects (My Goods eat, battle Goods sheet).
7. Workbench screen (Battle tab, Key upgrades and bagTier, bombs in the Goods sheet). Waits for board #1285.
8. Accessory slot with stats in battle.
9. E2E loop.
10. Later epic, own spec: placing furniture in My Home.

Per-beast loot overrides; gifting food to the party; trading between heroes; look pieces as drops (Look Unlocks project 3 can add a drop kind to rollDrops later); placing furniture.