@jskit-ai/create-app 0.1.68 → 0.1.70

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jskit-ai/create-app",
-  "version": "0.1.68",
+  "version": "0.1.70",
   "description": "Scaffold minimal JSKIT app shells.",
   "type": "module",
   "files": [

package/src/server/index.js

@@ -220,7 +220,9 @@ function printUsage(stream = process.stderr) {
   stream.write("Usage: jskit-create-app [app-name] [options]\n");
   stream.write("\n");
   stream.write("Options:\n");
-  stream.write(`  --template <name>  Template folder under templates/ (default: ${DEFAULT_TEMPLATE})\n`);
+  stream.write(
+    `  --template <name>  Template folder under templates/ (default: ${DEFAULT_TEMPLATE}; use ai-seed for the minimal AI seed flow)\n`
+  );
   stream.write("  --title <text>     App title used for template replacements\n");
   stream.write("  --target <path>    Target directory (default: ./<app-name>)\n");
   stream.write("  --initial-bundles <preset>  Optional bundle preset: none | auth (default: none)\n");
@@ -609,6 +611,9 @@ export async function runCli(
     });
 
     const targetLabel = toRelativeTargetLabel(path.resolve(cwd), result.targetDirectory);
+    const normalizedTemplateName = normalizeTemplatePathSegments(result.template).join("/");
+    const isAiSeedTemplate = normalizedTemplateName === "ai-seed";
+    const wrotePackageJson = result.touchedFiles.includes("package.json");
     if (result.dryRun) {
       stdout.write(
         `[dry-run] Would create app "${result.appName}" from template "${result.template}" at ${targetLabel}.\n`
@@ -625,10 +630,17 @@ export async function runCli(
       stdout.write("\n");
       stdout.write("Next steps:\n");
       stdout.write(`- cd ${shellQuote(targetLabel)}\n`);
-      stdout.write("- npm install\n");
-      stdout.write("- npm run dev\n");
+      if (isAiSeedTemplate) {
+        stdout.write("- hand the repo to your AI agent and have it read AGENTS.md\n");
+        stdout.write(
+          `- once the Stage 1 shape is clear, let it run npx @jskit-ai/create-app ${shellQuote(result.appName)} --target . --force --tenancy-mode <mode>\n`
+        );
+      } else if (wrotePackageJson) {
+        stdout.write("- npm install\n");
+        stdout.write("- npm run dev\n");
+      }
 
-      if (result.selectedSetupCommands.length > 0) {
+      if (!isAiSeedTemplate && result.selectedSetupCommands.length > 0) {
         stdout.write("\n");
         stdout.write(`Initial framework setup commands (${result.initialBundles}):\n`);
         for (const command of result.selectedSetupCommands) {

package/templates/ai-seed/AGENTS.md

@@ -0,0 +1,38 @@
+# AI Seed Instructions
+
+This workspace is intentionally only a JSKIT seed scaffold. It is not a real JSKIT app yet.
+
+Use this file only for the initial JSKIT setup conversation.
+
+If you need more JSKIT documentation before the real scaffold exists, use:
+
+- `https://github.com/mobily-enterprises/jskit-ai/blob/main/packages/agent-docs/site/guide/index.md`
+- `https://github.com/mobily-enterprises/jskit-ai/blob/main/packages/agent-docs/site/guide/app-setup/initial-scaffolding.md`
+- `https://github.com/mobily-enterprises/jskit-ai/blob/main/packages/agent-docs/site/guide/app-setup/quickstart.md`
+- `https://github.com/mobily-enterprises/jskit-ai/blob/main/packages/agent-docs/site/guide/app-setup/working-with-the-jskit-cli.md`
+
+What to do now:
+
+1. Ask only the Stage 1 setup questions first:
+   - app purpose
+   - tenancy mode: `none`, `personal`, or `workspaces`
+   - database engine: MySQL or Postgres
+   - auth provider
+   - whether the baseline should include users, console, workspaces, realtime, or assistant
+2. If a database-backed baseline is selected, do not stop at the engine name. Confirm one of these is true before moving on:
+   - the target database already exists and the app connection values are known
+   - or the developer has enough local admin or create-database access for the chosen engine to create it now
+3. Once the baseline package stack is clear, ask plainly for the exact local development setup values needed for the next chosen install step. Use the real env var names or option names instead of vague requests for "credentials".
+4. Treat those values as routine local development setup inputs, not production secrets. Examples:
+   - `DB_HOST`, `DB_PORT`, `DB_NAME`, `DB_USER`, `DB_PASSWORD`
+   - `AUTH_SUPABASE_URL`, `AUTH_SUPABASE_PUBLISHABLE_KEY`, `APP_PUBLIC_URL`
+   - `OPENAI_API_KEY` if assistant support is selected
+5. For MySQL or Postgres, if the database does not exist yet, ask for whatever local admin or create-database access is needed to create it, then make sure the database exists before promoting the scaffold. Do not move on while the database is still hypothetical.
+6. If assistant support is selected, explain that `OPENAI_API_KEY` can be given now or wired later; the scaffold can still be created first.
+7. Do not hand-write JSKIT runtime files or invent file topology in this seed workspace.
+8. Once the Stage 1 decisions are clear, promote this directory into the real app scaffold by running:
+   `npx @jskit-ai/create-app <app-name> --target . --force --tenancy-mode <mode>`
+   Use the current directory name as `<app-name>` unless the developer explicitly wants a different app name.
+9. After that, run `npm install`.
+10. Then stop, re-read the overwritten `AGENTS.md`, and continue with the normal JSKIT app workflow from that file. Do not rely on memory from the seed stage.
+11. Do not install JSKIT runtime packages until the new app `AGENTS.md` has been re-read.