Add user cooking context for personalized recipe generation#70
Merged
Add user cooking context for personalized recipe generation#70
Conversation
Inject free-form cooking preferences (equipment, skill level, cuisine preferences, ingredient substitutions) into AI recipe prompts, enabling more personalized recipe generation without changing the existing dietary requirements flow. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ddd7c48e54
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The UpdatePersonalization repository method copied UnitSystem, Requirements, and UID but omitted CookingContext, silently dropping the value on every update. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Keep middleware wrapping from main (R5) and add CookingContext template parameter from cooking-skills (R8) inside each closure. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
CookingContextfield toPersonalizationmodel -- free-form text where users describe their kitchen equipment, skill level, cuisine preferences, and ingredient substitutions{{.CookingContext}}template variablecooking_contextin the personalization API (read and update) so clients can set itDetails
The field is optional and backward-compatible: empty string means no injection, so existing users get the same behavior as before. No migration file needed -- GORM AutoMigrate handles adding the column.
The cooking context flows through the full stack:
Personalization.CookingContext) -- stored in DBPersonalizationResponse.CookingContext) -- returned via APIUpdatePersonalization) -- acceptscooking_contextin request bodyRecipeRequest.CookingContext) -- carries context to providerprompts.yaml) -- injected after dietary requirementsanthropic.go) -- passes to template renderingTest plan
go build ./...compiles cleanlygo test ./...all tests passPUT /personalizationand confirm it persists🤖 Generated with Claude Code