CommonTable — One table. Everyone included.

A developer built CommonTable, a collaborative AI meal-planning web app that lets a household propose a recipe, discuss changes, and have an LLM suggest adaptations while a separate deterministic safety engine checks the result against each member's dietary constraints. The project deliberately keeps the model out of safety decisions, returning SAFE, UNSAFE, or NEEDS REVIEW verdicts and then generating a grocery list once everyone approves. The developer says the household context, collaboration workflow, and safety engine — not the model — are what turn the demo into a product.

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend https://dev.to/challenges/hacktoberfest-weekend-2026-10-01 . Meet CommonTable — a collaborative AI meal planner designed for people who actually eat together. Imagine this: Three friends live together. Someone has to cook tonight. They suggest a recipe in the app. Everyone gets notified, reviews it, and can suggest changes. The system checks the recipe against the household's dietary constraints, identifies conflicts, and helps find safer alternatives. Instead of: “What should we eat?” the app helps answer: “What can all of us actually eat?” 👨🍳 Cook proposes a meal ↓ 📢 Friends receive the proposal 💬 Friends suggest changes 🤖 AI adapts the recipe 🛡️ Safety engine checks the updated ingredients ✅ Everyone approves 🛒 Grocery list is generated The goal isn't to create another AI recipe generator. It's to make group meal planning less chaotic, more collaborative, and safer. The project is a responsive web application built around open-source AI and a deterministic safety layer. Frontend Backend AI I deliberately didn't let the LLM decide whether a meal is safe. The flow is: User / Cook ↓ AI generates recipe ↓ Structured ingredients ↓ Ingredient normalization ↓ Safety & constraint engine ↓ Household profiles ↓ SAFE / UNSAFE / NEEDS REVIEW The AI can suggest a substitution. The safety engine decides whether the resulting recipe conflicts with the household's known constraints. That separation is important because an LLM sounding confident doesn't make a food-safety decision reliable. Open innovation made it possible to build this as more than a thin wrapper around a closed AI API. Using open-source and open-weight technologies gives us the ability to: More importantly, the project isn't dependent on the model being the entire product. The model is one component. The household context, collaboration workflow, safety engine, and product logic belong to us. That's the part that turns an AI demo into an actual product. Most meal-planning apps think about one person . Real dinners usually involve more than one. When you're cooking with friends or roommates, the problem isn't just finding a recipe. It's remembering: Who can eat this? Who can't? What can we change? Does everyone agree? What do we actually need to buy? I wanted to turn that messy conversation into one simple workflow. Propose. Discuss. Adapt. Check. Approve. Eat. And hopefully, fewer: “Wait... does this contain peanuts?” 😅 Add applicable partner categories here. If you live with roommates, cook with friends, or regularly have to plan around different diets and allergies, this is the kind of problem I'd love to make easier. Feedback is welcome — especially from people who have experienced the “What are we eating tonight?” group-chat debate. 😄 GitHub: Add repository Demo: Add deployed URL