Personal · Weekend build
Build your own Paprika Recipe Manager
Recipes without the life story, groceries without the chaos. Paprika Recipe Manager charges $2.5–$5 per month — that’s $30–$60 a year — for something you can replace with focused software of your own. Here is the honest scope, the honest timeline, and the exact prompt to hand your coding agent.
Who this replacement is for
This build targets one home cook planning dinners for the household. The goal: import recipes cleanly, plan the week, and shop from one aggregated list. If you need more than that, keep paying — the point of building it yourself is owning a tool shaped exactly like your workflow, not re-implementing a venture-funded roadmap.
Same build, different logo: this v1 also replaces Mela and Crouton — they all solve the same core job.
How long it actually takes
One number would be a lie, so here are three. Each tier is a real, usable product — pick the one that matches how much of Paprika Recipe Manager you actually use.
| Estimate | What you get |
|---|---|
| 6 hours | url import, recipes, scaled grocery list |
| 2 days | photos, cook timers, plan templates, list sharing |
| 1 month+ | native apps, cloud sync, pantry tracking — the part you should probably skip |
What a minimal Paprika Recipe Manager alternative needs
- a URL importer that parses schema.org recipe markup into clean ingredients and steps
- a recipe library with tags, search, and serving-size scaling
- a weekly meal plan that assigns recipes to days
- an aggregated grocery list that merges quantities and groups items by aisle
- a cook mode with large-type steps and a kept-awake screen
Data model
Recipe, Ingredient, PlanEntry, GroceryList, GroceryItem
Integrations
schema.org recipe extraction, Screen Wake Lock API
Capability context
Astro, HTMX, D1
The guardrail
Fetch recipe pages server-side with timeouts and size caps, and store only the structured recipe the user reviewed and chose to save.
Deliberate non-goals
Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
The complete build prompt
Copy this into your coding agent of choice. It is scoped for a useful v1 — journeys, screens, business rules, data model, security, tests, and acceptance scenarios included. Pick your stack:
You are building a production-ready software product named “Stewpot”, a deliberately focused alternative to Paprika Recipe Manager. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: one home cook planning dinners for the household. Primary outcome: import recipes cleanly, plan the week, and shop from one aggregated list. Product principle: optimize the exact workflow below instead of copying the full breadth of Paprika Recipe Manager. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. The cook pastes a recipe URL, watches the importer parse schema.org markup into ingredients and steps, fixes one quantity, tags the recipe, and saves it to the library. 2. The cook assigns recipes to the week’s days, scales one dinner from four servings to six, and generates a grocery list with quantities merged and grouped by aisle. 3. In the kitchen, the cook opens cook mode, works through large-type steps with the screen kept awake, and later checks off grocery items at the store from a phone. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Library: recipe cards with photo, tags, source domain, search, serving count, and a prominent import-from-URL action. 2. Recipe detail: ingredients with a serving-size scaler, numbered steps, notes, source link, and add-to-plan and cook-mode actions. 3. Week planner: seven day columns, assigned recipes with chosen servings, drag between days, and a generate-grocery-list action. 4. Grocery list: items merged by ingredient and grouped by aisle, check-off state, manual additions, and a plain-text export. CORE CAPABILITIES 1. a URL importer that parses schema.org recipe markup into clean ingredients and steps 2. a recipe library with tags, search, and serving-size scaling 3. a weekly meal plan that assigns recipes to days 4. an aggregated grocery list that merges quantities and groups items by aisle 5. a cook mode with large-type steps and a kept-awake screen DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Fetch recipe pages server-side with timeouts and size caps, parse only schema.org Recipe markup, and always show the parsed result for review before saving anything. 2. Store ingredient quantities as structured amount, unit, and name so scaling and list aggregation are arithmetic, not string surgery. 3. Merge grocery items only when ingredient name and unit are compatible; otherwise keep both lines rather than guessing a conversion. 4. Keep aisle assignments as an editable per-household mapping and remember corrections for every future list. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Recipe, Ingredient, PlanEntry, GroceryList, GroceryItem. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Astro pages and ordinary HTML forms. Use HTMX for form submissions, partial navigation, and server-driven updates, then Alpine.js only for small local browser state. The core workflow must remain understandable if either enhancement layer fails. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with the AHA stack: Astro for routing, layouts, and server-rendered pages; HTMX for interactions that benefit from HTML fragment responses; and Alpine.js for small, local interface state. Prefer Cloudflare D1 for relational persistence, R2 for object storage, Workers for server endpoints and scheduled work, Durable Objects only for coordinated real-time state, and Workflows or Queues for durable background jobs—but only when the product requirements call for them. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, HTMX, D1 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with schema.org recipe extraction and Screen Wake Lock API. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Fetch recipe pages server-side with timeouts and size caps, and store only the structured recipe the user reviewed and chose to save. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. Given a page with valid recipe markup, importing produces editable ingredients and steps and saves nothing without the cook’s confirmation. 2. Given two planned recipes that both need onions in compatible units, the grocery list contains one onion line with the summed quantity. 3. Given cook mode is open, the screen stays awake through a slow braise and the current step survives an accidental page refresh. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
You are building a production-ready software product named “Stewpot”, a deliberately focused alternative to Paprika Recipe Manager. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: one home cook planning dinners for the household. Primary outcome: import recipes cleanly, plan the week, and shop from one aggregated list. Product principle: optimize the exact workflow below instead of copying the full breadth of Paprika Recipe Manager. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. The cook pastes a recipe URL, watches the importer parse schema.org markup into ingredients and steps, fixes one quantity, tags the recipe, and saves it to the library. 2. The cook assigns recipes to the week’s days, scales one dinner from four servings to six, and generates a grocery list with quantities merged and grouped by aisle. 3. In the kitchen, the cook opens cook mode, works through large-type steps with the screen kept awake, and later checks off grocery items at the store from a phone. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Library: recipe cards with photo, tags, source domain, search, serving count, and a prominent import-from-URL action. 2. Recipe detail: ingredients with a serving-size scaler, numbered steps, notes, source link, and add-to-plan and cook-mode actions. 3. Week planner: seven day columns, assigned recipes with chosen servings, drag between days, and a generate-grocery-list action. 4. Grocery list: items merged by ingredient and grouped by aisle, check-off state, manual additions, and a plain-text export. CORE CAPABILITIES 1. a URL importer that parses schema.org recipe markup into clean ingredients and steps 2. a recipe library with tags, search, and serving-size scaling 3. a weekly meal plan that assigns recipes to days 4. an aggregated grocery list that merges quantities and groups items by aisle 5. a cook mode with large-type steps and a kept-awake screen DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Fetch recipe pages server-side with timeouts and size caps, parse only schema.org Recipe markup, and always show the parsed result for review before saving anything. 2. Store ingredient quantities as structured amount, unit, and name so scaling and list aggregation are arithmetic, not string surgery. 3. Merge grocery items only when ingredient name and unit are compatible; otherwise keep both lines rather than guessing a conversion. 4. Keep aisle assignments as an editable per-household mapping and remember corrections for every future list. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Recipe, Ingredient, PlanEntry, GroceryList, GroceryItem. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Render with React Server Components by default. Use Server Actions for authenticated form mutations and add Client Components only for interactions that genuinely require browser state, browser APIs, drag-and-drop, or live updates. The core workflow must remain understandable before client-side JavaScript finishes loading. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Next.js, the App Router, and TypeScript. Use Server Components by default, Server Actions for authenticated mutations, and Route Handlers for public APIs, OAuth callbacks, webhooks, feeds, uploads, and downloads. Use PostgreSQL through Drizzle ORM with versioned migrations and an isolated test database. Access S3-compatible object storage through a server-only adapter, and run slow or retryable work in a real job or workflow system instead of the request lifecycle. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, HTMX, D1 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with schema.org recipe extraction and Screen Wake Lock API. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Fetch recipe pages server-side with timeouts and size caps, and store only the structured recipe the user reviewed and chose to save. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. Given a page with valid recipe markup, importing produces editable ingredients and steps and saves nothing without the cook’s confirmation. 2. Given two planned recipes that both need onions in compatible units, the grocery list contains one onion line with the summed quantity. 3. Given cook mode is open, the screen stays awake through a slow braise and the current step survives an accidental page refresh. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
You are building a production-ready software product named “Stewpot”, a deliberately focused alternative to Paprika Recipe Manager. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: one home cook planning dinners for the household. Primary outcome: import recipes cleanly, plan the week, and shop from one aggregated list. Product principle: optimize the exact workflow below instead of copying the full breadth of Paprika Recipe Manager. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. The cook pastes a recipe URL, watches the importer parse schema.org markup into ingredients and steps, fixes one quantity, tags the recipe, and saves it to the library. 2. The cook assigns recipes to the week’s days, scales one dinner from four servings to six, and generates a grocery list with quantities merged and grouped by aisle. 3. In the kitchen, the cook opens cook mode, works through large-type steps with the screen kept awake, and later checks off grocery items at the store from a phone. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Library: recipe cards with photo, tags, source domain, search, serving count, and a prominent import-from-URL action. 2. Recipe detail: ingredients with a serving-size scaler, numbered steps, notes, source link, and add-to-plan and cook-mode actions. 3. Week planner: seven day columns, assigned recipes with chosen servings, drag between days, and a generate-grocery-list action. 4. Grocery list: items merged by ingredient and grouped by aisle, check-off state, manual additions, and a plain-text export. CORE CAPABILITIES 1. a URL importer that parses schema.org recipe markup into clean ingredients and steps 2. a recipe library with tags, search, and serving-size scaling 3. a weekly meal plan that assigns recipes to days 4. an aggregated grocery list that merges quantities and groups items by aisle 5. a cook mode with large-type steps and a kept-awake screen DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Fetch recipe pages server-side with timeouts and size caps, parse only schema.org Recipe markup, and always show the parsed result for review before saving anything. 2. Store ingredient quantities as structured amount, unit, and name so scaling and list aggregation are arithmetic, not string surgery. 3. Merge grocery items only when ingredient name and unit are compatible; otherwise keep both lines rather than guessing a conversion. 4. Keep aisle assignments as an editable per-household mapping and remember corrections for every future list. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Recipe, Ingredient, PlanEntry, GroceryList, GroceryItem. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Blade views and ordinary forms. Use Livewire for focused server-driven interactions and Alpine.js only for small local interface state. The core workflow must remain understandable without relying on a client-side application shell. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Laravel, PHP, Blade, Livewire, and Alpine.js. Use controllers and Blade forms for durable navigation, Livewire for focused interactions, Form Requests for validation, Policies and Gates for authorization, and small application actions or services for domain transitions. Use Eloquent with migrations, database constraints, and transactions; Laravel Storage for private S3-compatible files; queued Jobs for retryable work; the Scheduler for recurring work; and Notifications or Mail for email. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, HTMX, D1 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with schema.org recipe extraction and Screen Wake Lock API. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Fetch recipe pages server-side with timeouts and size caps, and store only the structured recipe the user reviewed and chose to save. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. Given a page with valid recipe markup, importing produces editable ingredients and steps and saves nothing without the cook’s confirmation. 2. Given two planned recipes that both need onions in compatible units, the grocery list contains one onion line with the summed quantity. 3. Given cook mode is open, the screen stays awake through a slow braise and the current step survives an accidental page refresh. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
You are building a production-ready software product named “Stewpot”, a deliberately focused alternative to Paprika Recipe Manager. Build a complete, usable vertical slice—not a landing page, static mockup, or disconnected collection of components. WORKING AGREEMENT Before writing implementation code, produce a short technical plan that names the routes or pages, server actions or endpoints, data tables, important state transitions, authorization boundaries, background jobs, and external adapters. Resolve contradictions in favor of the narrow audience and non-goals below. Prefer a small, legible architecture over speculative abstraction, but do not omit persistence, validation, error handling, or tests. PRODUCT BRIEF Primary user: one home cook planning dinners for the household. Primary outcome: import recipes cleanly, plan the week, and shop from one aggregated list. Product principle: optimize the exact workflow below instead of copying the full breadth of Paprika Recipe Manager. A first-time user should understand what to do from the interface itself, without a tour or documentation. END-TO-END USER JOURNEYS Implement all of these flows through the real interface and persistent data layer: 1. The cook pastes a recipe URL, watches the importer parse schema.org markup into ingredients and steps, fixes one quantity, tags the recipe, and saves it to the library. 2. The cook assigns recipes to the week’s days, scales one dinner from four servings to six, and generates a grocery list with quantities merged and grouped by aisle. 3. In the kitchen, the cook opens cook mode, works through large-type steps with the screen kept awake, and later checks off grocery items at the store from a phone. SCREENS AND INFORMATION ARCHITECTURE Build these as coherent responsive views. Each screen must specify its primary action, secondary actions, visible status, validation feedback, empty state, loading or pending state, success confirmation, and recoverable failure state. 1. Library: recipe cards with photo, tags, source domain, search, serving count, and a prominent import-from-URL action. 2. Recipe detail: ingredients with a serving-size scaler, numbered steps, notes, source link, and add-to-plan and cook-mode actions. 3. Week planner: seven day columns, assigned recipes with chosen servings, drag between days, and a generate-grocery-list action. 4. Grocery list: items merged by ingredient and grouped by aisle, check-off state, manual additions, and a plain-text export. CORE CAPABILITIES 1. a URL importer that parses schema.org recipe markup into clean ingredients and steps 2. a recipe library with tags, search, and serving-size scaling 3. a weekly meal plan that assigns recipes to days 4. an aggregated grocery list that merges quantities and groups items by aisle 5. a cook mode with large-type steps and a kept-awake screen DETAILED BEHAVIOR AND BUSINESS RULES Treat these as server-enforced product requirements, not interface suggestions: 1. Fetch recipe pages server-side with timeouts and size caps, parse only schema.org Recipe markup, and always show the parsed result for review before saving anything. 2. Store ingredient quantities as structured amount, unit, and name so scaling and list aggregation are arithmetic, not string surgery. 3. Merge grocery items only when ingredient name and unit are compatible; otherwise keep both lines rather than guessing a conversion. 4. Keep aisle assignments as an editable per-household mapping and remember corrections for every future list. DATA MODEL AND LIFECYCLE Design a small relational schema centered on Recipe, Ingredient, PlanEntry, GroceryList, GroceryItem. Before implementing it, document: 1. Each table’s purpose, primary key, ownership or tenant boundary, timestamps, status fields, and important attributes. 2. Foreign keys, uniqueness constraints, check constraints, indexes needed by the named screens, and transaction boundaries for multi-record changes. 3. The allowed lifecycle or state transitions, who may trigger each transition, which transitions are terminal or reversible, and what audit history must remain immutable. 4. Archive, retention, and deletion behavior, including what happens to dependent records and external files. 5. Idempotency strategy for submissions, jobs, imports, notifications, webhooks, or retries where applicable. Use migrations rather than ad-hoc schema creation. Store time instants consistently and retain named timezone context whenever local schedules or dates matter. Never rely on a counter, disabled button, or client-side check to preserve a business invariant. USERS, AUTHENTICATION, AND PERMISSIONS Implement only the roles required by the stated audience. Make the ownership and visibility model explicit before coding. Enforce authorization in every server-side query and mutation, including search, exports, attachments, live updates, and guessed URLs—not merely by hiding controls. Use secure session defaults, protect state-changing requests, and provide an understandable signed-out, expired-session, and forbidden state. Seed distinct users when multiple roles are required so permissions can be demonstrated and tested. INTERACTION AND VISUAL DIRECTION The product should feel fast, calm, focused, and credible rather than like a generic admin template. Use a clear visual hierarchy, restrained color, readable typography, generous hit targets, and consistent placement for primary actions. Start with server-rendered HTML and progressively enhance only the interactions that benefit from it. The core workflow must remain understandable if enhancement fails. Start with server-rendered Rails views and ordinary forms. Use Turbo for navigation, submissions, and server-driven updates, then Stimulus only for small browser-side behavior. Do not turn the product into a client-side SPA, and keep the core workflow usable when enhancement fails. Design mobile layouts intentionally instead of simply stacking desktop panels. Support keyboard navigation, visible focus, semantic landmarks, explicit labels, useful page titles, reduced-motion preferences, and screen-reader announcements for asynchronous results. Never use color alone to communicate state. Destructive actions require clear scope and confirmation; safe repeated actions should be idempotent. TECHNICAL DIRECTION Build this version with Ruby on Rails and Hotwire: Turbo for navigation, form submissions, and server-driven updates, and Stimulus for small browser-side behavior. Use RESTful controllers with strong parameters and explicit authorization, with domain transitions in testable models or small application services. Use Active Record migrations plus database-level constraints and transactions; Active Storage with an S3-compatible service for private files; Active Job with a durable queue backend for retryable work; Action Mailer for email; and Action Cable only when live updates are required. Keep domain rules in testable server-side modules instead of route handlers or UI components. Separate persistence, external providers, and background work behind small interfaces without building a framework. Prefer ordinary HTML forms and URLs for durable navigation; use optimistic interaction only when failure can be reconciled clearly. The product brief currently identifies Astro, HTMX, D1 as capability context. Preserve any required native, browser-only, edge, storage, real-time, or background-processing capability through a narrow adapter appropriate to the selected framework. If the core workflow genuinely requires native or browser APIs, keep that runtime as the primary execution surface rather than simulating inaccessible capabilities or inventing an unnecessary web surface. Integrate with schema.org recipe extraction and Screen Wake Lock API. For every integration: - List required environment variables in an .env.example without real secrets. - Add a small adapter with timeouts, normalized errors, and a deterministic local fake or development path. - Verify inbound signatures and deduplicate provider events where supported. - Keep credentials server-side, encrypt long-lived provider tokens at rest, and redact secrets and sensitive payloads from logs. - Define retry, backoff, and idempotency behavior for any side effect that can be repeated. SECURITY AND PRIVACY Fetch recipe pages server-side with timeouts and size caps, and store only the structured recipe the user reviewed and chose to save. Validate, normalize, and length-limit all untrusted input on the server. Escape rendered content by default, sanitize any intentionally accepted markup, rate-limit public or abuse-prone actions, and use private object storage plus short-lived authorized URLs for sensitive files. Collect the minimum personal data necessary for the named workflow. Document retention and deletion behavior. Add specific protections for the riskier surfaces in this app, such as uploads, redirects, outbound requests, email delivery, OAuth, webhooks, CSV import or export, and real-time connections. ACCEPTANCE SCENARIOS Automate these app-specific scenarios at the most appropriate level: 1. Given a page with valid recipe markup, importing produces editable ingredients and steps and saves nothing without the cook’s confirmation. 2. Given two planned recipes that both need onions in compatible units, the grocery list contains one onion line with the summed quantity. 3. Given cook mode is open, the screen stays awake through a slow braise and the current step survives an accidental page refresh. TESTING Add focused unit tests for state transitions, authorization predicates, normalization, date or money calculations, and other risky domain rules. Add integration tests for persistence constraints and each external adapter’s success, timeout, retry, and rejection paths. Add at least one browser-level test for every end-to-end journey above, including one small-screen viewport. Tests must use isolated data and run through a documented single command. OPERATIONS AND FAILURE RECOVERY Add structured server logs with request, job, or event correlation IDs but no secrets or unnecessarily sensitive data. Make failures actionable in both the interface and logs. Background work must expose pending, succeeded, failed, and retrying states where relevant; do not silently swallow errors. Include safe database migration and rollback guidance, seed data, backup and restore notes, external-data cleanup behavior, and a basic health or diagnostic path appropriate to the stack. DELIVERABLES Ship the working application, migrations, representative seed data, tests, .env.example, and a concise README. The README must cover prerequisites, local setup, environment variables, migrations, seed and test commands, deployment, integration setup, backup and restore, security decisions, and known limitations. Seed data should exercise the happy path plus at least one empty, failed, overdue, expired, archived, or permission-restricted state relevant to the product. DEFINITION OF DONE The app is complete when a fresh developer can follow the README, create and migrate the database, run the app, sign in as each relevant role, complete every named journey using real persisted data, refresh without losing state, recover from common failures, and use the core interface on phone and desktop. All acceptance scenarios pass, permission boundaries are covered by tests, and no core screen is left as a placeholder. NON-GOALS Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
Build just one piece
Not ready to replace all of Paprika Recipe Manager? Fine. These are the peculiar sub-problems hiding inside it — the parts that are actually interesting to build. Each one is a standalone prompt, scoped to an evening, no strings attached to the full build.
The parser that finds the recipe under the life storyschema.org markup in the wild: @graph soup, string steps, and three formats per site.
Build a recipe importer that parses schema.org markup from arbitrary URLs. Fetch the page server-side with a timeout and a response-size cap, then dig out the Recipe object. Real-world markup is hostile: JSON-LD might be a bare object, an array, or buried in an @graph list next to Organization and BreadcrumbList nodes; @type can be a string or an array; some sites still use microdata instead of JSON-LD. Handle all of it. Instructions arrive as plain strings, arrays of strings, HowToStep objects, or HowToSection groups that need flattening; images arrive as a URL, an object, or an array. Extract title, ingredient lines, ordered steps, servings, and times, strip the HTML entities and embedded tags that infest ingredient strings, and always show the parsed result for the cook to review and correct before anything saves. A page without recipe markup gets a clear explanation, not a crash. Done when: recipes import cleanly from three structurally different real sites, malformed markup degrades to a helpful error, and nothing persists without explicit confirmation.
The ingredient scaler that knows what ½ meansParse “1 ½ cups flour, sifted” into numbers you can actually multiply.
Build structured ingredient parsing and serving-size scaling for recipes. Ingredient lines arrive as prose: 1 1/2 cups flour, ½ tsp salt, 2-3 cloves garlic, a pinch of nutmeg. Parse each into amount, unit, and name, handling unicode fraction characters, mixed numbers, ranges (scale both ends), and unitless items like 2 eggs. Whatever refuses to parse keeps its original text and is marked unscalable rather than mangled by guesswork. Scaling from 4 servings to 6 multiplies amounts by 1.5 and then renders them back as kitchen-friendly quantities: 2.25 cups displays as 2 ¼ cups, and awkward results snap to the nearest sensible kitchen fraction instead of showing 0.66666 cups. Keep the original parse immutable and scale at render time, so returning to 4 servings restores the exact original numbers with no accumulated rounding drift. Done when: 1 ½ cups scaled to 1.5x renders as 2 ¼ cups, ranges and unitless counts scale correctly, and unparseable lines pass through untouched and clearly flagged.
The grocery list that merges onions but never guessesTwo recipes, one onion line. Cups and grams stay separate on principle.
Build grocery list aggregation from a week of planned recipes. Collect every ingredient from every planned recipe at its chosen serving scale, then merge: two lines combine only when their normalized ingredient names match and their units are compatible, 200g flour plus 300g flour is 500g flour, but 1 cup flour plus 200g flour stays as two lines, because guessing density conversions is how you buy the wrong amount. Normalize names just enough to merge (case, whitespace, simple plurals like onion and onions) without collapsing genuinely different items like red onion into onion. Group the merged list by aisle using a per-household mapping: when the cook drags an item to a different aisle, remember that assignment for every future list. Unknown items land in an unsorted section instead of a wrong guess. Keep check-off state and manual additions, and export as plain text. Done when: compatible duplicates merge with summed quantities, incompatible units coexist as separate lines, and an aisle correction made this week is remembered next week.
The cook mode that outlasts a three-hour braiseScreen awake, current step saved, greasy-thumb-sized controls.
Build a kitchen cook mode for recipe steps. One step at a time in large type, with previous and next controls big enough for a greasy thumb, plus the ingredient amounts relevant to the current step visible without navigating away. Two reliability problems make it interesting. First, the screen: acquire a wake lock via the Screen Wake Lock API so the display survives a slow braise, and reacquire it on the visibilitychange event, because the lock is silently released whenever the cook switches to check a message. Show an unobtrusive indicator when the lock is active, and degrade gracefully on browsers without the API. Second, state: persist the current step index locally on every navigation, so an accidental refresh, a crashed tab, or a phone reboot restores the cook to the exact step they were on, with a resume prompt rather than a jarring jump. Done when: the screen stays awake through backgrounding and returning, a refresh mid-recipe resumes on the correct step, and unsupported browsers still work minus the wake lock.
Frequently asked questions
How long does it take to build your own Paprika Recipe Manager?
A basic version — url import, recipes, scaled grocery list — takes about 6 hours. Roughly 2 days gets you a solid v1 with photos, cook timers, plan templates, list sharing. Matching everything Paprika Recipe Manager really does (native apps, cloud sync, pantry tracking) is closer to 1 month+, which is exactly why you should scope down instead.
How much does Paprika Recipe Manager cost if I keep subscribing?
Paprika Recipe Manager runs $2.5–$5 per month on public paid plans, which is $30–$60 per year. A focused self-built replacement costs your build time plus close-to-zero hosting.
What stack should I use to build a Paprika Recipe Manager alternative?
The build prompt on this page ships in four flavors: the AHA stack (Astro, HTMX, Alpine.js), Next.js, Laravel, and Ruby on Rails. The capability context for this product is Astro, HTMX, D1. Pick the stack you already know — the scope matters more than the framework.
What features does a minimal Paprika Recipe Manager replacement need?
A useful v1 needs: a URL importer that parses schema.org recipe markup into clean ingredients and steps; a recipe library with tags, search, and serving-size scaling; a weekly meal plan that assigns recipes to days; an aggregated grocery list that merges quantities and groups items by aisle; a cook mode with large-type steps and a kept-awake screen. Everything else is scope creep until you personally miss it.
What should I deliberately not build?
Do not build nutrition analysis, pantry inventory, social recipe sharing, or native mobile apps.
Does this build also replace Mela and Crouton?
Yes. Paprika Recipe Manager, Mela and Crouton all solve the same core job — import recipes cleanly, plan the week, and shop from one aggregated list. The scoped v1 on this page covers what most people use any of them for, so one focused build replaces whichever you currently pay for.