recipe improvement items

[ryanwaits]

• [ ] list dependencies and versions required to run the code
• [ ] add clarinet browser sdk integration to run clarity examples
• [ ] integrate js repl for running stacks.js examples
• [ ] add/integrate stacks connect examples with ability to preview
• [ ] add chainhook examples using platform api
• [ ] add registry for downloading recipes to local projects, ie npx @hirosystems/recipes add
• [ ] add supporting test files when downloading code locally with registry

[ginny-d]

These are some UI/UX suggestions only:

• Being able to filter by tag
• Maybe create some categorization by use-case instead of by tool. This way we could have some "popular/recommended" for "defi" or "nfts" or "sbtc", etc
• On the grid view, it'd be great if the link to the recipe is the whole card as opposed to the code part, since that's not very intuitive
• On the list view, I'm not sure if the "created on" column really adds any value. Instead we can have a "Last updated on..." inside the recipe page

If these make sense to you I can def help with some mock ups!