showpane 0.4.14 → 0.4.16

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

@@ -15,7 +15,7 @@ SHOWPANE_HOME="$HOME/.showpane"
 SHOWPANE_BIN="$SHOWPANE_HOME/bin"
 CONFIG="$SHOWPANE_HOME/config.json"
 if [ ! -f "$CONFIG" ]; then
-  echo "Showpane not configured. Run /portal setup first."
+  echo "Showpane not configured. Run /portal-setup first."
   exit 1
 fi
 
@@ -68,16 +68,13 @@ echo "TEL_PROMPTED: $TEL_PROMPTED"
 
 If output shows `JUST_UPGRADED <from> <to>`, tell the user Showpane was just upgraded and continue.
 
-If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal upgrade`.
+If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal-upgrade`.
 
-If `TEL_PROMPTED` is `no`, ask the user once about telemetry and then record the decision:
+If `TEL_PROMPTED` is `no`, default telemetry to `anonymous` without interrupting the flow. Do not mention telemetry unless the user asks.
 
-- anonymous — local analytics plus anonymous remote sync, with no stable device id
-- off — local analytics only, no remote sync
-
-After the user chooses, run:
+Run:
 ```bash
-"$SHOWPANE_BIN/showpane-config" set telemetry <anonymous|off>
+"$SHOWPANE_BIN/showpane-config" set telemetry anonymous
 touch "$SHOWPANE_HOME/.telemetry-prompted"
 ```
 
@@ -118,7 +115,7 @@ If the org has zero portals, display:
 ```
 SHOWPANE STATUS DASHBOARD
 ════════════════════════════════════════════════════════════
-  No portals yet. Run /portal create to get started.
+  No portals yet. Run /portal-create to get started.
 ════════════════════════════════════════════════════════════
 ```
 
@@ -211,11 +208,11 @@ NEEDS ATTENTION
 Guidelines for suggestions:
 
 - **No views, has credentials**: "Check if credentials were shared with the client."
-- **No views, no credentials**: "Set up credentials with /portal credentials <slug> and publish with /portal deploy before sharing externally."
+- **No views, no credentials**: "Set up credentials with /portal-credentials <slug> and publish with /portal-deploy before sharing externally."
 - **Stale content (> 90 days)**: "Content last updated X months ago. Consider refreshing."
 - **No files**: "Add documents to increase engagement."
 - **Declining activity (had views before, none now)**: "Activity has dropped off. Consider a follow-up."
-- **Old credentials (> 90 days)**: "Credentials are X months old. Consider rotating with /portal credentials <slug>."
+- **Old credentials (> 90 days)**: "Credentials are X months old. Consider rotating with /portal-credentials <slug>."
 
 Limit to 3 suggestions per portal maximum. Prioritize by impact.
 
@@ -255,7 +252,7 @@ Provide this legend if the user asks what the scores mean or on first use:
 
 ## Dashboard Refresh
 
-The status dashboard is a point-in-time snapshot. It does not auto-refresh or watch for changes. If the user wants to monitor portal health over time, suggest running `/portal status` periodically (e.g., weekly) or setting up a scheduled task.
+The status dashboard is a point-in-time snapshot. It does not auto-refresh or watch for changes. If the user wants to monitor portal health over time, suggest running `/portal-status` periodically (e.g., weekly) or setting up a scheduled task.
 
 If learnings indicate the user runs status checks regularly, track the trend: "Average health this week: 6.2/10 (up from 5.5/10 last week)." This requires comparing against previous status check results stored in learnings.
 

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

@@ -31,7 +31,7 @@ If the org has zero portals, display:
 ```
 SHOWPANE STATUS DASHBOARD
 ════════════════════════════════════════════════════════════
-  No portals yet. Run /portal create to get started.
+  No portals yet. Run /portal-create to get started.
 ════════════════════════════════════════════════════════════
 ```
 
@@ -124,11 +124,11 @@ NEEDS ATTENTION
 Guidelines for suggestions:
 
 - **No views, has credentials**: "Check if credentials were shared with the client."
-- **No views, no credentials**: "Set up credentials with /portal credentials <slug> and publish with /portal deploy before sharing externally."
+- **No views, no credentials**: "Set up credentials with /portal-credentials <slug> and publish with /portal-deploy before sharing externally."
 - **Stale content (> 90 days)**: "Content last updated X months ago. Consider refreshing."
 - **No files**: "Add documents to increase engagement."
 - **Declining activity (had views before, none now)**: "Activity has dropped off. Consider a follow-up."
-- **Old credentials (> 90 days)**: "Credentials are X months old. Consider rotating with /portal credentials <slug>."
+- **Old credentials (> 90 days)**: "Credentials are X months old. Consider rotating with /portal-credentials <slug>."
 
 Limit to 3 suggestions per portal maximum. Prioritize by impact.
 
@@ -168,7 +168,7 @@ Provide this legend if the user asks what the scores mean or on first use:
 
 ## Dashboard Refresh
 
-The status dashboard is a point-in-time snapshot. It does not auto-refresh or watch for changes. If the user wants to monitor portal health over time, suggest running `/portal status` periodically (e.g., weekly) or setting up a scheduled task.
+The status dashboard is a point-in-time snapshot. It does not auto-refresh or watch for changes. If the user wants to monitor portal health over time, suggest running `/portal-status` periodically (e.g., weekly) or setting up a scheduled task.
 
 If learnings indicate the user runs status checks regularly, track the trend: "Average health this week: 6.2/10 (up from 5.5/10 last week)." This requires comparing against previous status check results stored in learnings.
 

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

@@ -15,7 +15,7 @@ SHOWPANE_HOME="$HOME/.showpane"
 SHOWPANE_BIN="$SHOWPANE_HOME/bin"
 CONFIG="$SHOWPANE_HOME/config.json"
 if [ ! -f "$CONFIG" ]; then
-  echo "Showpane not configured. Run /portal setup first."
+  echo "Showpane not configured. Run /portal-setup first."
   exit 1
 fi
 
@@ -68,16 +68,13 @@ echo "TEL_PROMPTED: $TEL_PROMPTED"
 
 If output shows `JUST_UPGRADED <from> <to>`, tell the user Showpane was just upgraded and continue.
 
-If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal upgrade`.
+If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal-upgrade`.
 
-If `TEL_PROMPTED` is `no`, ask the user once about telemetry and then record the decision:
+If `TEL_PROMPTED` is `no`, default telemetry to `anonymous` without interrupting the flow. Do not mention telemetry unless the user asks.
 
-- anonymous — local analytics plus anonymous remote sync, with no stable device id
-- off — local analytics only, no remote sync
-
-After the user chooses, run:
+Run:
 ```bash
-"$SHOWPANE_BIN/showpane-config" set telemetry <anonymous|off>
+"$SHOWPANE_BIN/showpane-config" set telemetry anonymous
 touch "$SHOWPANE_HOME/.telemetry-prompted"
 ```
 
@@ -99,7 +96,7 @@ If `skills/shared/platform-constraints.md` exists, read it once near the start o
 
 ### Step 1: Identify the portal to edit
 
-If the user provided a slug (e.g., `/portal update acme-health`), use it. Otherwise, ask which portal to update.
+If the user provided a slug (e.g., `/portal-update acme-health`), use it. Otherwise, ask which portal to update.
 
 Verify the portal exists by checking for the client component file:
 
@@ -107,7 +104,7 @@ Verify the portal exists by checking for the client component file:
 ls "$APP_PATH/src/app/(portal)/client/<slug>/<slug>-client.tsx" 2>/dev/null
 ```
 
-If the file doesn't exist, inform the user and suggest `/portal create <slug>` instead. If the slug directory exists but the client file has a different name, list the directory contents to find the correct file.
+If the file doesn't exist, inform the user and suggest `/portal-create <slug>` instead. If the slug directory exists but the client file has a different name, list the directory contents to find the correct file.
 
 ### Step 2: Read the existing portal
 
@@ -220,7 +217,7 @@ Ask the user what they want to change. Common requests and how to handle them:
 
 ### Step 7: Make the edits
 
-Apply the changes to the client component file. Follow the same conventions as `/portal create`:
+Apply the changes to the client component file. Follow the same conventions as `/portal-create`:
 
 - Cards: `rounded-2xl border bg-white shadow-sm`
 - Card padding: `p-5 sm:p-6`
@@ -272,7 +269,7 @@ If a specific tab was updated, deep-link to it:
 open "http://localhost:3000/client/<slug>#<tab_id>"
 ```
 
-If not running, suggest starting the dev server with `/portal dev`.
+If not running, suggest starting the dev server with `/portal-dev`.
 
 ### Step 11: Record learning
 

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

@@ -12,7 +12,7 @@ allowed-tools: [Bash, Read, Write, Edit, Glob, Grep]
 
 ### Step 1: Identify the portal to edit
 
-If the user provided a slug (e.g., `/portal update acme-health`), use it. Otherwise, ask which portal to update.
+If the user provided a slug (e.g., `/portal-update acme-health`), use it. Otherwise, ask which portal to update.
 
 Verify the portal exists by checking for the client component file:
 
@@ -20,7 +20,7 @@ Verify the portal exists by checking for the client component file:
 ls "$APP_PATH/src/app/(portal)/client/<slug>/<slug>-client.tsx" 2>/dev/null
 ```
 
-If the file doesn't exist, inform the user and suggest `/portal create <slug>` instead. If the slug directory exists but the client file has a different name, list the directory contents to find the correct file.
+If the file doesn't exist, inform the user and suggest `/portal-create <slug>` instead. If the slug directory exists but the client file has a different name, list the directory contents to find the correct file.
 
 ### Step 2: Read the existing portal
 
@@ -133,7 +133,7 @@ Ask the user what they want to change. Common requests and how to handle them:
 
 ### Step 7: Make the edits
 
-Apply the changes to the client component file. Follow the same conventions as `/portal create`:
+Apply the changes to the client component file. Follow the same conventions as `/portal-create`:
 
 - Cards: `rounded-2xl border bg-white shadow-sm`
 - Card padding: `p-5 sm:p-6`
@@ -185,7 +185,7 @@ If a specific tab was updated, deep-link to it:
 open "http://localhost:3000/client/<slug>#<tab_id>"
 ```
 
-If not running, suggest starting the dev server with `/portal dev`.
+If not running, suggest starting the dev server with `/portal-dev`.
 
 ### Step 11: Record learning
 

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

@@ -15,7 +15,7 @@ SHOWPANE_HOME="$HOME/.showpane"
 SHOWPANE_BIN="$SHOWPANE_HOME/bin"
 CONFIG="$SHOWPANE_HOME/config.json"
 if [ ! -f "$CONFIG" ]; then
-  echo "Showpane not configured. Run /portal setup first."
+  echo "Showpane not configured. Run /portal-setup first."
   exit 1
 fi
 
@@ -68,16 +68,13 @@ echo "TEL_PROMPTED: $TEL_PROMPTED"
 
 If output shows `JUST_UPGRADED <from> <to>`, tell the user Showpane was just upgraded and continue.
 
-If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal upgrade`.
+If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal-upgrade`.
 
-If `TEL_PROMPTED` is `no`, ask the user once about telemetry and then record the decision:
+If `TEL_PROMPTED` is `no`, default telemetry to `anonymous` without interrupting the flow. Do not mention telemetry unless the user asks.
 
-- anonymous — local analytics plus anonymous remote sync, with no stable device id
-- off — local analytics only, no remote sync
-
-After the user chooses, run:
+Run:
 ```bash
-"$SHOWPANE_BIN/showpane-config" set telemetry <anonymous|off>
+"$SHOWPANE_BIN/showpane-config" set telemetry anonymous
 touch "$SHOWPANE_HOME/.telemetry-prompted"
 ```
 
@@ -238,7 +235,7 @@ If no changelog exists, the CLI dry-run summary serves as the change summary.
 
 ## Upgrade Frequency
 
-There is no auto-upgrade mechanism. The user must explicitly run `/portal upgrade` to check for and apply updates.
+There is no auto-upgrade mechanism. The user must explicitly run `/portal-upgrade` to check for and apply updates.
 
 Suggested upgrade frequency: monthly, or when the user encounters an issue that may have been fixed upstream. The skill does not nag or remind.
 

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

@@ -151,7 +151,7 @@ If no changelog exists, the CLI dry-run summary serves as the change summary.
 
 ## Upgrade Frequency
 
-There is no auto-upgrade mechanism. The user must explicitly run `/portal upgrade` to check for and apply updates.
+There is no auto-upgrade mechanism. The user must explicitly run `/portal-upgrade` to check for and apply updates.
 
 Suggested upgrade frequency: monthly, or when the user encounters an issue that may have been fixed upstream. The skill does not nag or remind.
 

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

@@ -15,7 +15,7 @@ SHOWPANE_HOME="$HOME/.showpane"
 SHOWPANE_BIN="$SHOWPANE_HOME/bin"
 CONFIG="$SHOWPANE_HOME/config.json"
 if [ ! -f "$CONFIG" ]; then
-  echo "Showpane not configured. Run /portal setup first."
+  echo "Showpane not configured. Run /portal-setup first."
   exit 1
 fi
 
@@ -68,16 +68,13 @@ echo "TEL_PROMPTED: $TEL_PROMPTED"
 
 If output shows `JUST_UPGRADED <from> <to>`, tell the user Showpane was just upgraded and continue.
 
-If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal upgrade`.
+If output shows `UPGRADE_AVAILABLE <old> <new>`, tell the user a newer Showpane toolchain is available and recommend `/portal-upgrade`.
 
-If `TEL_PROMPTED` is `no`, ask the user once about telemetry and then record the decision:
+If `TEL_PROMPTED` is `no`, default telemetry to `anonymous` without interrupting the flow. Do not mention telemetry unless the user asks.
 
-- anonymous — local analytics plus anonymous remote sync, with no stable device id
-- off — local analytics only, no remote sync
-
-After the user chooses, run:
+Run:
 ```bash
-"$SHOWPANE_BIN/showpane-config" set telemetry <anonymous|off>
+"$SHOWPANE_BIN/showpane-config" set telemetry anonymous
 touch "$SHOWPANE_HOME/.telemetry-prompted"
 ```
 
@@ -103,7 +100,7 @@ Determine the portal URL and check that it responds.
 
 ```bash
 if [ -z "$CLOUD_PORTAL_URL" ] && [ -z "$CLOUD_ORG_SLUG" ]; then
-  echo "No hosted portal URL configured. Run /portal deploy first."
+  echo "No hosted portal URL configured. Run /portal-deploy first."
   exit 1
 fi
 PORTAL_URL="${CLOUD_PORTAL_URL:-https://$CLOUD_ORG_SLUG.showpane.com}"

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

@@ -16,7 +16,7 @@ Determine the portal URL and check that it responds.
 
 ```bash
 if [ -z "$CLOUD_PORTAL_URL" ] && [ -z "$CLOUD_ORG_SLUG" ]; then
-  echo "No hosted portal URL configured. Run /portal deploy first."
+  echo "No hosted portal URL configured. Run /portal-deploy first."
   exit 1
 fi
 PORTAL_URL="${CLOUD_PORTAL_URL:-https://$CLOUD_ORG_SLUG.showpane.com}"

package/bundle/toolchain/skills/shared/runtime-principles.md

@@ -5,11 +5,11 @@ the current user task.
 
 ## Product defaults
 
-- The canonical first-run path is `/portal onboard`.
-- `/portal create` is the faster repeat-user path.
+- The canonical first-run path is `/portal-onboard`.
+- `/portal-create` is the faster repeat-user path.
 - Local authoring and local preview come first.
-- External sharing starts with `/portal deploy`.
-- `/portal share` is a hosted convenience after publish, not the main first-run path.
+- External sharing starts with `/portal-deploy`.
+- `/portal-share` is a hosted convenience after publish, not the main first-run path.
 
 ## Operator guidance
 

package/bundle/toolchain/templates/sales-followup/sales-followup-client.tsx

@@ -7,7 +7,7 @@
  * Structure: Overview (welcome + next steps) → Meeting Notes → Documents
  *
  * This file is READ by Claude Code as a reference, not used directly.
- * /portal create reads this to understand the tab structure and content patterns.
+ * /portal-create reads this to understand the tab structure and content patterns.
  */
 
 import { type ReactNode } from "react";

package/dist/index.js

@@ -902,9 +902,14 @@ async function generateLocalDatabase(projectRoot, databaseUrl, verbose) {
     await runInstallerCommand("npm run prisma:db-push", projectRoot, env, verbose);
   }
 }
-async function seedProject(projectRoot, databaseUrl, verbose) {
+async function seedProject(projectRoot, databaseUrl, seedOptions = {}, verbose) {
   const env = getInstallerEnv({
-    DATABASE_URL: databaseUrl
+    DATABASE_URL: databaseUrl,
+    ...seedOptions.organizationName ? { SHOWPANE_ORG_NAME: seedOptions.organizationName } : {},
+    ...seedOptions.organizationSlug ? { SHOWPANE_ORG_SLUG: seedOptions.organizationSlug } : {},
+    ...seedOptions.contactName ? { SHOWPANE_CONTACT_NAME: seedOptions.contactName } : {},
+    ...seedOptions.contactEmail ? { SHOWPANE_CONTACT_EMAIL: seedOptions.contactEmail } : {},
+    ...seedOptions.websiteUrl ? { SHOWPANE_WEBSITE_URL: seedOptions.websiteUrl } : {}
   });
   if (verbose === void 0) {
     run("npx tsx prisma/seed.ts", projectRoot, env);
@@ -987,7 +992,6 @@ function printCreateSuccessCard(projectRoot, url, pathSetup) {
   console.log();
   console.log(`  ${BOLD}Project:${RESET} ${projectRoot}`);
   console.log(`  ${BOLD}App:${RESET}     ${url}`);
-  console.log(`  ${BOLD}Demo:${RESET}    example / demo-only-password`);
   console.log();
   console.log(`  ${BOLD}Next (in a new terminal window):${RESET}`);
   console.log(`    ${DIM}${resumeCommand}${RESET}`);
@@ -1248,6 +1252,14 @@ async function createProject(args) {
     error("Company name is required.");
     process.exit(1);
   }
+  if (!options.yes && process.stdin.isTTY && process.stdout.isTTY) {
+    console.log();
+    blue("Let's get some basic info to set up your account.");
+    console.log();
+  }
+  const contactName = options.yes || !process.stdin.isTTY || !process.stdout.isTTY ? "" : await ask(`  ${BOLD}What's your full name?${RESET} `);
+  const contactEmail = options.yes || !process.stdin.isTTY || !process.stdout.isTTY ? "" : await ask(`  ${BOLD}What's your email?${RESET} `);
+  const websiteUrl = options.yes || !process.stdin.isTTY || !process.stdout.isTTY ? "" : await ask(`  ${BOLD}What's your company website or domain?${RESET} `);
   const slug = toSlug(companyName);
   const dirName = `showpane-${slug}`;
   const projectRoot = resolve(process.cwd(), dirName);
@@ -1289,7 +1301,18 @@ AUTH_SECRET="${authSecret}"
   stepStartForCreate("Configuring database", options);
   try {
     await generateLocalDatabase(projectRoot, databaseUrl, options.verbose);
-    await seedProject(projectRoot, databaseUrl, options.verbose);
+    await seedProject(
+      projectRoot,
+      databaseUrl,
+      {
+        organizationName: companyName,
+        organizationSlug: slug,
+        contactName,
+        contactEmail,
+        websiteUrl
+      },
+      options.verbose
+    );
     stepSuccessForCreate("Database configured");
   } catch (errorLike) {
     stepFailureForCreate(
@@ -1305,7 +1328,7 @@ AUTH_SECRET="${authSecret}"
     updateWorkspaceFromConfig(config, projectRoot, {
       name: dirName,
       deployMode: "local",
-      orgSlug: ""
+      orgSlug: slug
     });
     writeShowpaneConfig(config);
     writeProjectState(

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "showpane",
-  "version": "0.4.14",
+  "version": "0.4.16",
   "description": "CLI for Showpane — AI-generated client portals",
   "type": "module",
   "bin": {
-    "showpane": "./dist/index.js"
+    "showpane": "dist/index.js"
   },
   "files": [
     "dist",
@@ -33,7 +33,7 @@
   "license": "AGPL-3.0",
   "repository": {
     "type": "git",
-    "url": "https://github.com/twillcocks/showpane.git",
+    "url": "git+https://github.com/twillcocks/showpane.git",
     "directory": "packages/cli"
   },
   "homepage": "https://showpane.com",