

Requirements
How To Start
- After hundreds (perhaps thousands) of hours of using these recipes, I rarely need to use any of the CORE Cookbook recipes aside from Recipes RCP-001-001-002-HANDOFF-SNAPSHOT and RCP-001-001-002-HANDOFF-SNAPSHOT, but when I do, they are essential to the functioning of CRAFT. Also, the A.I. reads all of these recipes at the start of each session. This happens quietly in the background. Even though you may never need to call the recipe, the A.I. will know all of them and it helps the A.I. to understand what CRAFT is and how it works. Even if you rarely need to use these recipes, they are still working for you and are essential to the CRAFT Framework.
- Provide the recipe directive with source parameters: #H->AI::Directive: (Please execute the Single Recipe Runner with these parameters: * source_type: [file/url] * source: [path or URL] )
- For file sources: – Verify .txt extension for security – Read and parse file contents – Extract recipe code from markers For URL sources: – Fetch page content – Check domain against CRAFTFramework.ai – Warn for non-official sources – Require explicit consent to proceed
- Verify CRAFT standards compliance: – Required elements present (recipe_id, title, description, parameters, prompt_template) – Recipe ID follows RCP-XXX-XXX-XXX-NAME format – Proper version numbering
- Verify required sections: – Step markers or phase structure present – CRAFT comment formatting (H->AI, AI->H) – Clear execution flow defined
- Scan for suspicious patterns: – Dangerous file operations – Code injection risks – System command execution – Unauthorized file access Block recipes with security concerns.
- Present validated recipe summary: – Recipe ID and name – Description and difficulty – Required parameters User chooses: review, execute, or cancel.
- If executing, collect required parameters: – Present each required parameter – Show available options if defined – Validate parameter types
- Execute the imported recipe: – Store in session memory – Run prompt_template with parameters – Report success or handle errors Note: Imported recipes persist only for the current session.
When to Use This Recipe
Recipe FAQ
A: Only .txt files are accepted for security reasons. Q: Can I import recipes from any URL?
A: Yes, but non-CRAFTFramework.ai sources trigger a
security warning requiring explicit consent. Q: Do imported recipes persist across sessions?
A: No, imported recipes are available only for the
current session. Q: What happens if validation fails?
A: The recipe provides specific error details and
does not execute invalid or unsafe recipes.
