Recipe contract
copy · verify · understand · adaptgoal → files → checks → interaction → explanation
A recipe is complete only when its imports, manifest dependencies, capabilities, event path, expected UI, and verification boundary are all explicit.
When to use it
Use this checklist whenever you follow or write a Luastra recipe.
- Goal: know the visible behavior before copying code.
- Files: replace exactly the listed files in a fresh starter project.
- Checks: do not continue until luastra check and luastra test report result=PASS.
- Interaction: follow the stated clicks and compare the visible result.
- Boundary: automated checks prove contracts; the named browser or device interaction proves presentation.