Dapcook
A household recipe manager: import recipes from any URL, organize them with tags, plan meals for the week, and generate a shopping list from the plan.
Features
- Recipe import — scrape a recipe from a URL (JSON-LD, meta tags, or Readability fallback) or paste raw text; an AI step extracts and normalizes ingredients/steps and can translate or transform a recipe (e.g. adjust servings).
- Tagging — recipes are organized with tags grouped into tag groups (drag-and-drop management, per-user default filters).
- Meal planner — schedule recipes into a weekly calendar, with recurring planner rules.
- Shopping lists — generate a shopping list from the planner, with categories, rules, and realtime sync across household members.
- Households — invite-based household membership (join links, shared plans/lists) with an admin area.
- Recipe sharing — share a recipe via an unlisted link.
Tech Stack
- Next.js (App Router) + React + TypeScript
- Supabase for auth, Postgres, and storage
- Anthropic SDK for recipe extraction/transformation
- Tailwind CSS, shadcn/ui,
@dnd-kit for drag-and-drop
- Vitest (unit) + Playwright (e2e)
Getting Started
Copy .env.local.example to .env.local and fill in Supabase/Anthropic credentials, then run the dev server:
npm install
npm run dev
Open http://localhost:3000 to see the result.
Database schema and migrations live in supabase/migrations.
Scripts
npm run dev — start the dev servernpm run build / npm run start — production build/servenpm run lint — ESLintnpm run type-check — TypeScript checknpm run test / npm run test:watch — unit tests (Vitest)npm run test:e2e — end-to-end tests (Playwright)
Project Structure
src/app — routes, grouped into (app) (main authenticated app: recipes, planner, shopping, settings, admin), (auth) (login), (flow) (guided flows), and api (route handlers)src/lib — domain logic: ai, scraper, recipes, planner, shopping, tags, auth, supabasesrc/components — UI components by feature areadocs/superpowers — feature specs and implementation plans
Deployment
staging is a permanent, downstream-only integration branch: it carries main
plus whatever is still being tested, and it never merges back into main.
- Small change — land it on
main. It deploys to production, and
.github/workflows/sync-staging.yml merges it into staging automatically.
- Big feature — branch off
main, merge that branch into staging to test
it on the staging URL, then merge the same branch into main once approved.
If staging ever tangles it can be thrown away, because it holds no unique
history:
git checkout staging && git reset --hard origin/main && git push --force origin staging
Migrations
scripts/apply-migrations.ts applies pending supabase/migrations/*.sql to
staging automatically, tracking what it has run in a schema_migrations table.
Databases that predate that table are recognised by their existing schema and
seeded from supabase/baseline.txt rather than re-migrated. Production
migrations are applied by hand.
See Next.js deployment docs for details.
