The Fridge Fix

Build me a working meal-planning dashboard called The Fridge Fix using ingredient photos or a cupboard list I provide.

Help me see what I have, prioritise ingredients using confirmed dates, plan meals and create a shopping list for what is missing. Create the actual interactive tool, not just a list of recipe ideas.

MY INGREDIENTS
If I have not supplied photos or a list, ask for them. Accept a written list as an equal alternative to photographs. Read visible packaging and labels, but flag anything uncertain. Ask me to confirm item identity, quantity, units, date type and any unclear date rather than guessing.

Ask for household servings, dietary preferences, allergies or ingredients to avoid, typical cooking time and available equipment. Ask which country I am in for food-label guidance; use UK guidance only when appropriate. Do not produce personalised meal suggestions until allergies/avoidances are confirmed, including an explicit answer of none. Let me change these preferences later and recheck affected meals.

INVENTORY
Give each ingredient a stable ID and editable fields: name, amount, unit, storage location (fridge/freezer/cupboard), use-by or best-before date, date unknown, opened date where supplied, package storage instructions and notes. Keep separate batches with different dates distinct. Do not assume a photo reveals the amount left in a packet, its storage history, freshness or whether it is safe to eat.

Show searchable inventory cards or rows and filters for location, ingredient, date status and available/used up. Include add, edit, archive and undo controls. Show the date and timezone used by the date calculations. Never treat an unknown date as today or as indefinitely safe.

USE THESE FIRST
Sort eligible confirmed ingredients by their relevant upcoming dates. Use separate labels for approaching use-by, best-before quality dates and dates needing confirmation. Do not merge those into an unexplained “expiry” score.

For the UK, use-by is about safety and best-before is about quality. Do not propose eating an item after its use-by date based on its appearance or smell. Exclude past-use-by items from ordinary meal suggestions; if the user records timely cooking/freezing, treat that as a separate state requiring the relevant storage and defrosting guidance. Dates do not override package storage instructions. Check current official guidance for the user's location before adding safety-specific rules. Do not certify food as safe from a photo.

MEAL IDEAS
Prepare a practical set of meals from the confirmed inventory and preferences. For each, show servings, approximate preparation/cooking time, equipment, ingredients with quantities, what is available, what needs buying, concise steps and which dated items it uses. Name ordinary recipe ideas accurately; do not invent claims about nutritional benefits or precise calories.

Include filters for cooking time, meal type, dietary preference and “Use what I have” versus “Needs a few extras”. “Use what I have” must exclude meals with unconfirmed or missing required ingredients. Never silently assume I own oil, salt, spices or other staples; ask or list them as missing. Mark quantity availability as unknown when it cannot be established.

Exclude my stated allergens and avoidances. For packaged ingredients, require label checking when needed; do not certify an entire meal allergen-free from a photo, a vegan label or an incomplete ingredient list. Verify safety-critical cooking/storage instructions with appropriate official sources when generating them, and provide concise source links in the tool's help section.

Make filtering and planning work from the prepared recipe collection. Do not include a pretend AI recipe-generation button. If the inventory changes and new ideas are needed, let me update it through this conversation or add a recipe manually with ingredient quantities and instructions.

WEEKLY PLANNER
Add a seven-day meal planner for a selected calendar week. Let me assign, move, replace or remove meals and change servings. Use labelled controls, with drag-and-drop only as an optional extra. Flag a plan that places a use-by ingredient after its confirmed safe window instead of silently allowing the suggestion.

Track ingredient quantities required across the whole selected plan. Do not allocate the same remaining quantity to several meals as if it were unlimited. Planning should reserve quantities, not pretend the food has already been consumed. Include a separate Mark cooked action with confirmation before adjusting inventory, plus undo. If amounts are unknown or units cannot be reliably converted, ask me to review them rather than guessing.

SHOPPING LIST
Generate a deduplicated list of required ingredients for the selected plan minus confirmed available stock. Add quantities only when units are compatible; do not turn grams into millilitres without a supported conversion. Separate “Need to buy” from “Check quantity/label”. Include manual additions, editable amounts, checkboxes and grouping by shopping category. Recalculate when meals or servings change while preserving manual additions and applicable ticked states.

Provide Copy shopping list and Print shopping list controls, plus a printable weekly menu. Buying or checking off an item must not silently change inventory until I confirm it was added. Do not place orders, connect to grocery accounts or invent live prices.

DESIGN
Use a clean, neutral monochrome interface: off-white #FAFAF8 for the page, white #FFFFFF for cards and light text on dark buttons, charcoal #202020 for headings, main text, links and buttons, mid-grey #6B6B6B for secondary text on white/off-white, and light grey #E3E3E0 for borders and subtle callouts. Use charcoal text on light-grey surfaces. Keep original uploaded photographs in their natural colours.

Make it responsive with readable type, compact introductions, clearly labelled controls, comfortable phone tap targets, keyboard access, visible focus and reduced-motion support. Give every image descriptive alternative text. Do not rely on colour alone to communicate status. Use useful empty states and working controls rather than decorative buttons.

SAVING AND DELIVERY
Save edits and progress in this browser and restore them after refresh. Use IndexedDB for image files; do not rely on temporary chat image URLs or put full-size photos into localStorage. Explain browser-local storage briefly and do not imply cross-device syncing. Provide a downloadable backup and restore with validation and confirmation before replacing saved work. Preserve existing work if an import fails. Keep uploaded personal material private by default and use private hosting or a supported local artifact.

Deliver the finished working dashboard link or file with my content already inside it, not just a plan, screenshot or code snippets. If this environment cannot create the artifact, explain the limitation honestly. Check the main controls, data rules, saved state, backup/restore and mobile layout when tools permit. State what you actually tested. No fake live integrations or buttons that pretend to invoke the AI tools in this chat.

Specifically check date handling, allergen exclusions, quantity reservations across meals, serving changes, incompatible units, shopping-list deduplication, manual additions and undo. Begin by checking my ingredients and asking about servings and dietary requirements.