This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
A local-first cooking & meal-memory skill for Codex, Antigravity & Claude Code. Stored in local SQLite with pure Python (zero API keys). Tracks recipes, plans, allergies & real cooked/eaten history separately.
I built Meal Magic because I wanted an AI cooking assistant that actually remembers my household's allergies, preferences, and what we really cooked or ate — without locking our data into a cloud SaaS, requiring extra API keys, or mixing up "we planned pasta" with "we actually ate pasta."
How it works:
The skill (SKILL.md + references) teaches Codex, Antigravity, or Claude Code how to format complete recipes, respect per-member dietary restrictions, and suggest varied meals.
The storage helper (meal_store.py) runs locally using only the Python 3.10+ standard library and SQLite. No network calls, no telemetry, no external dependencies.
Cross-agent shared profile: All three hosts can share the same local household database on Windows, macOS, and Linux, with transactional migrations (currently schema v8) and idempotent retry keys.
What we just shipped in v0.7.0:
Full recipe updates and safe deletion (recipe-remove keeps historical meal snapshots intact)
Date-range filtering on meal-list and read-only variety analytics via meal-stats
Selective recipe-import with dry_run conflict previews
A verified Windows shared-profile fast path + 175 automated tests across Ubuntu, macOS, and Windows
I'd love your honest feedback on the UX, the CLI/skill architecture, or anything you'd want to see next. Happy to answer any questions!
No comment highlights available yet. Please check back later!
About Meal Magic on Product Hunt
“Local-first cooking & meal skill for AI agents”
Meal Magic was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #420 on the daily leaderboard. A local-first cooking & meal-memory skill for Codex, Antigravity & Claude Code. Stored in local SQLite with pure Python (zero API keys). Tracks recipes, plans, allergies & real cooked/eaten history separately.
Meal Magic was featured in Open Source (69.1k followers), Developer Tools (523.3k followers), Artificial Intelligence (484k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 287.7k products, making this a competitive space to launch in.
Who hunted Meal Magic?
Meal Magic was hunted by Lazaros Avramidis. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Meal Magic stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt! 👋
I built Meal Magic because I wanted an AI cooking assistant that actually remembers my household's allergies, preferences, and what we really cooked or ate — without locking our data into a cloud SaaS, requiring extra API keys, or mixing up "we planned pasta" with "we actually ate pasta."
How it works:
The skill (SKILL.md + references) teaches Codex, Antigravity, or Claude Code how to format complete recipes, respect per-member dietary restrictions, and suggest varied meals.
The storage helper (meal_store.py) runs locally using only the Python 3.10+ standard library and SQLite. No network calls, no telemetry, no external dependencies.
Cross-agent shared profile: All three hosts can share the same local household database on Windows, macOS, and Linux, with transactional migrations (currently schema v8) and idempotent retry keys.
What we just shipped in v0.7.0:
Full recipe updates and safe deletion (recipe-remove keeps historical meal snapshots intact)
Date-range filtering on meal-list and read-only variety analytics via meal-stats
Selective recipe-import with dry_run conflict previews
A verified Windows shared-profile fast path + 175 automated tests across Ubuntu, macOS, and Windows
I'd love your honest feedback on the UX, the CLI/skill architecture, or anything you'd want to see next. Happy to answer any questions!