showpane 0.4.14 → 0.4.15

package/bundle/meta/scaffold-manifest.json

@@ -1,18 +1,18 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-04-10T15:24:11.197Z",
-  "scaffoldVersion": "0.2.5",
+  "generatedAt": "2026-04-11T21:50:01.081Z",
+  "scaffoldVersion": "0.2.6",
   "files": {
     ".env.example": "ed105f2bdcd1888a98181d55e3c9f7d6eff3ae9c3e2366c2e777a12e3caddfa7",
     ".gitignore": "998e5f43865ea56ac79a05acfd5d4b0d696f310bd5325a1ed458c3d40154d437",
-    "VERSION": "e959f750e92dbb7614ae28ac96f0a37272caed81d8bbb758791af7bfbb6106a0",
+    "VERSION": "be3c6d2c6c406a64d44f0b6464a887e290416dd90c524094485b1be00936d6d7",
     "next.config.ts": "cf27999cc274cce79bc4c8df11789807719abf40752b60e4b4967a3d2f0ed013",
     "package-lock.json": "d8e30eb86f08e70787d4459a084b4ab2a9f119696bbd3146ec4ba5675fffd3c2",
     "package.json": "b095e17e7fc181c630e87fe9f473c5a4ef969afcd4b110f9f9c6d6a6d93f1c0b",
     "postcss.config.js": "fa650b380adfabb151a0b352f7135e107e6352345f899060f1c5c231228f94bf",
     "prisma.config.ts": "36f56fd74eae70632e484443e38d08665158d72d5c978dc456651d8d5e1a636e",
     "prisma/schema.local.prisma": "f5d6f3cb17d6d229f46ef82eef7c0ff4261596924f0173fef075ac394f423073",
-    "prisma/seed.ts": "398b645c31ea0d5b0291f27c32aded22bdb64021e581a547e85b3cccca65c551",
+    "prisma/seed.ts": "bb8eb3bc189fabbab3be83d3909afee583a5b724d258139feda22af504bed134",
     "public/example-avatar.svg": "0edeb0d3fbefa89cc27ffe6564d20e3ee0fd073cb6d9f2a025248ef3b3f277fd",
     "public/example-logo.svg": "bc5cd933aff2a17698dee66a7b4ea940ad12238e9d813474d643b459b1e8d6da",
     "public/robots.txt": "331ea9090db0c9f6f597bd9840fd5b171830f6e0b3ba1cb24dfa91f0c95aedc1",
@@ -24,10 +24,10 @@
     "src/__tests__/portal-contracts.test.ts": "9562b67f84f528ee0bb0bc4c0225adaf1dcc38c59b7629bda7c44e374a020eac",
     "src/app/(portal)/client/[slug]/page.tsx": "4f2f9253b2ad5d37a0f13759db52c786ae9c401f50fae9431da1417e9736e000",
     "src/app/(portal)/client/[slug]/s/[token]/route.ts": "a445e54b9139e40dfe0bc039e34e6af224a27f75a614741ab224d317ad4d3ec9",
-    "src/app/(portal)/client/example/example-client.tsx": "b9b744f0358b7773f319757157598fc69059eb38e0eaa1c09cb5fc10cfc3894b",
+    "src/app/(portal)/client/example/example-client.tsx": "ed32b111acea861f448d865338f8841d47c6ca7c2f87ed30d85bb0804940d4ec",
     "src/app/(portal)/client/example/page.tsx": "f330864f63c9feea76c8a62c3eba3ce57578627e0d4abd929fd7fefdfc7af058",
     "src/app/(portal)/client/layout.tsx": "4f43871510408a81da229d48ae316ec1d1c1beda93121922246300a2c8fd0999",
-    "src/app/(portal)/client/page.tsx": "af36f1a6f359d6a7bd4a6ac550058c9d9c107e9885bb238b4c06ec26700e23e3",
+    "src/app/(portal)/client/page.tsx": "7b4e3e5b286672f83581e24349e98ac930d8bbf5dfed02793754be2ddadf430f",
     "src/app/api/client-auth/route.ts": "ce1858559b1e944d5b1dc719d1f03bebf66286671700b1b5397382109f0f1e0d",
     "src/app/api/client-auth/share/route.ts": "ed82414212dcd26af8c6c0f2bd44d9d79a727ed35cfedbac8c4077a6220aad14",
     "src/app/api/client-events/route.ts": "13d545537b7e8ce421e6169d25c105adf2a2de3d978ae0a2c6751ff5f7d2eb33",
@@ -38,10 +38,10 @@
     "src/app/api/health/route.ts": "78fff55707372ce0cd6e9e49ef4f049622bc43cc42916d3f83e0162409d678b1",
     "src/app/globals.css": "28dcda76006d0e6af01b6dcf1a315dc5b5b6931c880fc53fd6565ff09d5dd13a",
     "src/app/layout.tsx": "c17aabeb2b486f023e777230343ace6cc06840f641a10b9dd9f65e092018f82f",
-    "src/app/page.tsx": "ef5a6cb28d4f364ca94306736e250da2d25a4076d9cf4bee621bacf03ec87f0b",
+    "src/app/page.tsx": "1f71205c3ae30bf6929d37947b0c94ae53aed33b6689b7d6b13066ad51c1bc14",
     "src/components/copy-button.tsx": "2f3d1d8a6a0a570c8d78e19c3c15519c44af17b5d8893ae5a5f57db5ecce7077",
     "src/components/portal-login.tsx": "8b0d91bb28674e1102fd2e5b5ddcc3a93755dd806fbd3d1b2dbea2646cffca5e",
-    "src/components/portal-shell.tsx": "6b90b1ca0bd8ba0762a03411e1103190085c7b138cf30362e412832e888f9d01",
+    "src/components/portal-shell.tsx": "f46a0f753a4a0318f06c8b4e46295febb84b03ea082c95057a6da50c737b4e21",
     "src/lib/abuse-controls.ts": "d79d58d93267aca48ad0b7b9b91f753c9a3c27263e4e98daf768a950c44a6fc6",
     "src/lib/branding.ts": "cc55f40e02bc3e486b227988f95739ca1cda8012c97b591295995eb4465efd57",
     "src/lib/client-auth.ts": "b9bdfe77dbe5d6ec6c6a930627fc43d3253f0d76fd8fc4093af5a75742bebe42",

package/bundle/scaffold/VERSION

@@ -1 +1 @@
-0.2.5
+0.2.6

package/bundle/scaffold/prisma/seed.ts

@@ -1,49 +1,54 @@
 import { PrismaClient } from "@/lib/prisma-client";
-import bcrypt from "bcryptjs";
 
 const prisma = new PrismaClient();
 
+function normalizeSlug(value: string): string {
+  return value
+    .toLowerCase()
+    .trim()
+    .replace(/[^a-z0-9\s-]/g, "")
+    .replace(/\s+/g, "-")
+    .replace(/-+/g, "-")
+    .replace(/^-|-$/g, "");
+}
+
+function normalizeWebsiteUrl(value: string | undefined): string | null {
+  if (!value) return null;
+  const trimmed = value.trim();
+  if (!trimmed) return null;
+  return trimmed.startsWith("http://") || trimmed.startsWith("https://")
+    ? trimmed
+    : `https://${trimmed}`;
+}
+
 async function main() {
-  const org = await prisma.organization.upsert({
-    where: { slug: "demo" },
-    update: {},
-    create: {
-      name: "Demo Company",
-      slug: "demo",
-      contactName: "Jane Smith",
-      contactTitle: "Account Manager",
-      contactEmail: "jane@example.com",
-      supportEmail: "support@example.com",
-      websiteUrl: "https://example.com",
-    },
-  });
+  const organizationName = process.env.SHOWPANE_ORG_NAME?.trim();
+  if (!organizationName) {
+    console.log("Seed skipped: no organization details provided");
+    return;
+  }
 
-  const passwordHash = await bcrypt.hash("demo-only-password", 10);
+  const organizationSlug =
+    process.env.SHOWPANE_ORG_SLUG?.trim() || normalizeSlug(organizationName);
+  const contactName = process.env.SHOWPANE_CONTACT_NAME?.trim() || null;
+  const contactEmail = process.env.SHOWPANE_CONTACT_EMAIL?.trim() || null;
+  const websiteUrl = normalizeWebsiteUrl(process.env.SHOWPANE_WEBSITE_URL);
 
-  await prisma.clientPortal.upsert({
-    where: {
-      organizationId_slug: {
-        organizationId: org.id,
-        slug: "example",
-      },
-    },
-    update: {
-      companyName: "Acme Health",
-      username: "example",
-      passwordHash,
-      lastUpdated: "2 April 2026",
-    },
+  const org = await prisma.organization.upsert({
+    where: { slug: organizationSlug },
+    update: {},
     create: {
-      organizationId: org.id,
-      slug: "example",
-      companyName: "Acme Health",
-      username: "example",
-      passwordHash,
-      lastUpdated: "2 April 2026",
+      name: organizationName,
+      slug: organizationSlug,
+      contactName,
+      contactTitle: null,
+      contactEmail,
+      supportEmail: contactEmail,
+      websiteUrl,
     },
   });
 
-  console.log("Seed complete: org 'demo', portal 'example' (username: example, password: demo-only-password)");
+  console.log(`Seed complete: org '${org.slug}'`);
 }
 
 main()

package/bundle/scaffold/src/app/(portal)/client/example/example-client.tsx

@@ -1,9 +1,8 @@
 "use client";
 
 /**
- * Reference portal — the /portal create skill reads this file as the quality
+ * Reference portal — the /portal-create skill reads this file as the quality
  * and style guide when generating new portals. Keep it polished.
- * Login: username "example", password "demo-only-password" (seeded by prisma/seed.ts)
  */
 
 import { type ReactNode } from "react";

package/bundle/scaffold/src/app/(portal)/client/page.tsx

@@ -5,14 +5,15 @@ import { PortalLogin } from "@/components/portal-login";
 export default function ClientLogin() {
   return (
     <PortalLogin
-      companyName="Demo Company"
+      companyName="Your Portal"
       companyLogo={
         <div className="flex h-7 w-7 items-center justify-center rounded-lg bg-gray-900">
-          <span className="text-xs font-bold text-white">D</span>
+          <span className="text-xs font-bold text-white">P</span>
         </div>
       }
-      companyUrl="https://example.com"
-      supportEmail="support@example.com"
+      companyUrl="https://showpane.com"
+      supportEmail="support@showpane.com"
+      description="Private portal access. Sign in with the credentials you were sent."
     />
   );
 }

package/bundle/scaffold/src/app/page.tsx

@@ -118,10 +118,10 @@ export default async function Home() {
                   Recommended
                 </p>
                 <p className="mt-3 font-mono text-sm leading-6 text-slate-700">
-                  /portal onboard
+                  /portal-onboard
                 </p>
               </div>
-              <CopyButton text="/portal onboard" />
+              <CopyButton text="/portal-onboard" />
             </div>
           </section>
 

package/bundle/scaffold/src/components/portal-shell.tsx

@@ -248,7 +248,7 @@ export function PortalShell({
               <span>
                 This portal is local only. Tell Claude{" "}
                 <code className="rounded bg-white px-1.5 py-0.5 font-mono text-[11px] text-amber-950 sm:text-xs">
-                  /portal deploy
+                  /portal-deploy
                 </code>{" "}
                 to publish it to Showpane Cloud.
               </span>

package/bundle/toolchain/CLI_VERSION

@@ -1 +1 @@
-0.4.14
+0.4.15

package/bundle/toolchain/VERSION

@@ -1 +1 @@
-1.1.5 (requires app >= 0.2.5)
+1.1.6 (requires app >= 0.2.6)

package/bundle/toolchain/skills/VERSION

@@ -1 +1 @@
-1.1.5 (requires app >= 0.2.5)
+1.1.6 (requires app >= 0.2.6)

package/bundle/toolchain/skills/portal-analytics/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"
 ```
 
@@ -147,7 +144,7 @@ For all portals, the response includes a `portals` array with the same fields pe
 
 If the script exits with a non-zero code, read stderr for the error JSON. Common errors:
 
-- `portal_not_found`: The slug does not exist in this organization. Suggest running `/portal list` to see available portals.
+- `portal_not_found`: The slug does not exist in this organization. Suggest running `/portal-list` to see available portals.
 - `no_analytics_data`: The portal exists but has zero recorded events. This is normal for brand-new portals.
 
 ### Step 3: Format the output as an ASCII table
@@ -251,7 +248,7 @@ A portal with zero views is not necessarily a problem. Context matters:
 - **New portal (created in last 7 days)**: Zero views is expected if the hosted portal has not been sent yet. Note: "Portal was created recently. Publish it first, then share hosted access with the client to start tracking engagement."
 - **Portal with credentials but no views**: The client may not have received the hosted portal yet, or the email landed in spam. Suggest: "Credentials exist but no one has logged in. Consider publishing first or resending the hosted portal details."
 - **Portal that previously had views but now has zero**: The client relationship may have gone cold. This is the most actionable signal -- suggest a follow-up.
-- **Portal with credentials and share link but no views**: The client may not have used the hosted link yet, or it may have been buried in email. Suggest resending the hosted link with `/portal share`.
+- **Portal with credentials and share link but no views**: The client may not have used the hosted link yet, or it may have been buried in email. Suggest resending the hosted link with `/portal-share`.
 
 ## Telemetry
 
@@ -265,8 +262,8 @@ If telemetry is enabled, the analytics skill records a minimal event after each
 
 - If the preamble fails (no config, no Prisma), stop and show the error. Do not attempt to query analytics.
 - If `query-analytics.ts` returns a non-zero exit code, display the error message from stderr and suggest a fix.
-- If DATABASE_URL is empty, tell the user: "No database configured. Run /portal setup to connect your database."
-- If the analytics query times out (large dataset), suggest narrowing the period: "Query took too long. Try a shorter period: /portal analytics whzan --period 7d"
+- If DATABASE_URL is empty, tell the user: "No database configured. Run /portal-setup to connect your database."
+- If the analytics query times out (large dataset), suggest narrowing the period: "Query took too long. Try a shorter period: /portal-analytics whzan --period 7d"
 
 ## Learnings Integration
 

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

@@ -60,7 +60,7 @@ For all portals, the response includes a `portals` array with the same fields pe
 
 If the script exits with a non-zero code, read stderr for the error JSON. Common errors:
 
-- `portal_not_found`: The slug does not exist in this organization. Suggest running `/portal list` to see available portals.
+- `portal_not_found`: The slug does not exist in this organization. Suggest running `/portal-list` to see available portals.
 - `no_analytics_data`: The portal exists but has zero recorded events. This is normal for brand-new portals.
 
 ### Step 3: Format the output as an ASCII table
@@ -164,7 +164,7 @@ A portal with zero views is not necessarily a problem. Context matters:
 - **New portal (created in last 7 days)**: Zero views is expected if the hosted portal has not been sent yet. Note: "Portal was created recently. Publish it first, then share hosted access with the client to start tracking engagement."
 - **Portal with credentials but no views**: The client may not have received the hosted portal yet, or the email landed in spam. Suggest: "Credentials exist but no one has logged in. Consider publishing first or resending the hosted portal details."
 - **Portal that previously had views but now has zero**: The client relationship may have gone cold. This is the most actionable signal -- suggest a follow-up.
-- **Portal with credentials and share link but no views**: The client may not have used the hosted link yet, or it may have been buried in email. Suggest resending the hosted link with `/portal share`.
+- **Portal with credentials and share link but no views**: The client may not have used the hosted link yet, or it may have been buried in email. Suggest resending the hosted link with `/portal-share`.
 
 ## Telemetry
 
@@ -178,8 +178,8 @@ If telemetry is enabled, the analytics skill records a minimal event after each
 
 - If the preamble fails (no config, no Prisma), stop and show the error. Do not attempt to query analytics.
 - If `query-analytics.ts` returns a non-zero exit code, display the error message from stderr and suggest a fix.
-- If DATABASE_URL is empty, tell the user: "No database configured. Run /portal setup to connect your database."
-- If the analytics query times out (large dataset), suggest narrowing the period: "Query took too long. Try a shorter period: /portal analytics whzan --period 7d"
+- If DATABASE_URL is empty, tell the user: "No database configured. Run /portal-setup to connect your database."
+- If the analytics query times out (large dataset), suggest narrowing the period: "Query took too long. Try a shorter period: /portal-analytics whzan --period 7d"
 
 ## Learnings Integration
 

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

@@ -20,7 +20,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
 
@@ -73,16 +73,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"
 ```
 
@@ -104,7 +101,7 @@ If `skills/shared/platform-constraints.md` exists, read it once near the start o
 
 ### Step 1: 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.
+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.
 
 Validate the slug by running:
 
@@ -145,7 +142,7 @@ Never fail or block because Granola is unavailable. It is purely additive.
 ### Step 3: Template selection
 
 Ask which template to use as a starting point. Keep this brief and practical —
-the user chose `/portal create` because they want the fast path, not a wizard.
+the user chose `/portal-create` because they want the fast path, not a wizard.
 
 1. **sales-followup** — Meeting notes, next steps, documents. Best after a sales call.
 2. **consulting** — Project overview, deliverables, timeline. Best for ongoing engagements.
@@ -286,7 +283,7 @@ Run the create-portal script to register the portal in the database:
 cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id <org_id>
 ```
 
-This creates the `ClientPortal` record with the slug, company name, and links it to the Organization. It does NOT create credentials — that is a separate step via `/portal credentials`.
+This creates the `ClientPortal` record with the slug, company name, and links it to the Organization. It does NOT create credentials — that is a separate step via `/portal-credentials`.
 
 ### Step 7: Self-review
 
@@ -319,7 +316,7 @@ open "http://localhost:3000/client/<slug>"
 
 If not running, suggest:
 
-> "Start the dev server with `/portal dev` to preview your portal at http://localhost:3000/client/<slug>"
+> "Start the dev server with `/portal-dev` to preview your portal at http://localhost:3000/client/<slug>"
 
 ### Step 9: Summary and next steps
 
@@ -334,10 +331,10 @@ Portal created: <slug>
              src/app/(portal)/client/<slug>/<slug>-client.tsx
 
 Next steps:
-  1. Create login credentials: /portal credentials <slug>
-  2. Preview the portal:       /portal preview <slug>
-  3. Edit content:             /portal update <slug>
-  4. Deploy:                   /portal deploy
+  1. Create login credentials: /portal-credentials <slug>
+  2. Preview the portal:       /portal-preview <slug>
+  3. Edit content:             /portal-update <slug>
+  4. Deploy:                   /portal-deploy
 ```
 
 ### Step 10: Record learning

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

@@ -17,7 +17,7 @@ capabilities, read `skills/shared/platform-constraints.md` and apply the relevan
 
 ### Step 1: 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.
+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.
 
 Validate the slug by running:
 
@@ -58,7 +58,7 @@ Never fail or block because Granola is unavailable. It is purely additive.
 ### Step 3: Template selection
 
 Ask which template to use as a starting point. Keep this brief and practical —
-the user chose `/portal create` because they want the fast path, not a wizard.
+the user chose `/portal-create` because they want the fast path, not a wizard.
 
 1. **sales-followup** — Meeting notes, next steps, documents. Best after a sales call.
 2. **consulting** — Project overview, deliverables, timeline. Best for ongoing engagements.
@@ -199,7 +199,7 @@ Run the create-portal script to register the portal in the database:
 cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/create-portal.ts" --slug <slug> --company "<client_company_name>" --org-id <org_id>
 ```
 
-This creates the `ClientPortal` record with the slug, company name, and links it to the Organization. It does NOT create credentials — that is a separate step via `/portal credentials`.
+This creates the `ClientPortal` record with the slug, company name, and links it to the Organization. It does NOT create credentials — that is a separate step via `/portal-credentials`.
 
 ### Step 7: Self-review
 
@@ -232,7 +232,7 @@ open "http://localhost:3000/client/<slug>"
 
 If not running, suggest:
 
-> "Start the dev server with `/portal dev` to preview your portal at http://localhost:3000/client/<slug>"
+> "Start the dev server with `/portal-dev` to preview your portal at http://localhost:3000/client/<slug>"
 
 ### Step 9: Summary and next steps
 
@@ -247,10 +247,10 @@ Portal created: <slug>
              src/app/(portal)/client/<slug>/<slug>-client.tsx
 
 Next steps:
-  1. Create login credentials: /portal credentials <slug>
-  2. Preview the portal:       /portal preview <slug>
-  3. Edit content:             /portal update <slug>
-  4. Deploy:                   /portal deploy
+  1. Create login credentials: /portal-credentials <slug>
+  2. Preview the portal:       /portal-preview <slug>
+  3. Edit content:             /portal-update <slug>
+  4. Deploy:                   /portal-deploy
 ```
 
 ### Step 10: Record learning

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

@@ -25,7 +25,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
 
@@ -78,16 +78,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"
 ```
 
@@ -109,7 +106,7 @@ If `skills/shared/platform-constraints.md` exists, read it once near the start o
 
 ### Step 1: Identify the portal
 
-If the user provided a slug (e.g., `/portal credentials acme-health`), use it. Otherwise, list available portals to help the user choose:
+If the user provided a slug (e.g., `/portal-credentials acme-health`), use it. Otherwise, list available portals to help the user choose:
 
 ```bash
 cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/list-portals.ts" --org-id <org_id>
@@ -117,9 +114,9 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 
 Present the list and ask which portal needs credentials. If there is only one portal, confirm it rather than asking.
 
-Verify the portal exists by checking the database. The `create-portal.ts` script should have been run during `/portal create` to register the portal. If no DB record exists, inform the user:
+Verify the portal exists by checking the database. The `create-portal.ts` script should have been run during `/portal-create` to register the portal. If no DB record exists, inform the user:
 
-> "No portal record found for '<slug>'. Run `/portal create <slug>` first to register it."
+> "No portal record found for '<slug>'. Run `/portal-create <slug>` first to register it."
 
 Also check the portal's current credential status from the list output. If credentials already exist, inform the user before proceeding:
 
@@ -156,7 +153,7 @@ The script returns JSON on stdout:
 
 If the script returns an error, handle it based on the error type:
 
-- `portal_not_found` — The portal slug doesn't exist in the database for this org. Suggest running `/portal create <slug>` first.
+- `portal_not_found` — The portal slug doesn't exist in the database for this org. Suggest running `/portal-create <slug>` first.
 - `database_error` — Connection or query failure. Check DATABASE_URL and re-apply the local schema with `cd $APP_PATH && npm run prisma:db-push`.
 - `auth_secret_missing` — The AUTH_SECRET environment variable is not set in `$APP_PATH/.env`. The rotate-credentials script needs this to function. Suggest adding `AUTH_SECRET=<random-string>` to the .env file.
 
@@ -183,7 +180,7 @@ The ASCII box ensures the credentials stand out clearly in terminal output. Do n
 
 Immediately after displaying credentials, show this warning:
 
-> **Save these credentials now.** They will not be shown again. The password is hashed in the database and cannot be retrieved. If lost, run `/portal credentials <slug>` again to rotate to a new password.
+> **Save these credentials now.** They will not be shown again. The password is hashed in the database and cannot be retrieved. If lost, run `/portal-credentials <slug>` again to rotate to a new password.
 
 If this was a rotation (`"rotated": true`), add:
 
@@ -196,8 +193,8 @@ Provide guidance on how to share the credentials with the client:
 > **How to share with your client:**
 > - Send the username and password via a secure channel (encrypted email, Signal, etc.)
 > - The login page is at `/client` — the client enters the portal slug as the "company" field, then the username and password
-> - For external access, publish the portal first with `/portal deploy`
-> - After publish, you can use `/portal share <slug>` if you want a direct hosted link instead of asking the client to log in
+> - For external access, publish the portal first with `/portal-deploy`
+> - After publish, you can use `/portal-share <slug>` if you want a direct hosted link instead of asking the client to log in
 
 Recommend against sharing credentials via:
 - Unencrypted email (can be intercepted)
@@ -236,8 +233,8 @@ Credentials created for: acme-health
 
 Next steps:
   1. Send credentials to the client via a secure channel
-  2. Deploy if not already live: /portal deploy
-  3. Optional hosted direct link after publish: /portal share <slug>
+  2. Deploy if not already live: /portal-deploy
+  3. Optional hosted direct link after publish: /portal-share <slug>
 ```
 
 ### Step 9: Record credential event
@@ -259,7 +256,7 @@ echo '{"skill":"portal-credentials","key":"credentials-created","insight":"Creat
 
 ## Error Handling
 
-- **Script not found**: If `$SKILL_DIR/bin/rotate-credentials.ts` does not exist, the skill pack may not be fully installed. Suggest running `/portal upgrade` or checking the Showpane installation.
+- **Script not found**: If `$SKILL_DIR/bin/rotate-credentials.ts` does not exist, the skill pack may not be fully installed. Suggest running `/portal-upgrade` or checking the Showpane installation.
 - **Prisma connection error**: DATABASE_URL may be wrong or the database may be down. Check the .env file and database status.
 - **Permission denied on .env**: The preamble sources `$APP_PATH/.env`. If this file is not readable, the DATABASE_URL will not be set. Check file permissions.
 - **Script timeout**: If the script takes more than 30 seconds, something is wrong. The most common cause is a database connection timeout — check network connectivity to the database host.

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

@@ -22,7 +22,7 @@ hooks:
 
 ### Step 1: Identify the portal
 
-If the user provided a slug (e.g., `/portal credentials acme-health`), use it. Otherwise, list available portals to help the user choose:
+If the user provided a slug (e.g., `/portal-credentials acme-health`), use it. Otherwise, list available portals to help the user choose:
 
 ```bash
 cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PATH/tsconfig.json" "$SKILL_DIR/bin/list-portals.ts" --org-id <org_id>
@@ -30,9 +30,9 @@ cd "$APP_PATH" && NODE_PATH="$APP_PATH/node_modules" npx tsx --tsconfig "$APP_PA
 
 Present the list and ask which portal needs credentials. If there is only one portal, confirm it rather than asking.
 
-Verify the portal exists by checking the database. The `create-portal.ts` script should have been run during `/portal create` to register the portal. If no DB record exists, inform the user:
+Verify the portal exists by checking the database. The `create-portal.ts` script should have been run during `/portal-create` to register the portal. If no DB record exists, inform the user:
 
-> "No portal record found for '<slug>'. Run `/portal create <slug>` first to register it."
+> "No portal record found for '<slug>'. Run `/portal-create <slug>` first to register it."
 
 Also check the portal's current credential status from the list output. If credentials already exist, inform the user before proceeding:
 
@@ -69,7 +69,7 @@ The script returns JSON on stdout:
 
 If the script returns an error, handle it based on the error type:
 
-- `portal_not_found` — The portal slug doesn't exist in the database for this org. Suggest running `/portal create <slug>` first.
+- `portal_not_found` — The portal slug doesn't exist in the database for this org. Suggest running `/portal-create <slug>` first.
 - `database_error` — Connection or query failure. Check DATABASE_URL and re-apply the local schema with `cd $APP_PATH && npm run prisma:db-push`.
 - `auth_secret_missing` — The AUTH_SECRET environment variable is not set in `$APP_PATH/.env`. The rotate-credentials script needs this to function. Suggest adding `AUTH_SECRET=<random-string>` to the .env file.
 
@@ -96,7 +96,7 @@ The ASCII box ensures the credentials stand out clearly in terminal output. Do n
 
 Immediately after displaying credentials, show this warning:
 
-> **Save these credentials now.** They will not be shown again. The password is hashed in the database and cannot be retrieved. If lost, run `/portal credentials <slug>` again to rotate to a new password.
+> **Save these credentials now.** They will not be shown again. The password is hashed in the database and cannot be retrieved. If lost, run `/portal-credentials <slug>` again to rotate to a new password.
 
 If this was a rotation (`"rotated": true`), add:
 
@@ -109,8 +109,8 @@ Provide guidance on how to share the credentials with the client:
 > **How to share with your client:**
 > - Send the username and password via a secure channel (encrypted email, Signal, etc.)
 > - The login page is at `/client` — the client enters the portal slug as the "company" field, then the username and password
-> - For external access, publish the portal first with `/portal deploy`
-> - After publish, you can use `/portal share <slug>` if you want a direct hosted link instead of asking the client to log in
+> - For external access, publish the portal first with `/portal-deploy`
+> - After publish, you can use `/portal-share <slug>` if you want a direct hosted link instead of asking the client to log in
 
 Recommend against sharing credentials via:
 - Unencrypted email (can be intercepted)
@@ -149,8 +149,8 @@ Credentials created for: acme-health
 
 Next steps:
   1. Send credentials to the client via a secure channel
-  2. Deploy if not already live: /portal deploy
-  3. Optional hosted direct link after publish: /portal share <slug>
+  2. Deploy if not already live: /portal-deploy
+  3. Optional hosted direct link after publish: /portal-share <slug>
 ```
 
 ### Step 9: Record credential event
@@ -172,7 +172,7 @@ echo '{"skill":"portal-credentials","key":"credentials-created","insight":"Creat
 
 ## Error Handling
 
-- **Script not found**: If `$SKILL_DIR/bin/rotate-credentials.ts` does not exist, the skill pack may not be fully installed. Suggest running `/portal upgrade` or checking the Showpane installation.
+- **Script not found**: If `$SKILL_DIR/bin/rotate-credentials.ts` does not exist, the skill pack may not be fully installed. Suggest running `/portal-upgrade` or checking the Showpane installation.
 - **Prisma connection error**: DATABASE_URL may be wrong or the database may be down. Check the .env file and database status.
 - **Permission denied on .env**: The preamble sources `$APP_PATH/.env`. If this file is not readable, the DATABASE_URL will not be set. Check file permissions.
 - **Script timeout**: If the script takes more than 30 seconds, something is wrong. The most common cause is a database connection timeout — check network connectivity to the database host.