How AislePrompt Recipes Are Made
AislePrompt recipes are drafted by an AI-assisted pipeline and published by AislePrompt Editorial. They are not individually cooked before publication. This page explains what the pipeline draws on, which checks run before a recipe goes live, and how to report a problem.
How a recipe is drafted
Each recipe is drafted programmatically from technique templates, cuisine-specific method libraries, and a master ingredient list. The templates set the method, ratios, timing, and doneness cues that recipes built from them share, so a correction made in a template reaches every recipe built from it. Recipe pages are labeled AI-assisted, and recipe hero images are AI-generated and labeled as such.
What is checked before publication
- Nutrition: values are calculated from USDA FoodData Central (fdc.nal.usda.gov) ingredient data, not estimated by hand.
- Dietary tags: a tag such as keto, Whole30, paleo, gluten-free, or low-sodium is applied by rules that check the ingredient list and macros against that diet's published criteria.
- Labeling claims: "low-fat", "low-sodium", "high-protein", and "sugar-free" follow FDA and USDA labeling conventions.
- Doneness cues: where a recipe gives a temperature target, it also gives a visual or tactile cue for cooks without a probe thermometer.
Ingredients and the Instacart handoff
Every ingredient in the master list is mapped to a UPC or a generic name that Instacart's retailer catalogs stock, so "Order on Instacart" sends the ingredient the recipe calls for rather than a guess.
Corrections
If a recipe, ingredient list, or nutrition value looks wrong, tell us at /feedback. We fix the recipe, and the template behind it when the error came from there.