Recipes SwiftUI Screen

Pick what dinner needs to be and the grid answers. Each need chip narrows the collections to the ones that can meet every pick, and the tiles that stay reorder by how many of their recipes fit, in a single spring, while the count above them rolls to the new total. Each tile is a solid block with a two-line title (a regular line over a bold one), a line drawing that bleeds off its bottom edge and a round arrow button in a deeper shade of the block. When nothing fits, the grid gives way to an empty state with a way back.

Notes

• RecipeTiles takes its tiles, needs and colours through parameters and reads no theme. Bind selection to keep a person's picks, and handle onOpen to push the collection.
• A tile's needs counts its recipes per need. The default ranking takes the smallest of those counts for the picked needs; when you have the recipes themselves, pass rank and return the exact number that fit.
• The six drawings (RecipeArt: bowl, leaves, pot, fish, loaf and pan) are original line art drawn in code with two stroke weights. RecipeTileArt draws them anywhere, at any size, in the ink and accent you give it; the web preview draws the same paths.
• Tiles move as a grid, not as a list, so VoiceOver reads each one as a button with its title and how many recipes fit. Chips carry the selected trait, and a selection haptic marks every change.
• At accessibility text sizes the grid becomes one column and tiles grow with the text. Reduce Motion replaces the reflow spring with a short fade.
• RecipeTilesExample at the end of RecipeTiles.swift is the screen shown in the preview, with the eyebrow, the two-weight headline and the app's floating bar. Copy it as a starting point.