You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Vercel AI SDK, AI Elements, and Cloudflare Kumo UI modules so teams can install chatbot and UI building blocks as owned source.
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: AGENTS.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,17 +4,19 @@ StackFoundry is a public source registry for production SaaS modules.
4
4
5
5
## Product Rules
6
6
7
-
1. The registry is the product. Presets are only bundles of modules.
8
-
2.Every module must include source files, docs, env notes, tests/checklist, and maintenance instructions.
7
+
1. The registry is the product. Modules are source-delivered capabilities; presets install bundles; recipes explain complete workflow paths and install order.
8
+
2.Published modules must include source files, docs, env notes when needed, tests/checklist, and maintenance skills. Proposal ideas belong in requests or roadmap docs until source exists.
9
9
3. Base scaffolds must stay small. Optional providers are adapters, not hard dependencies.
10
10
4. Do not introduce public-facing references to how the project was authored.
11
11
5. Never commit secrets, `.env.local`, provider credentials, private customer data, local caches, or generated machine metadata.
- Current source shape: `registry/modules`, `registry/presets`, `registry/recipes`, and `registry/skills`.
17
+
- Public generated output lives in `public/r` and `apps/web/public/r`; never edit generated registry output by hand.
18
+
- Shared provider/framework/database/platform guidance belongs in `registry/skills/<name>/SKILL.md` and is installed to `.stackfoundry/skills/<name>/SKILL.md`.
19
+
- 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.
18
20
19
21
## Quality Gates
20
22
@@ -23,8 +25,10 @@ Before moving to a new phase:
23
25
-`git status` is clean except intentional changes.
24
26
- Docs are updated.
25
27
- Module manifests validate.
26
-
- The demo path works from a fresh checkout.
27
-
- Changed modules include skill guidance.
28
+
- Generated registry output is rebuilt when source registry files change.
29
+
- Recipes, presets, and install order are updated when a workflow changes.
30
+
- Changed modules include maintenance skills and checklist updates.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ A module should include:
32
32
-`skill/SKILL.md`
33
33
-`tests/checklist.md`
34
34
35
-
Use `stub` for modules that document a real SaaS capability but do not install source yet. Use `ready` only when the module has installable source files and passes registry validation.
35
+
Use GitHub module/provider requests for proposed capabilities that do not install source yet. Use `ready` only when the module has installable source files and passes registry validation.
36
36
37
37
## Provider Adapters
38
38
@@ -55,7 +55,7 @@ Good public PR shapes:
55
55
56
56
- one new provider adapter
57
57
- one ready module implementation
58
-
- one stub-to-ready promotion
58
+
- one proposal-to-ready module promotion
59
59
- one recipe/preset update with generated registry output
0 commit comments