protovibe 1.0.0 → 1.0.3

package/dist/index.mjs

@@ -69,7 +69,7 @@ import { Box as Box2, Text as Text3 } from "ink";
 var WIDTH = 42;
 function InfoBox() {
   const separator = "\u2500".repeat(WIDTH);
-  return /* @__PURE__ */ React3.createElement(Box2, { flexDirection: "column" }, /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u256D" + "\u2500".repeat(WIDTH) + "\u256E"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "  version  "), /* @__PURE__ */ React3.createElement(Text3, { color: "#ffffff" }, "1.0.0"), " ".repeat(WIDTH - 17), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "  by  "), /* @__PURE__ */ React3.createElement(Text3, { color: "#ffffff" }, "razorgojo"), " ".repeat(WIDTH - 15), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502  ", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "powered by  "), /* @__PURE__ */ React3.createElement(Gradient, { text: "Claude Code", fromHex: "#7B2FBE", toHex: "#3B82F6" }), " ".repeat(WIDTH - 25), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u251C" + separator + "\u2524"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#6d5a8a", italic: true }, "  Vibecode your prototypes."), " ".repeat(WIDTH - 28), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2570" + "\u2500".repeat(WIDTH) + "\u256F"));
+  return /* @__PURE__ */ React3.createElement(Box2, { flexDirection: "column" }, /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u256D" + "\u2500".repeat(WIDTH) + "\u256E"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "  version  "), /* @__PURE__ */ React3.createElement(Text3, { color: "#ffffff" }, "1.0.0"), " ".repeat(WIDTH - 17), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "  by  "), /* @__PURE__ */ React3.createElement(Text3, { color: "#ffffff" }, "razorgojo"), " ".repeat(WIDTH - 15), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502  ", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "powered by  "), /* @__PURE__ */ React3.createElement(Gradient, { text: "Claude Code", fromHex: "#7B2FBE", toHex: "#3B82F6" }), " ".repeat(WIDTH - 25), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u251C" + separator + "\u2524"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#6d5a8a", italic: true }, "  Vibecode your prototypes."), " ".repeat(WIDTH - 28), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u251C" + separator + "\u2524"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#b39ddb" }, "  commands"), " ".repeat(WIDTH - 11), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2502", /* @__PURE__ */ React3.createElement(Text3, { color: "#ffffff" }, "  /exit"), /* @__PURE__ */ React3.createElement(Text3, { color: "#6d5a8a" }, "  \u2014  quit ProtoVibe at any time"), " ".repeat(WIDTH - 37), "\u2502"), /* @__PURE__ */ React3.createElement(Text3, { color: "#3a1a6a" }, "\u2570" + "\u2500".repeat(WIDTH) + "\u256F"));
 }
 
 // src/auth.ts
@@ -128,8 +128,11 @@ import * as clack from "@clack/prompts";
 // src/templates/CLAUDE.md.ts
 var CLAUDE_MD = `# CLAUDE.md
 
-When you start, your first and only task is to run /protovibe.
-Do not wait for user input. Do not do anything else first.
+IMMEDIATE INSTRUCTION \u2014 execute this before doing anything else, before reading any other file, before responding to the user in any way:
+
+Run /protovibe now.
+
+Do not greet the user. Do not ask what they want. Do not wait for input. Do not explain what you are about to do. Just run /protovibe immediately and silently.
 
 At any point during the workflow, the user can type /takeover to exit ProtoVibe and work directly in Claude Code with full context preserved.
 `;
@@ -143,7 +146,16 @@ You are running the ProtoVibe automated project setup workflow. Follow these sta
 
 ## Stage 0 \u2014 Mode Selection
 
-Present the user with two options:
+Present the following immediately. Do not wait for any prior input:
+
+First, show the available commands:
+
+> **Available commands** (use these at any time during your session):
+> - \`/summarise\` \u2014 get a plain-language summary of what's been done so far
+> - \`/takeover\` \u2014 exit the ProtoVibe workflow and work directly in Claude Code
+> - \`/protovibe\` \u2014 restart the ProtoVibe workflow from the beginning
+
+Then immediately ask:
 
 > "Welcome to ProtoVibe. What would you like to do?"
 > 1. **Build from scratch** \u2014 start a new project
@@ -197,31 +209,41 @@ Wait for a free-text response. Accept anything. Do not proceed until you have an
 
 ## Stage 2 \u2014 Deep Requirements Probing
 
-Ask follow-up questions **one at a time**. Each question must be directly informed by all previous answers. Never ask about something already covered.
+Your goal is to achieve complete, end-to-end clarity on this product before moving on. You must fully understand the user flow, product requirements, and all edge cases \u2014 with zero ambiguity.
 
-You must reach complete, unambiguous clarity on all of the following before moving on:
-- **Who** are the target users? (be specific \u2014 not just "everyone")
-- **What** does each core feature actually do? (behavior, not just names)
-- **Platform** \u2014 web, mobile, desktop, CLI, or multiple?
-- **Auth** \u2014 is user login required? If yes, what type?
-- **Data** \u2014 what data is created, stored, read? Any real-time requirements?
-- **Integrations** \u2014 any third-party services, APIs, or existing systems?
-- **Constraints** \u2014 performance, offline support, team size, timeline, existing tech choices?
+**How to probe:**
 
-**There is no question limit.** Keep probing until you have zero unanswered questions. Do not summarize until everything is fully clear.
+Ask your questions in **grouped batches** \u2014 not one at a time. Group related questions together so the user can answer them in one response. After receiving answers, analyse them carefully. If anything is still unclear, incomplete, or raises new questions, ask a follow-up batch. Repeat until you have full clarity.
 
-When you are confident nothing is ambiguous, present a complete structured summary:
+You must cover all of the following \u2014 do not move on until every point is resolved:
+
+- **Who** are the target users? (be specific \u2014 demographics, roles, technical level)
+- **What** does each core feature actually do? (exact behavior, not just feature names)
+- **User Flow** \u2014 how does a user move through the product from first open to completing each core action? Walk through every key path.
+- **Platform** \u2014 web, mobile, desktop, CLI, or multiple? Any specific device or OS constraints?
+- **Auth** \u2014 is login required? What type? (email, social, SSO?) Any roles or permission levels?
+- **Data** \u2014 what data is created, stored, read, or deleted? Any real-time or sync requirements?
+- **Integrations** \u2014 any third-party services, APIs, payment systems, or external tools?
+- **Constraints** \u2014 performance targets, offline support, accessibility needs, team size, timeline, existing tech choices the user wants to keep?
+- **Edge cases** \u2014 what happens when things go wrong? Any critical failure states to handle?
+
+**There is no question limit.** If the user's answers raise new questions, ask them. Keep going until you have the full picture.
+
+When you are confident everything is fully clear, present a complete structured summary:
 
 ---
 **Project:** [name]
-**Users:** [specific description]
+**Type:** [web app / mobile app / desktop app / CLI tool / etc.]
+**Target Users:** [specific description]
+**Summary:** [2\u20133 sentences describing what the app does and the problem it solves]
 **Core Features:**
-[bulleted list \u2014 each with a one-line description of its behavior]
-**Platform:** [web / mobile / desktop / CLI]
-**Auth:** [yes/no and type]
-**Data & Storage:** [summary]
-**Integrations:** [summary]
-**Constraints:** [summary]
+[bulleted list \u2014 each feature with a precise one-line description of its behavior]
+**User Flow:** [step-by-step walkthrough of the primary user journey]
+**Platform:** [web / mobile / desktop / CLI \u2014 with any specific constraints]
+**Auth:** [yes/no, type, roles if any]
+**Data & Storage:** [what data exists, how it's stored, any real-time needs]
+**Integrations:** [third-party services and how they connect]
+**Constraints & Requirements:** [all hard constraints, performance targets, non-negotiables]
 ---
 
 Then ask: "Does this capture everything? Confirm to continue."
@@ -269,13 +291,21 @@ Ask the user:
 
 Wait for confirmation. Do not create the file without it.
 
-On confirmation, write **specs.md** in the current working directory. It must contain:
-- **Tech Stack** \u2014 chosen stack with a one-line justification for each major choice
-- **User Flow** \u2014 step-by-step description of how a user moves through the app from first open to completing a core action
-- **Feature List** \u2014 all features with priority labels (P0 = must have for MVP, P1 = important but not blocking, P2 = nice to have)
-- **Data Model** \u2014 key entities, their fields, and relationships
-- **Integration Notes** \u2014 any third-party services and how they connect
-- **Constraints & NFRs** \u2014 performance targets, platform requirements, any hard constraints
+On confirmation, write **specs.md** in the current working directory. It must be detailed but concise \u2014 every section should give enough information to build from, without padding. Include the following:
+
+- **App Overview** \u2014 what the app is, what problem it solves, and what type of app it is (web, mobile, CLI, etc.)
+- **Target Audience** \u2014 who the users are, their roles, technical level, and any relevant context
+- **Summary** \u2014 a short paragraph (3\u20135 sentences) describing what the app does end-to-end
+- **App Features** \u2014 full list of features with priority labels:
+  - P0 = must have for MVP
+  - P1 = important but not blocking launch
+  - P2 = nice to have / future iteration
+  Each feature should include a one-line description of its exact behavior.
+- **Complete User Flow** \u2014 step-by-step walkthrough of every key user journey, from first open through all core actions. Cover the primary flow and any critical alternate paths.
+- **Tech Stack** \u2014 chosen stack with a one-line justification for each major technology choice
+- **Data Model** \u2014 key entities, their fields, types, and relationships
+- **Integration Notes** \u2014 any third-party services, APIs, or external tools and how they connect
+- **Additional Requirements** \u2014 any extra constraints, performance targets, accessibility needs, non-functional requirements, or specific details the user provided that don't fit above
 
 After writing, tell the user:
 
@@ -290,6 +320,8 @@ Without asking the user, do the following in order:
 1. Delete the existing CLAUDE.md file in the current directory
 2. Run /init \u2014 this will analyze the project (including specs.md) and generate a new, project-aware CLAUDE.md
 
+The generated CLAUDE.md must contain full, detailed context to help Claude with all future development on this project. /init should produce a CLAUDE.md that includes: the project purpose and scope, the full tech stack with reasoning, the architecture overview, key entities and data relationships, the complete feature set, user flow summary, coding conventions and patterns to follow, known constraints, and any integration details. It should be a complete reference document \u2014 not a summary.
+
 After /init completes, confirm:
 
 > "CLAUDE.md \u2713 \u2014 your project is initialized."
@@ -302,9 +334,13 @@ Do not mention the deletion to the user. Do not ask permission. Just do it silen
 
 Tell the user:
 
-> "You can now go for building out the code."
+> "Your project is fully scoped and ready to build."
+>
+> "Type **Build it** to start building, or ask me anything about the project first."
 
-Stop all automation. From this point forward, respond only to direct user requests. The ProtoVibe workflow is complete.
+Wait for the user to type "Build it" (or a clear equivalent). Do not start writing any code until they do.
+
+Once they confirm, begin building the project according to the specs.md and CLAUDE.md. Work systematically through the P0 features first.
 
 ---
 
@@ -336,6 +372,28 @@ When this command is run:
 4. From this point forward, respond normally to all user requests. No more workflow stages. No more automation. Just Claude Code.
 `;
 
+// src/templates/summarise.md.ts
+var SUMMARISE_MD = `# /summarise \u2014 Session Summary
+
+When this command is run, provide a concise summary in simple, plain language of everything that has happened in the current session.
+
+Structure your summary like this:
+
+**What we're building:** [one sentence describing the project]
+**What's been decided so far:**
+[bullet list \u2014 each decision made, e.g. tech stack chosen, features confirmed, architecture selected]
+**What's been done:**
+[bullet list \u2014 any files created, code written, or stages completed]
+**What comes next:**
+[bullet list \u2014 the immediate next steps]
+
+Rules:
+- Keep it short \u2014 no more than 10 bullet points total across all sections
+- Use plain words. No jargon. Write as if explaining to someone who hasn't been in the conversation.
+- If nothing has happened yet, say: "Nothing has been decided yet. We're just getting started."
+- After giving the summary, ask: "Would you like to continue where we left off?"
+`;
+
 // src/scaffold.ts
 function getSubdirectories(dirPath) {
   try {
@@ -357,6 +415,7 @@ async function browseForDirectory() {
     const subdirs = getSubdirectories(currentPath);
     const isRoot = dirname(currentPath) === currentPath;
     const options = [
+      { value: "__exit__", label: "\u238B  Exit ProtoVibe" },
       { value: "__select__", label: `\u2713  Use this folder \u2014 ${currentPath}` },
       ...!isRoot ? [{ value: "__up__", label: "\u2191  Go up" }] : [],
       ...subdirs.map((dir) => ({ value: join2(currentPath, dir), label: `\u{1F4C1}  ${dir}` }))
@@ -369,7 +428,10 @@ async function browseForDirectory() {
       clack.cancel("Cancelled.");
       process.exit(0);
     }
-    if (choice === "__select__") {
+    if (choice === "__exit__") {
+      clack.cancel("Exiting ProtoVibe. See you next time.");
+      process.exit(0);
+    } else if (choice === "__select__") {
       return currentPath;
     } else if (choice === "__up__") {
       currentPath = dirname(currentPath);
@@ -379,16 +441,17 @@ async function browseForDirectory() {
   }
 }
 async function scaffoldProject() {
-  clack.intro("");
   const projectName = await clack.text({
     message: "Project name:",
+    placeholder: "my-project",
     validate(value) {
+      if (value.trim() === "/exit") return void 0;
       if (!value.trim()) return "Project name is required.";
       if (/[^a-zA-Z0-9\-_]/.test(value)) return "Use only letters, numbers, hyphens, and underscores.";
     }
   });
-  if (clack.isCancel(projectName)) {
-    clack.cancel("Cancelled.");
+  if (clack.isCancel(projectName) || String(projectName).trim() === "/exit") {
+    clack.cancel("Exiting ProtoVibe. See you next time.");
     process.exit(0);
   }
   clack.log.info("Select where to create your project:");
@@ -402,6 +465,7 @@ async function scaffoldProject() {
   writeFileSync(join2(targetDir, "CLAUDE.md"), CLAUDE_MD, "utf-8");
   writeFileSync(join2(targetDir, ".claude", "commands", "protovibe.md"), PROTOVIBE_MD, "utf-8");
   writeFileSync(join2(targetDir, ".claude", "commands", "takeover.md"), TAKEOVER_MD, "utf-8");
+  writeFileSync(join2(targetDir, ".claude", "commands", "summarise.md"), SUMMARISE_MD, "utf-8");
   clack.outro(`\u2713 Project created at ${targetDir}`);
   return targetDir;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "protovibe",
-  "version": "1.0.0",
+  "version": "1.0.3",
   "description": "A branded CLI platform layer on top of Claude Code",
   "author": "razorgojo",
   "license": "MIT",