How To Use Recipes
Recipes are complete build paths for common interaction shapes. Start with Door Interaction if you are new to the framework. Use the other recipes after the target, interactor, and prompt UI pipeline is already working.
Recipe Order
- Door Interaction: one target, one point, one command, one execution outcome.
- Hold And Multi-Tap Interaction: progress-based input patterns.
- Paged Command Surface: large command lists and More/Back controls.
- Custom Requirement And Action: Blueprint availability and state changes.
- Custom Prompt Widget: project UI presentation.
- Multi-Participant Hold: shared route progress.
- Save And Restore Interaction State: persistence after ids are stable.
Recipe Validation Rule
Do not stack several advanced systems at once. Confirm the current recipe in play before adding the next layer. A door interaction that focuses, prompts, activates, and changes state is the base for almost every other recipe.