{"content":"# Building with fullstackrecipes\n\nDiscover and follow recipes via MCP resources for setup guides, skills, and cookbooks. The meta-skill for using fullstackrecipes effectively.\n\n## How fullstackrecipes Works\n\nfullstackrecipes provides setup instructions for building full-stack applications and skills to work with them. Content is organized into two types:\n\n1. **Setup Recipes**: Step-by-step guides to configure tools and services (e.g., setting up authentication, database, payments)\n2. **Skills**: Instructions for working with previously configured tools (e.g., writing queries, using auth, logging)\n\n**Cookbooks** bundle related recipes together in sequence. For example, \"Base App Setup\" includes Next.js, Shadcn UI, Neon Postgres, Drizzle ORM, and AI SDK setup recipes and skills.\n\n---\n\n## Accessing Recipes via MCP\n\nThe fullstackrecipes MCP server exposes all recipes and cookbooks as resources. Resources are organized by type:\n\n- `recipe://` - Individual setup guides and skills\n- `cookbook://` - Bundled recipe sequences\n\n### Set up MCP Server\n\nIf the MCP server is not already set up, add it with:\n\n```bash\nbunx add-mcp https://fullstackrecipes.com/api/mcp -y\n```\n\nThis updates all detected agents automatically. If no agents are detected, add `-a opencode -a cursor` to the command or prompt the user to specify what agents they want to use for this project.\n\n### List All Resources\n\nUse the `list_resources` tool to get all available recipes and cookbooks:\n\n```\nCall the list_resources tool from fullstackrecipes\n```\n\nThis returns a JSON array of all resources with their URIs, names, descriptions, and types (recipe or cookbook).\n\n### Read a Specific Recipe\n\nFetch the full content of any recipe by its resource URI:\n\n```\nRead the \"neon-drizzle-setup\" resource from fullstackrecipes\n```\n\nThe recipe content includes all steps, code examples, and file paths needed to complete the setup.\n\n### Fallback: Fetch via curl\n\nIf the MCP server is not available, list all recipes via llms.txt:\n\n```bash\ncurl https://fullstackrecipes.com/llms.txt\n```\n\nThen fetch a specific recipe as markdown:\n\n```bash\ncurl -H \"Accept: text/markdown\" https://fullstackrecipes.com/api/recipes/<slug>\n\n# Example: fetch the neon-drizzle-setup recipe\ncurl -H \"Accept: text/markdown\" https://fullstackrecipes.com/api/recipes/neon-drizzle-setup\n```\n\n---\n\n## Best Practices for Following Recipes\n\n### Follow Recipes Exactly\n\nRecipes are tested instructions. Follow them step-by-step without modifications unless you have a specific reason to deviate.\n\n### Complete Dependencies First\n\nSome recipes depend on others. The MCP resource descriptions indicate prerequisites. Complete setup recipes before using their corresponding skills.\n\n### Use Skills for Day-to-Day Work\n\nOnce a tool is configured, use the skill for ongoing development. Skills contain patterns, code examples, and API references that apply to the configured tools.\n\n### Check for Updates\n\nRecipes are updated as libraries evolve. When troubleshooting issues or starting new features, fetch the latest recipe content from the MCP server rather than relying on cached instructions.\n\n---\n\n## Authoring Recipes\n\nWhen writing recipes that include installable utilities, use the `{% registry %}` tag to provide both CLI installation and source code viewing.\n\n### Registry Tag\n\nThe registry tag renders:\n\n1. **Install via shadcn CLI** - A copy-able command to install the utility\n2. **Source code viewer** - Collapsible code block showing the full source\n\nExample usage:\n\n```markdoc\n{% registry items=\"assert\" /%}\n```\n\nThis renders the CLI command and source code from `public/r/assert.json`. Users can install via CLI or copy the code directly.\n\n### Avoid Code Duplication\n\nWhen using a registry tag, **do not duplicate the code** in the recipe. The registry tag handles displaying the source code automatically.\n\nBad:\n\n```markdoc\n{% registry items=\"workflow-stream\" /%}\n\nInstall via the registry above, or create manually:\n\n\\`\\`\\`typescript\n// src/workflows/steps/stream.ts\n// ... same code as registry item ...\n\\`\\`\\`\n```\n\nGood:\n\n```markdoc\n{% registry items=\"workflow-stream\" /%}\n\nImport and use the stream utilities in your workflow:\n\n\\`\\`\\`typescript\nimport { startStream, finishStream } from \"@/workflows/steps/stream\";\n\\`\\`\\`\n```\n\nThe registry tag already provides the installation command and source code. Only add usage examples or explanations that aren't part of the installable code itself.\n\n---\n\n## References\n\n- [fullstackrecipes.com](https://fullstackrecipes.com) - Browse all recipes and cookbooks\n- [MCP Resources](https://fullstackrecipes.com/api/mcp) - Direct MCP server endpoint"}