Mealime Pro

Build me a focused family organization, recipes and household inventory workflow for the personal core of Mealime Pro. Requirements:

- Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA. Model the inputs, state transitions, and outputs named in this family organization, recipes and household inventory prompt; keep source IDs and timestamps.
- Paid product context: Plan meals from user-entered recipes and create a combined shopping list. Build only this DIY scope: Plan meals from user-entered recipes, create a combined shopping list, share or print a simple plan, and keep household data portable and owner-controlled.
- Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
- Support recurring chores or events, reminders, completion history, and printable views.
- Add CSV or JSON import and export plus photo attachments with clear size limits. Allow private and shared items and make every change attributable and undoable. Add backups, household export, member removal, and a simple invite code.
- Use a local web page with input, progress, review, and export views. Required input or access: local or self-hosted storage; optional email notifications.
- Recovery: Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization; frictionless family sync. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Mealime Pro

## Project scope
Plan meals from user-entered recipes, create a combined shopping list, share or print a simple plan, and keep household data portable and owner-controlled.

Catalogue verdict: no. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Mealime Pro, plan meals from user-entered recipes and create a combined shopping list. The hard boundary is licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization, plus sync, integrations, and household adoption.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- modern browser
- local or self-hosted storage
- optional email notifications

## Stack and architecture
- Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA.
- Model the inputs, state transitions, and outputs named in this family organization, recipes and household inventory prompt; keep source IDs and timestamps.
- Interface for this family organization, recipes and household inventory workflow: a local web page with input, progress, review, and export views.

## Security and data integrity
- Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization.

## Agent implementation rules
- Project rule, data: Model the inputs, state transitions, and outputs named in this family organization, recipes and household inventory prompt; keep source IDs and timestamps.
- Project rule, behavior: Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
- Project rule, recovery: Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this family organization, recipes and household inventory operation with sample or user-owned data: Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
- Show a concrete result or export: Add CSV or JSON import and export plus photo attachments with clear size limits.
- State the practical limit: licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization.

## Engineering roadmap
1. Phase 1, architecture and data: Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA. Model the inputs, state transitions, and outputs named in this family organization, recipes and household inventory prompt; keep source IDs and timestamps.
2. Phase 2, implement: Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
3. Phase 3, implement: Support recurring chores or events, reminders, completion history, and printable views.
4. Phase 4, review and output: Add CSV or JSON import and export plus photo attachments with clear size limits.
5. Phase 5, recovery and acceptance: Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server. Verify this invariant with a saved fixture: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs. State the practical limit: licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization.

## Paid-product capabilities outside this build
- licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization
- frictionless family sync
- retailer and smart-home integrations
- large recipe or product database
- mobile polish

## Implementation prompt
Build me a focused family organization, recipes and household inventory workflow for the personal core of Mealime Pro. Requirements:

- Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA. Model the inputs, state transitions, and outputs named in this family organization, recipes and household inventory prompt; keep source IDs and timestamps.
- Paid product context: Plan meals from user-entered recipes and create a combined shopping list. Build only this DIY scope: Plan meals from user-entered recipes, create a combined shopping list, share or print a simple plan, and keep household data portable and owner-controlled.
- Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
- Support recurring chores or events, reminders, completion history, and printable views.
- Add CSV or JSON import and export plus photo attachments with clear size limits. Allow private and shared items and make every change attributable and undoable. Add backups, household export, member removal, and a simple invite code.
- Use a local web page with input, progress, review, and export views. Required input or access: local or self-hosted storage; optional email notifications.
- Recovery: Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: An invalid input or interrupted operation must retain the source and show a recoverable state; exported records must reload with the same IDs.
- Out of scope: licensed recipe catalog, nutrition data, retailer links, mobile apps, and personalization; frictionless family sync. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.