
Use Fullstackrecipes
- 190 installs
- 18 repo stars
- Updated June 8, 2026
- andrelandgraf/fullstackrecipes
Apply proven full-stack recipes for auth, data fetching, forms, deployment wiring, and cross-layer patterns when scaffolding or extending a production web application.
About
use-fullstackrecipes from andrelandgraf/fullstackrecipes teaches Claude to follow curated full-stack recipes for web apps, spanning frontend flows, backend APIs, and connecting infrastructure. It suits teams shipping SaaS or content products who want repeatable patterns instead of one-off stack decisions.
- End-to-end full-stack implementation recipes
- Auth, API, and UI composition patterns
- Faster scaffolding across common app shapes
- Consistent conventions from fullstackrecipes repo
- Reduces ad-hoc architecture during build
Use Fullstackrecipes by the numbers
- 190 all-time installs (skills.sh)
- Ranked #2,119 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/andrelandgraf/fullstackrecipes --skill use-fullstackrecipesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 190 |
|---|---|
| repo stars | ★ 18 |
| Last updated | June 8, 2026 |
| Repository | andrelandgraf/fullstackrecipes ↗ |
What it does
Apply proven full-stack recipes for auth, data fetching, forms, deployment wiring, and cross-layer patterns when scaffolding or extending a production web application.
Files
Building with fullstackrecipes
Discover and follow recipes by fetching their Markdown for setup guides, skills, and cookbooks.
How fullstackrecipes Works
Content comes in two types:
1. Setup Recipes (type: "setup"): one-time guides to configure a tool or service (auth, database, payments). Atomic installs with declared prerequisites — adoptable on their own. 2. Skills (type: "skill"): day-to-day patterns for an already-configured tool (querying, auth, logging). They assume the canonical assembled stack and are installed via the skills CLI, not pasted as content.
Cookbooks are ordered, two-phase setups: they run their setup recipes in order, then install the matching skills. After a cookbook completes, the project has both the configured stack and the installed skills. For example, "Base App Setup" configures Next.js, Shadcn UI, Neon Postgres, Drizzle ORM, and the AI SDK, then installs the Drizzle querying skill as its final step.
Fetching Recipes as Markdown
Every page on fullstackrecipes.com has a Markdown twin — append .md to any URL. No MCP server or special tooling required, just curl.
Start with the index to see every recipe and cookbook with its slug:
curl https://fullstackrecipes.com/llms.txtThen fetch the full content of any recipe or cookbook by slug:
# A setup recipe or skill
curl https://fullstackrecipes.com/recipes/neon-drizzle-setup.md
# A cookbook (inlines all of its recipes in order)
curl https://fullstackrecipes.com/recipes/base-app-setup.mdEach .md response includes the title, description, prerequisites, and every step, code example, and file path.
Best Practices
- Follow recipes exactly. They are tested instructions; don't deviate without a specific reason.
- Complete dependencies first. Each recipe's Prerequisites section lists what to finish first — complete a setup recipe before its matching skill.
- Install skills, don't just read them. Skills are installed with
bunx skills add ...so the agent retains the patterns for ongoing work. Installing them is the final step of a cookbook, not optional reading. Install only after their setup recipes are complete. - Check for updates. Recipes evolve with their libraries. When troubleshooting or starting a feature, re-fetch the latest
.mdinstead of relying on cached instructions.
References
- fullstackrecipes.com - Browse all recipes and cookbooks
- Index - Every recipe and cookbook with its slug