feat: add agent-ready install prompts

Add prompt packs and context files for coding agents so API SaaS infrastructure installs can be dry-run, reviewed, and verified as editable source.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: jesseoue

AGENTS.md

@@ -16,6 +16,7 @@ StackFoundry is a public source registry for production SaaS modules. The sharp
 - Current source shape: `registry/modules`, `registry/presets`, `registry/recipes`, and `registry/skills`.
 - Public generated output lives in `public/r` and `apps/web/public/r`; never edit generated registry output by hand.
 - Shared provider/framework/database/platform guidance belongs in `registry/skills/<name>/SKILL.md` and is installed to `.stackfoundry/skills/<name>/SKILL.md`.
+- Agent-ready install prompts and context belong in installable modules such as `agent-ready-installs`; keep them tool-compatible and safe for Cursor, Codex, Claude, and similar coding agents.
 - The hosted web app is Next.js on Vercel. Cloudflare support is an installable registry starter for consuming apps, not this repo's default deployment path.
 
 ## Quality Gates

CHANGELOG.md

@@ -9,6 +9,7 @@
 - Added an installable `cloudflare-next-starter` module for consuming apps while keeping StackFoundry itself on the standard Next.js/Vercel path.
 - Added Vercel AI building blocks: `ai-sdk`, `ai-elements`, and `ai-chatbot-sdk`.
 - Added `cloudflare-kumo-ui` as an optional Cloudflare UI building-block module.
+- Added `agent-ready-installs` with prompt packs and context files for Cursor, Codex, Claude, and similar coding agents.
 - Added docs for recipes, install order, readiness, conventions, and a mirrored docs changelog.
 - Added OpenSSF Scorecard scanning and private vulnerability reporting links.
 

README.md

@@ -9,7 +9,7 @@ shadcn for production SaaS systems.
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)
 ![Next.js](https://img.shields.io/badge/Next.js-16-black)
 ![Vercel](https://img.shields.io/badge/deploy-Vercel-black)
-![Modules](https://img.shields.io/badge/modules-155-orange)
+![Modules](https://img.shields.io/badge/modules-156-orange)
 ![Recipes](https://img.shields.io/badge/recipes-9-purple)
 ![Presets](https://img.shields.io/badge/presets-13-teal)
 ![Inspired by shadcn](https://img.shields.io/badge/inspired%20by-shadcn-111111)
@@ -18,6 +18,8 @@ StackFoundry is a public source registry for the production systems SaaS teams r
 
 Modules install as source files in your app. You review the code, own the code, and keep the maintenance context that ships with it.
 
+StackFoundry installs are also coding-agent-ready: Cursor, Codex, Claude, and similar tools can inspect recipes, dry-run installs, review generated diffs, and follow included prompt packs.
+
 > [!IMPORTANT]
 > The registry is the product. Modules are the unit of value. Recipes are the guided path. Presets are convenience bundles.
 
@@ -43,6 +45,7 @@ pnpm stackfoundry add recipe api-saas-starter --target ./my-app
 The API SaaS recipe installs the path most developer tools, AI APIs, data APIs, and B2B platforms need first:
 
 - API key lifecycle and verification
+- agent-ready prompt packs for Cursor, Codex, Claude, and similar tools
 - usage metering, quotas, and rate limits
 - credit wallet and Stripe billing foundations
 - webhook inbox and outbound delivery
@@ -81,6 +84,7 @@ Every module is expected to include:
 - setup, ownership, and deployment docs
 - verification checklists
 - maintenance skills under `.stackfoundry/skills`
+- prompt packs and context files for agent-ready install/review workflows when needed
 - install metadata for future diff/update safety
 
 ## Registry Coverage
@@ -93,7 +97,7 @@ Current source registry coverage:
 | Database | `drizzle-postgres`, `drizzle-relations`, `neon-postgres`, `supabase-postgres`, `cloudflare-d1` |
 | Auth and tenancy | `clerk-auth`, `orgs-rbac`, `account-modes`, `invites`, `enterprise-sso`, `scim-provisioning` |
 | Billing | `stripe-billing`, `billing-core`, `entitlements`, `credit-wallet`, `one-time-purchases`, `tax-vat` |
-| API product | `api-keys`, `public-api-orpc`, `webhook-inbox`, `webhook-delivery`, `api-docs` |
+| API product | `api-keys`, `agent-ready-installs`, `public-api-orpc`, `webhook-inbox`, `webhook-delivery`, `api-docs` |
 | Operations | `audit-log`, `background-jobs`, `system-health`, `incident-management`, `status-page`, `oncall-alerting` |
 | Analytics and growth | `posthog-analytics`, `tinybird-analytics`, `feature-flags`, `experiments`, `lifecycle-email` |
 | Notifications and comms | `notifications`, `notification-center`, `knock-notifications`, `resend-email`, `product-announcements` |
@@ -105,7 +109,7 @@ Current source registry coverage:
 <details>
 <summary>Current scale</summary>
 
-- 155 ready module manifests
+- 156 ready module manifests
 - 36 canonical categories
 - 13 preset bundles
 - 9 architecture recipes
@@ -121,6 +125,16 @@ The public hierarchy is intentionally simple:
 - Recipes explain the install path and order.
 - Presets are bundles for convenience.
 
+## Agent-Ready Installs
+
+The `agent-ready-installs` module adds prompt packs and context files for Cursor, Codex, Claude, and other coding agents:
+
+```bash
+pnpm stackfoundry add agent-ready-installs --target ./my-app --dry-run
+```
+
+It gives agents a safe workflow for inspecting recipes, dry-running installs, reviewing diffs, checking env notes, and verifying the target app after source lands.
+
 ## Recipes
 
 Recipes are opinionated install paths that explain what to install together and in what order.

apps/web/app/ai-seo.ts

@@ -54,7 +54,7 @@ export function renderLlmsFullTxt() {
     )
     .join("\n\n");
 
-  return `# StackFoundry Full AI Context\n\nStackFoundry helps teams install production SaaS systems as editable source code. The sharp wedge is API SaaS: API keys, usage tracking, quotas, credits, Stripe billing, docs, webhooks, and request visibility.\n\n${pages}\n\n## Coverage\n\nStackFoundry covers foundation, database, auth and tenancy, billing, API products, operations, observability, analytics and growth, docs, SEO, support, security, storage, deployment, provider adapters, and optional AI modules.\n\n## Positioning\n\nUse StackFoundry when a team wants production SaaS capabilities without adopting a black-box starter. The installed code belongs to the target repository and can be edited, reviewed, diffed, migrated, and removed like normal source.\n`;
+  return `# StackFoundry Full AI Context\n\nStackFoundry helps teams install production SaaS systems as editable source code. The sharp wedge is API SaaS: API keys, usage tracking, quotas, credits, Stripe billing, docs, webhooks, and request visibility. Agent-ready installs include prompt packs and context files for Cursor, Codex, Claude, and similar coding agents.\n\n${pages}\n\n## Coverage\n\nStackFoundry covers foundation, database, auth and tenancy, billing, API products, operations, observability, analytics and growth, docs, SEO, support, security, storage, deployment, provider adapters, agent-ready install workflows, and optional AI modules.\n\n## Positioning\n\nUse StackFoundry when a team wants production SaaS capabilities without adopting a black-box starter. The installed code belongs to the target repository and can be edited, reviewed, diffed, migrated, and removed like normal source.\n`;
 }
 
 export function getAiSitemap() {

apps/web/app/docs/page.tsx

@@ -51,6 +51,12 @@ const pathCards = [
       "webhook-delivery",
     ],
   },
+  {
+    title: "Agent-ready installs",
+    eyebrow: "Cursor, Codex, Claude",
+    body: "Use agent-ready-installs when a coding agent should inspect recipes, run dry-runs, review diffs, and follow safe infrastructure install prompts.",
+    modules: ["agent-ready-installs", "api-saas-starter", "api-keys", "usage-metering"],
+  },
   {
     title: "Auth: choose the boundary first",
     eyebrow: "default path",
@@ -154,8 +160,10 @@ const moduleGroups = [
   },
   {
     category: "API product",
-    summary: "Developer-facing APIs, keys, webhooks, docs, and usage visibility.",
+    summary:
+      "Developer-facing APIs, keys, agent-ready prompts, webhooks, docs, and usage visibility.",
     modules: [
+      "agent-ready-installs",
       "api-keys",
       "unkey-api-keys",
       "api-docs",
@@ -239,6 +247,7 @@ const moduleGroups = [
 ];
 
 const moduleMeta: Record<string, { tone: string; domain?: string }> = {
+  "agent-ready-installs": { tone: "api" },
   "next-saas-shell": { tone: "foundation", domain: "nextjs.org" },
   "drizzle-postgres": { tone: "database", domain: "drizzle.team" },
   "drizzle-relations": { tone: "database", domain: "drizzle.team" },
@@ -494,7 +503,7 @@ export default function DocsPage() {
           </div>
           <div className="docs-side-section">
             <h4>
-              Registry <strong>155</strong>
+              Registry <strong>156</strong>
             </h4>
             {moduleGroups.slice(0, 7).map((group) => (
               <a href="#module-catalog" key={group.category}>
@@ -754,7 +763,7 @@ $ pnpm stackfoundry recipe api-saas-starter`}</CodeBlock>
           <a href="#safety">Safety</a>
           <div className="docs-toc-meta">
             <span>Registry-first</span>
-            <span>155 modules</span>
+            <span>156 modules</span>
             <a href="https://github.com/jesseoue/stackfoundry">GitHub →</a>
           </div>
         </aside>

apps/web/app/page.tsx

@@ -22,7 +22,7 @@ type LandingModuleCard = {
 };
 
 const stats = [
-  { value: "155", label: "Modules" },
+  { value: "156", label: "Modules" },
   { value: "13", label: "Presets" },
   { value: "36", label: "Categories" },
   { value: "MIT", label: "License" },
@@ -77,6 +77,24 @@ const moduleCards: LandingModuleCard[] = [
       ],
     },
   },
+  {
+    name: "agent-ready-installs",
+    title: "Agent-Ready Installs",
+    category: "developer platform",
+    version: "ready",
+    description:
+      "Prompt packs and context files for Cursor, Codex, Claude, and other coding agents to install infra safely.",
+    tags: [
+      { label: "agent-ready", tone: "accent" },
+      { label: "prompts", tone: "success" },
+      { label: "Cursor/Codex/Claude", tone: "provider" },
+      { label: "review workflow", tone: "skill" },
+    ],
+    footer: {
+      summary: "4 files · prompts · context JSON",
+      actions: [{ label: "json", href: "/r/agent-ready-installs.json" }],
+    },
+  },
   {
     name: "api-keys",
     title: "API Keys",
@@ -273,7 +291,7 @@ const commandRows: Array<{
 
 const presetRows = [
   ["api-saas-starter", "API-first SaaS", "Keys, usage, credits, billing, webhooks"],
-  ["developer-platform", "Devtools", "Keys, docs, public APIs, usage"],
+  ["agent-ready-installs", "Coding agents", "Prompts, context, dry-run review"],
   ["b2b-saas", "Team products", "RBAC, invites, audit, SSO, SCIM"],
   ["internal-admin", "Operators", "Support, health, incidents, backups"],
   ["ai-saas", "AI products", "Chat, model routing, quotas, metering"],
@@ -282,7 +300,7 @@ const presetRows = [
 const assuranceRows = [
   {
     title: "What installs?",
-    body: "Source files, route shells, helpers, schema slices, docs, maintenance skills, and verification checklists.",
+    body: "Source files, route shells, helpers, schema slices, prompts, docs, maintenance skills, and verification checklists.",
   },
   {
     title: "What stays out?",

apps/web/app/registry/page.tsx

@@ -36,8 +36,8 @@ const featuredPresets = [
   {
     name: "developer-platform",
     title: "Developer Platform",
-    description: "API keys, public API surfaces, webhook delivery, usage, and developer docs.",
-    modules: ["api-keys", "unkey-api-keys", "webhook-inbox", "api-docs", "sdk-snippets"],
+    description: "API keys, agent-ready installs, public API surfaces, webhooks, usage, and docs.",
+    modules: ["api-keys", "agent-ready-installs", "webhook-inbox", "api-docs", "usage-metering"],
     tone: "API",
   },
   {
@@ -167,6 +167,7 @@ const moduleFamilies = [
     description:
       "The strongest wedge: keys, rate limits, usage, credits, public APIs, webhooks, and docs.",
     modules: [
+      "agent-ready-installs",
       "api-keys",
       "unkey-api-keys",
       "unkey-rate-limits",
@@ -335,7 +336,7 @@ const providerOptions = [
 ];
 
 const stats = [
-  ["155", "Module manifests"],
+  ["156", "Module manifests"],
   ["13", "Preset bundles"],
   ["9", "Recipes"],
   ["17", "Provider cards"],
@@ -449,7 +450,7 @@ pnpm stackfoundry diff api-keys --target ./my-app`}</code>
             <p>
               Recipes document the recommended install order for complete SaaS workflows. The
               sharpest path is API SaaS: keys, usage, rate limits, credits, billing, docs, webhooks,
-              and visibility.
+              visibility, and agent-ready install prompts.
             </p>
           </div>
 

docs/changelog.md

@@ -11,8 +11,9 @@ This page mirrors the release changelog and keeps the latest public registry cha
 3. Added an installable `cloudflare-next-starter` module for consuming apps while keeping StackFoundry itself on the standard Next.js/Vercel path.
 4. Added Vercel AI building blocks: `ai-sdk`, `ai-elements`, and `ai-chatbot-sdk`.
 5. Added `cloudflare-kumo-ui` as an optional Cloudflare UI building-block module.
-6. Added docs for recipes, install order, readiness, conventions, and this mirrored changelog.
-7. Added OpenSSF Scorecard scanning and private vulnerability reporting links.
+6. Added `agent-ready-installs` with prompt packs and context files for Cursor, Codex, Claude, and similar coding agents.
+7. Added docs for recipes, install order, readiness, conventions, and this mirrored changelog.
+8. Added OpenSSF Scorecard scanning and private vulnerability reporting links.
 
 ### Changed
 

docs/index.md

@@ -18,5 +18,6 @@
 2. Dry-run the full path: `pnpm stackfoundry add recipe api-saas-starter --target ./my-app --dry-run`.
 3. Read the [Registry](./registry.md), [Recipes](./recipes.md), and [Install order](./install-order.md) docs.
 4. Inspect the first modules in `registry/modules`: `api-keys`, `usage-metering`, `credit-wallet`, `stripe-billing`, and `webhook-delivery`.
-5. Run `pnpm registry:doctor`.
-6. Use [Readiness](./readiness.md) and [Conventions](./conventions.md) before adding new modules.
+5. Add agent-ready prompts when you want Cursor, Codex, Claude, or another coding agent to drive the install: `pnpm stackfoundry add agent-ready-installs --target ./my-app --dry-run`.
+6. Run `pnpm registry:doctor`.
+7. Use [Readiness](./readiness.md) and [Conventions](./conventions.md) before adding new modules.

docs/install-order.md

@@ -8,6 +8,16 @@ The practical first command is:
 pnpm stackfoundry add recipe api-saas-starter --target ./my-app --dry-run
 ```
 
+## Agent Workflow
+
+```text
+agent-ready-installs
+  -> inspect recipe
+  -> dry-run install
+  -> review diff
+  -> verify target app
+```
+
 ## Foundation
 
 ```text