create-jay 0.25.4 → 0.25.5

package/dist/index.js

@@ -264,7 +264,9 @@ async function scaffoldProject(projectDir, name, selectedPlugins) {
   writeFile(projectDir, ".jay", readTemplate("jay-config.yaml"));
   writeFile(projectDir, "vite.config.ts", readTemplate("vite.config.ts"));
   writeFile(projectDir, "tsconfig.json", readTemplate("tsconfig.json"));
-  writeFile(projectDir, "CLAUDE.md", readTemplate("CLAUDE.md"));
+  const agentGuidance = readTemplate("CLAUDE.md");
+  writeFile(projectDir, "CLAUDE.md", agentGuidance);
+  writeFile(projectDir, "agents.md", agentGuidance);
   const hasDesignValidator = selectedPlugins.some(
     (p) => p.name === "@jay-framework/design-system-validator"
   );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-jay",
-  "version": "0.25.4",
+  "version": "0.25.5",
   "type": "module",
   "description": "Create a new Jay Stack project",
   "license": "Apache-2.0",

package/skills/jay/SKILL.md

@@ -23,6 +23,21 @@ guides). After scaffolding, read those.
   server-side via the Claude Agent SDK. Its authentication matches Claude Code: install the `claude`
   CLI, then either set `ANTHROPIC_API_KEY` in the environment **or** run `claude login`. Without this
   the project still scaffolds, builds, and runs — only the `/aiditor` route's agent won't run.
+- **For any Wix plugin (`wix-stores` / `wix-members` / `wix-media` / `wix-data` / `wix-deploy`): a Wix
+  account + a browser login.** All Wix plugins share one credential owner,
+  `@jay-framework/wix-server-client`, which is pulled in automatically when you select any `wix-*`
+  plugin. Its setup is **interactive** — during `setup` it shells out to the Wix CLI
+  (`npx @wix/cli login`, opening a browser for OAuth) and, if the project isn't connected to a site yet,
+  runs `npm create @wix/new init` to connect one. From there it fetches the app secret and writes
+  `config/.wix.yaml` for you — you are **not** prompted for an API key, site ID, or client ID (those are
+  derived or fetched). Notes:
+  - This step **requires interactive mode.** In non-interactive / CI runs it is skipped with a
+    `needs-config` note; re-run `yarn setup` in a terminal to complete it.
+  - **`wix-deploy` additionally needs a live Wix login at deploy time** (`yarn wix:deploy`) — it uses
+    the Wix CLI session in `~/.wix`. If that session is missing it errors with "Run `wix login` first";
+    just run `npx @wix/cli login` again.
+  - **API key is optional / manual.** The default flow uses the auto-fetched app secret; only hand-edit
+    an `apiKey` into `config/.wix.yaml` if you deliberately choose the API-key strategy.
 
 ## 1 · Scaffold the project
 
@@ -54,6 +69,38 @@ The scaffolder then, in order: creates `./<name>/`, installs dependencies, gener
 complete non-interactively (e.g. a plugin needing credentials) is skipped with a note and can be re-run
 later with `yarn setup`.
 
+### Completing setup non-interactively (agents / CI)
+
+`jay-stack-cli setup` has three input modes:
+
+- `--interactive` — prompts a human in the terminal.
+- `--answers <file>` — reads answers from a YAML file (for agents).
+- _(neither)_ — surfaces every needed answer instead of prompting.
+
+When a plugin needs a value it can't get, setup does **not** hang or guess — it prints a structured,
+machine-readable block and exits that plugin:
+
+```
+setup-needs-answer:
+  plugin: @jay-framework/some-plugin
+  key: apiKey
+  type: input
+  message: "Enter your API key"
+  choices:          # only present for select-type questions
+    - us: United States
+```
+
+**The loop for an agent:** run `yarn setup` → for each `setup-needs-answer:` block, add a line
+`<key>: "<value>"` to an `answers.yaml` → re-run `jay-stack-cli setup --answers answers.yaml`. Any value
+still missing surfaces again as another `setup-needs-answer:`; repeat until none remain. The `key` is the
+stable join field between the question and your answer.
+
+**Exception — Wix login is not answerable via file.** The Wix plugins' credential setup shells out to
+the Wix CLI for a browser-based OAuth login (`npx @wix/cli login`). In non-interactive mode it returns a
+`needs-config` note ("requires interactive mode"), **not** a `setup-needs-answer:` — there is no key you
+can put in `answers.yaml` for it. A human must run `yarn setup` in a real terminal once to complete the
+Wix login; everything else (app secret, client ID, site ID) is fetched/derived automatically after that.
+
 ## 2 · What you get
 
 ```

package/templates/CLAUDE.md

@@ -6,6 +6,17 @@ This is a Jay Stack project.
 
 Run `yarn setup` then `yarn agent-kit` to generate the agent kit.
 
+### Plugin setup (credentials)
+
+`yarn setup` configures each installed plugin. For agents/CI it is non-interactive: a plugin that needs
+a value exits with a structured `setup-needs-answer:` block (`plugin`/`key`/`type`/`message`/`choices`).
+Put each `<key>: "<value>"` into `answers.yaml` and re-run `jay-stack-cli setup --answers answers.yaml`;
+repeat until every plugin reports `configured`. See `agent-kit/devops/INSTRUCTIONS.md` for the full loop.
+
+**Wix plugins are the exception:** their login is a browser OAuth via the Wix CLI, so it can't be
+answered from a file — run `yarn setup` once in a real terminal to complete it. Everything else (app
+secret, client ID, site ID) is fetched automatically afterward.
+
 Read `agent-kit/` for contracts, plugin references, and role guides — this is the authoritative
 guidance for the agent kit structure, CLI commands, and project organization.