home / skills / andrelandgraf / fullstackrecipes / use-fullstackrecipes

use-fullstackrecipes skill

/skills/use-fullstackrecipes

This skill helps you discover and follow production-ready fullstack recipes to accelerate setup, skills, and cookbooks for AI apps.

npx playbooks add skill andrelandgraf/fullstackrecipes --skill use-fullstackrecipes

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
474 B
---
name: use-fullstackrecipes
description: Discover and follow recipes via MCP resources for setup guides, skills, and cookbooks. The meta-skill for using fullstackrecipes effectively.
---

# Building with fullstackrecipes

Discover and follow recipes via MCP resources for setup guides, skills, and cookbooks. The meta-skill for using fullstackrecipes effectively.

```bash
curl -H "Accept: text/markdown" https://fullstackrecipes.com/api/recipes/use-fullstackrecipes
```

Overview

This skill helps you discover, follow, and apply production-ready recipes from the fullstackrecipes collection. It acts as a meta-skill that guides setup, integration, and adaptation of patterns, cookbooks, and step-by-step guides for full stack web AI apps. Use it to streamline onboarding, enforce consistent architecture, and accelerate feature delivery.

How this skill works

The skill queries the fullstackrecipes catalog to surface relevant recipes, setup guides, and code patterns. It highlights prerequisites, step sequences, and recommended files or components to modify. It can produce actionable checklists or copyable commands so you can apply recipes directly to your project.

When to use it

  • Starting a new full stack AI project and needing production-ready patterns
  • Onboarding team members to a consistent architecture and tooling
  • Integrating a specific feature (auth, uploads, deployments) with minimal guesswork
  • Migrating to opinionated defaults (file structure, components, deployment)
  • Creating internal docs or runbooks based on vetted cookbooks

Best practices

  • Read the recipe prerequisites first to ensure environment compatibility
  • Apply recipes incrementally and test each step locally before committing
  • Adapt patterns to your project's conventions instead of copying blindly
  • Keep track of recipe versions and notes for reproducibility
  • Use recipes as a starting point; customize security and performance settings

Example use cases

  • Follow a step-by-step guide to add user authentication with recommended UI components
  • Implement a file upload flow using a tested backend and storage pattern
  • Adopt deployment recipes to set up CI/CD with environment-specific tweaks
  • Create a consistent component library by following the registry's component patterns
  • Draft a team onboarding checklist that references specific setup recipes

FAQ

Can I customize recipes for my codebase?

Yes. Recipes are templates and patterns meant to be adapted; follow prerequisites but modify code to match your conventions.

Are recipes production-ready out of the box?

Recipes are designed to be production-ready patterns, but you should validate security, performance, and environment specifics before deploying.