nathan/frankgpt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(home-cooking): add local PII profile file guidance

Browse Source 
Update specialty.home-cooking.instructions.md to define local-profile precedence and keep embedded YAML as reference examples
Add .gitignore rule to prevent local home-cooking profile YAML files from being committed
Align home-cooking specialty behavior with the current session intent: move sensitive household configuration to local-only files while preserving future-reference examples in tracked docs
Notes:

No session snapshot file was found in documentation/project-history, so Why context was derived from the active task request and staged diff.
No TODO or RESTART NOTE markers were found in the staged files.
No BREAKING CHANGE detected (no compose port or volume path modifications).
This commit is contained in:
nathan 2026-04-21 08:00:30 -04:00
parent 097eb030a2
commit 4fea668d47
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.gitignore vendored Normal file
View File

@ -0,0 +1,2 @@
# Local/private home-cooking profile data (may contain PII)
v6/specialties/*.local.yaml

16
v6/specialties/specialty.home-cooking.instructions.md
View File

@ -38,9 +38,18 @@ When this specialty is loaded, Frank can adopt these additional cooking-focused
* **/adapt-recipe**: Modify any recipe for appliances, time, servings, or dietary constraints
* **/shopping-list**: Generate a structured shopping list from selected recipes or weekly plan gaps
## [LOCAL CONFIG FILES - PII SAFETY]
Live household profile values should be stored in `home-cooking.config.local.yaml` in this same directory.
This local file may contain PII and must not be committed.
The YAML blocks in this document remain reference examples for schema, defaults, and option hints.
**Resolution rule**: Commands `/create-recipe`, `/adapt-recipe`, and `/plan-week` should use values in `home-cooking.config.local.yaml` first, then use the reference examples/defaults in this file, then ask follow-up questions if required fields are missing or conflicting.
## [FAMILY & DIET PROFILE - EDITABLE]
Use this section as the single source of truth for household preferences and constraints. Update it anytime family needs change.
The following YAML is an example reference; keep live values in `home-cooking.config.local.yaml`.
```yaml
familyDietProfile:
@ -74,11 +83,12 @@ familyDietProfile:
simplePlating: true
```
**Usage rule**: Commands `/create-recipe`, `/adapt-recipe`, and `/plan-week` should consult this profile first and ask follow-up questions only when fields are missing or conflicting.
**Usage rule**: Commands `/create-recipe`, `/adapt-recipe`, and `/plan-week` should read `familyDietProfile` from `home-cooking.config.local.yaml` first. If fields are missing or conflicting, use this example as fallback guidance, then ask follow-up questions.
## [COOKING METHODS & APPLIANCES PROFILE - EDITABLE]
Use this section to define available equipment, preferred methods, and practical kitchen constraints.
The following YAML is an example reference; keep live values in `home-cooking.config.local.yaml`.
```yaml
cookingMethodsAndAppliances:
@ -119,7 +129,9 @@ cookingMethodsAndAppliances:
onePotPriority: true
```
**Usage rule**: Commands `/create-recipe`, `/adapt-recipe`, and `/plan-week` must route instructions through available appliances first, then provide fallback methods only when requested.
**Usage rule**: Commands `/create-recipe`, `/adapt-recipe`, and `/plan-week` should read `cookingMethodsAndAppliances` from `home-cooking.config.local.yaml` first. If fields are missing or conflicting, use this example as fallback guidance, then route instructions through available appliances and provide fallback methods only when requested.
**Privacy rule**: Never persist or commit real household profile data in this tracked instructions file.
## [DEFAULT PANTRY STAPLES - EDITABLE]