Authoring Recipes

Guidelines for writing fullstackrecipes content. This skill is for maintainers building out the fullstackrecipes project itself, not for developers consuming the stack (see use-fullstackrecipes for that).

fullstackrecipes is a site that helps developers and agents build better full stack apps by shipping an opinionated stack with setup instructions, best practices, and ready-to-clone starting points. It exposes four kinds of resources: setup recipes, skills, cookbooks, and templates.

Two Skill Directories — Don't Confuse Them

This repo contains two separate skills/ trees. They serve opposite audiences:

• ./skills/ — the skills this repo exposes/ships to consumers. These are the day-to-day, agent-facing workflow guides (drizzle-queries, authentication-best-practices, workflow-best-practices, etc.) that the website reads (and serves as Markdown via the .md endpoints) and that consumers install via bunx skills add. When this skill says "a skill," it means one of these.
• ./.agents/skills/ — the skills used internally by this workspace to build the fullstackrecipes project. This very authoring-recipes skill lives here. These are not exposed to consumers and are not part of the resource catalog.

When authoring or editing an exposed skill, you edit it under ./skills/<slug>/SKILL.md. Never put consumer-facing skill content in .agents/skills/.

Recipe Tiers

Every catalog item is one of three tiers, plus an optional template attached to a cookbook. The tier determines what it installs and what its prose may assume. The single source of truth for the catalog (slugs, titles, descriptions, tags, requires, and template links) is src/lib/recipes/data.tsx.