Cookable
Tell it what's in your kitchen; it tells you what you can cook tonight — plus swaps for whatever you're missing. Empty repo to installable app in six days.
Most recipe apps start from a recipe and send you to the shops. Cookable starts from what you already have. You type what's in your kitchen — `dahi`, `jeera`, `atta`, `shimla mirch`, `kadai`, `mixie`, `2 large onions`, or just paste a whole list — and it checks every recipe line by line. Each recipe lands on one of four shelves: "Make it now," "One or two things short," "A few things short," or "Not without a shop." When something's missing, it doesn't just shrug — it looks for what you could use instead, with the amount, and a warning when the stand-in can't do the whole job. The swap engine has opinions, which is what makes it trustworthy. It will happily swap the oil in paneer bhurji but will never swap the paneer. No oven? It tells you to use the air fryer about 20°C cooler and check 20–25% sooner. Every recipe shows protein, calories, fibre, and added sugar; sugar and honey get swapped out whenever there's a way. It installs like an app, works offline, has no account and no server — your kitchen stays in your browser. The build story is the real showpiece. Per the README: "from an empty repository to an installable app in six days," one pull request at a time, with a `CLAUDE.md` that explains *why* each convention exists, slash commands like `/add-recipe` for repetitive jobs, and a validator as the safety net. The author even documents the method so you can borrow it: write one sentence about what the app is for, let Claude Code build a first version, and whenever you catch yourself making the same correction twice, put it in `CLAUDE.md`. A working recipe app and a working recipe for vibe coding, in the same repo. Note: This project is curated by the VibeFix editors from public sources. All rights belong to the original creator.
