showpane 0.4.24 → 0.4.25

package/bundle/meta/scaffold-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-13T21:26:42.638Z",
+  "generatedAt": "2026-04-13T22:00:52.340Z",
   "scaffoldVersion": "0.2.7",
   "files": {
     ".env.example": "ed105f2bdcd1888a98181d55e3c9f7d6eff3ae9c3e2366c2e777a12e3caddfa7",

package/bundle/toolchain/CLI_VERSION

@@ -1 +1 @@
-0.4.24
+0.4.25

package/bundle/toolchain/skills/portal-create/SKILL.md

@@ -138,13 +138,8 @@ Store:
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 of guessing with ad-hoc SQL.
 
-Do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or template
-directories just to understand the project. Do not call `check-slug.ts` with
-anything except `--org-id`.
-Do not re-read config, Prisma, or SQLite to rediscover org fields that were already
-returned by `get-org.ts`.
-
-The canonical references for this skill are:
+Once `get-org.ts` succeeds, extra project probing rarely improves the draft.
+Use that result plus the selected template/example as the canonical references:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
@@ -153,6 +148,9 @@ The canonical references for this skill are:
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
 
+For slug checks, use `check-slug.ts` with `--org-id`. Re-reading config, Prisma,
+or SQLite usually just burns time without changing the correct org context.
+
 ### Step 2: Determine the portal slug
 
 If the user provided a slug (e.g., `/portal-create acme-health`), use it. Otherwise, infer from context — the company name mentioned in conversation, a meeting transcript, or ask the user directly.
@@ -215,10 +213,10 @@ Always also read the example portal as your quality and style reference:
 cat "$APP_PATH/src/app/(portal)/client/example/example-client.tsx"
 ```
 
-The template provides content structure. The example provides quality and styling. Match the example's patterns: card styles, typography, spacing, responsive breakpoints. Templates are inspiration, not rigid scaffolds. Adapt the structure to fit the actual content.
-
-Do not search the repo for templates or ask the filesystem where templates live.
-Use the selected template and the exact `SKILL_DIR` path above.
+The template provides structure. The example provides quality and styling.
+Read those directly from the known paths above, then match the example's card
+styles, typography, spacing, and responsive breakpoints. Templates are
+inspiration, not rigid scaffolds.
 
 ### Step 5: Analyze transcript (if available)
 

package/bundle/toolchain/skills/portal-create/SKILL.md.tmpl

@@ -43,13 +43,8 @@ Store:
 If the helper fails, stop and tell the user to run `/portal-setup` again instead
 of guessing with ad-hoc SQL.
 
-Do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or template
-directories just to understand the project. Do not call `check-slug.ts` with
-anything except `--org-id`.
-Do not re-read config, Prisma, or SQLite to rediscover org fields that were already
-returned by `get-org.ts`.
-
-The canonical references for this skill are:
+Once `get-org.ts` succeeds, extra project probing rarely improves the draft.
+Use that result plus the selected template/example as the canonical references:
 
 - the configured `APP_PATH`
 - the configured `ORG_SLUG`
@@ -58,6 +53,9 @@ The canonical references for this skill are:
 - `$SKILL_DIR/templates/<chosen-template>/...`
 - `$APP_PATH/src/app/(portal)/client/example/example-client.tsx`
 
+For slug checks, use `check-slug.ts` with `--org-id`. Re-reading config, Prisma,
+or SQLite usually just burns time without changing the correct org context.
+
 ### Step 2: Determine the portal slug
 
 If the user provided a slug (e.g., `/portal-create acme-health`), use it. Otherwise, infer from context — the company name mentioned in conversation, a meeting transcript, or ask the user directly.
@@ -120,10 +118,10 @@ Always also read the example portal as your quality and style reference:
 cat "$APP_PATH/src/app/(portal)/client/example/example-client.tsx"
 ```
 
-The template provides content structure. The example provides quality and styling. Match the example's patterns: card styles, typography, spacing, responsive breakpoints. Templates are inspiration, not rigid scaffolds. Adapt the structure to fit the actual content.
-
-Do not search the repo for templates or ask the filesystem where templates live.
-Use the selected template and the exact `SKILL_DIR` path above.
+The template provides structure. The example provides quality and styling.
+Read those directly from the known paths above, then match the example's card
+styles, typography, spacing, and responsive breakpoints. Templates are
+inspiration, not rigid scaffolds.
 
 ### Step 5: Analyze transcript (if available)
 

package/bundle/toolchain/skills/portal-onboard/SKILL.md

@@ -262,9 +262,8 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 Use the returned `org.id` as the canonical org id for the rest of the create flow.
 Do not guess schema fields or discover the org via ad-hoc SQLite queries if this helper succeeds.
 
-Also: do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or
-template directories just to reorient yourself. At this point the canonical inputs
-are already known:
+At this point, extra repo reorientation rarely changes the first draft. Use the
+known inputs below and spend the time shaping the portal instead:
 
 - workspace app path
 - org slug
@@ -272,6 +271,9 @@ are already known:
 - selected template
 - optional transcript source
 
+If you need structure or style, read only the selected template and the example
+portal. Other portal skills are for later phases and usually just add latency here.
+
 During this phase:
 
 - suggest a slug if needed
@@ -384,8 +386,10 @@ afterthought unless the user explicitly says they want to stop at local preview.
 
 If cloud auth is missing:
 
-- tell the user to run `showpane login`
-- after login completes, resume from the checkpoint
+- run `showpane login` inline via Bash in the current session
+- if you need to hand control to the user, tell them to run `! showpane login`
+- let it handle sign-in, sign-up, and checkout if needed
+- then resume publish from the checkpoint
 
 If deploy returns `organization_required`:
 

package/bundle/toolchain/skills/portal-onboard/SKILL.md.tmpl

@@ -169,9 +169,8 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 Use the returned `org.id` as the canonical org id for the rest of the create flow.
 Do not guess schema fields or discover the org via ad-hoc SQLite queries if this helper succeeds.
 
-Also: do not probe `showpane --help`, `package.json`, `scripts/`, `prisma/`, or
-template directories just to reorient yourself. At this point the canonical inputs
-are already known:
+At this point, extra repo reorientation rarely changes the first draft. Use the
+known inputs below and spend the time shaping the portal instead:
 
 - workspace app path
 - org slug
@@ -179,6 +178,9 @@ are already known:
 - selected template
 - optional transcript source
 
+If you need structure or style, read only the selected template and the example
+portal. Other portal skills are for later phases and usually just add latency here.
+
 During this phase:
 
 - suggest a slug if needed
@@ -291,8 +293,10 @@ afterthought unless the user explicitly says they want to stop at local preview.
 
 If cloud auth is missing:
 
-- tell the user to run `showpane login`
-- after login completes, resume from the checkpoint
+- run `showpane login` inline via Bash in the current session
+- if you need to hand control to the user, tell them to run `! showpane login`
+- let it handle sign-in, sign-up, and checkout if needed
+- then resume publish from the checkpoint
 
 If deploy returns `organization_required`:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "showpane",
-  "version": "0.4.24",
+  "version": "0.4.25",
   "description": "CLI for Showpane — AI-generated client portals",
   "type": "module",
   "bin": {