ship-create 1.6.5 → 1.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ship-create",
-  "version": "1.6.5",
+  "version": "1.7.1",
   "description": "Scaffold a new project the SHIP Method way — Structure, Human Flow, Instruction, Publish. No git clone, no API key, just one command.",
   "type": "module",
   "license": "MIT",

package/templates/.claude/skills/ship-method/SKILL.md

@@ -9,32 +9,79 @@ description: Use when starting any new product, feature, or "build me an app" re
 S — STRUCTURE  →  H — HUMAN FLOW  →  I — INSTRUCTION  →  P — PUBLISH
 ```
 
-## When `/build` is invoked — do this immediately, in this order
+## Phase 1 — Build (runs automatically on first open, no prompts)
 
-**Do not create a task list. Do not plan. Act.**
+**Do not ask anything. Do not show a menu. Just build.**
 
-### 1. Read (no output, no tasks)
-Silently read `docs/PROJECT.md` and `docs/HUMAN_FLOW.md`. Check **Section 9 Technical Decisions** for `UI language` — if Thai (ภาษาไทย), switch to Thai for all output from this point forward. The idea is already in Section 10 (Original Idea) and Section 1 (Product Vision) — do not ask the user to describe it again. Proceed directly to Step 2.
+### Step 1 — Read & decide (silent, no output)
+Read `docs/PROJECT.md` and `docs/HUMAN_FLOW.md`. Extract:
+- Product type, idea, target user, problem, value prop (already filled by `ship-create`)
+- UI language from Section 9 — switch language now, use it for everything after this
+- Auto-select the best theme from `theme-guide.md` for this product type — do not ask, just pick
 
-### 2. Theme — first visible output
-Present 2–3 theme options (palette name + font, one line each). Wait for the user to pick. Apply the chosen theme to `app/globals.css` and `app/layout.tsx`. Record in `docs/DESIGN_SYSTEM.md`. **This is the first thing the user sees — it must happen before any feature code.**
+### Step 2 — Build docs + flow diagram
+Write `docs/AI_BUILD_SPEC.md` immediately — functional requirements for the 2–3 core MVP features + data model. Keep it tight, 1 page max.
 
-### 3. Home screen — second visible output
-Read `HUMAN_FLOW.md`. Replace `app/page.tsx` with the real entry point for this product. The user should be able to run `npm run dev` and see their product, not the starter template.
+Then generate `docs/FLOW.md` — a Mermaid flowchart of the full user journey from `HUMAN_FLOW.md`. Include every screen, decision point, happy path, and key error/empty states. Format:
 
-### 4. Ask one question
-*"Which feature do you want to build first?"* Then build just that one.
+```markdown
+# User Flow
+
+> แก้ได้โดยตรงในไฟล์นี้ — เปิด Preview ใน VS Code (Cmd+Shift+P → "Mermaid Preview") หรือวางใน https://mermaid.live
+
+```mermaid
+flowchart TD
+    ...
+```
+```
+
+Rules for the diagram:
+- Use `([text])` for entry/exit points (stadium shape)
+- Use `[text]` for screens/pages
+- Use `{text}` for decision points
+- Use `-->|label|` for conditional paths
+- Show the happy path left-to-right or top-to-bottom
+- Keep node labels short (3–5 words max)
+
+### Step 3 — Build prototype
+Apply the chosen theme to `app/globals.css` and `app/layout.tsx`. Replace `app/page.tsx` with the real home screen based on `HUMAN_FLOW.md`. Build the first 1–2 screens that matter most for this product type. Record the theme choice in `docs/DESIGN_SYSTEM.md`.
+
+### Step 4 — Run
+Run `npm run dev` (or `pnpm dev` if pnpm is available). Confirm the app compiles and is accessible at localhost:3000.
+
+### Step 5 — Show & ask one question
+Tell the user (in the correct language):
+- What was built and why (2–3 sentences max)
+- Which theme was chosen and why (1 sentence)
+- Where to see the flow diagram: `docs/FLOW.md` (เปิด Preview ใน VS Code หรือ https://mermaid.live)
+- "เปิด localhost:3000 ดูได้เลย — ชอบทิศทางนี้ไหม?" (Thai) or "Open localhost:3000 — does this feel right?" (English)
+
+**That's Phase 1. Wait for the user's answer before doing anything else.**
 
 ---
 
-**That's the entire flow.** Steps 1–3 are one session. Features are added one at a time after that.
+## Phase 2 — Review (after user responds)
+
+**If the user likes it:**
+Enter ship review mode — ask which feature to build next, then build one at a time. After each feature, ask again. Track progress in `docs/AI_BUILD_SPEC.md`.
+
+**If the user wants changes:**
+Ask one focused question: "What feels off?" Make the adjustment, re-run, show again. Do not rebuild everything — change only what they point to.
+
+**When the product feels complete to the user:**
+Run through `docs/QA_CHECKLIST.md` silently. Report only what's missing or broken, not what passes. Then guide them to `/ship` for launch prep.
+
+---
 
 ## Hard rules
 
-- **No task list at start.** Create tasks only when building a specific feature, and only 1–2 at a time.
-- **No spec before theme.** `docs/AI_BUILD_SPEC.md` is written after the home screen exists, not before.
-- **No gates that block visible output.** The only thing that can pause the flow is a missing answer to a direct question.
-- **If the user says "skip docs":** comply. Say once what's skipped. Never repeat.
+- **No task list, ever.** Build directly — tasks are invisible internal steps, not output.
+- **No questions before the prototype exists.** The only interaction before Step 5 is code being written.
+- **Theme is chosen by the agent, not the user** — pick the best fit from `theme-guide.md` and explain briefly after.
+- **Run the app before showing results.** Never say "done" without confirming it compiles.
+- **One question at a time.** Never give a list of options or ask multiple things at once.
+
+---
 
 ## Reference files
 
@@ -42,7 +89,9 @@ Read `HUMAN_FLOW.md`. Replace `app/page.tsx` with the real entry point for this
 |---|---|
 | Vision, audience, MVP | `docs/PROJECT.md` |
 | User flow, screens | `docs/HUMAN_FLOW.md` |
-| Functional spec | `docs/AI_BUILD_SPEC.md` (written after home screen) |
+| Visual flow diagram (Mermaid) | `docs/FLOW.md` |
+| Functional spec | `docs/AI_BUILD_SPEC.md` |
 | Stack choices | `docs/tech-stack/STACK_DECISION_MATRIX.md` |
 | UI guidance | invoke `ui-ux-pro-max` skill |
 | Theme palette table | `theme-guide.md` (this skill folder) |
+| QA before ship | `docs/QA_CHECKLIST.md` |

package/templates/.cursorrules

@@ -51,13 +51,14 @@ All docs live under `docs/`:
 
 6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
 
-7. **When `/build` is invoked: act immediately, no planning, no task list.**
-   - **First:** read `docs/PROJECT.md` + `docs/HUMAN_FLOW.md` silently. If empty, ask one question: *"Describe your idea in one sentence."* Fill docs, then continue.
-   - **Second:** propose 2–3 theme options (one line each), let the user pick, apply to `app/globals.css` + `app/layout.tsx`. This is the first visible output.
-   - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
-   - **Then:** ask "which feature first?" and build just that one.
-   - **No task list at start.** No spec before theme. No gate that blocks visible output.
-   - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
+7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
+   - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
+   - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
+   - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
+   - Run `npm run dev` and confirm the app compiles.
+   - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
+   - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
+   - **No task list. No menu. No options. Build first, show second, ask third.**
 
 ## Quick Orientation for a New Agent Session
 

package/templates/.windsurfrules

@@ -51,13 +51,14 @@ All docs live under `docs/`:
 
 6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
 
-7. **When `/build` is invoked: act immediately, no planning, no task list.**
-   - **First:** read `docs/PROJECT.md` + `docs/HUMAN_FLOW.md` silently. If empty, ask one question: *"Describe your idea in one sentence."* Fill docs, then continue.
-   - **Second:** propose 2–3 theme options (one line each), let the user pick, apply to `app/globals.css` + `app/layout.tsx`. This is the first visible output.
-   - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
-   - **Then:** ask "which feature first?" and build just that one.
-   - **No task list at start.** No spec before theme. No gate that blocks visible output.
-   - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
+7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
+   - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
+   - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
+   - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
+   - Run `npm run dev` and confirm the app compiles.
+   - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
+   - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
+   - **No task list. No menu. No options. Build first, show second, ask third.**
 
 ## Quick Orientation for a New Agent Session
 

package/templates/AGENTS.md

@@ -51,13 +51,14 @@ All docs live under `docs/`:
 
 6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
 
-7. **When `/build` is invoked: act immediately, no planning, no task list.**
-   - **First:** read `docs/PROJECT.md` + `docs/HUMAN_FLOW.md` silently. If empty, ask one question: *"Describe your idea in one sentence."* Fill docs, then continue.
-   - **Second:** propose 2–3 theme options (one line each), let the user pick, apply to `app/globals.css` + `app/layout.tsx`. This is the first visible output.
-   - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
-   - **Then:** ask "which feature first?" and build just that one.
-   - **No task list at start.** No spec before theme. No gate that blocks visible output.
-   - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
+7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
+   - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
+   - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
+   - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
+   - Run `npm run dev` and confirm the app compiles.
+   - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
+   - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
+   - **No task list. No menu. No options. Build first, show second, ask third.**
 
 ## Quick Orientation for a New Agent Session
 

package/templates/CLAUDE.md

@@ -51,13 +51,14 @@ All docs live under `docs/`:
 
 6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
 
-7. **When `/build` is invoked: act immediately, no planning, no task list.**
-   - **First:** read `docs/PROJECT.md` + `docs/HUMAN_FLOW.md` silently. If empty, ask one question: *"Describe your idea in one sentence."* Fill docs, then continue.
-   - **Second:** propose 2–3 theme options (one line each), let the user pick, apply to `app/globals.css` + `app/layout.tsx`. This is the first visible output.
-   - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
-   - **Then:** ask "which feature first?" and build just that one.
-   - **No task list at start.** No spec before theme. No gate that blocks visible output.
-   - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
+7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
+   - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
+   - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
+   - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
+   - Run `npm run dev` and confirm the app compiles.
+   - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
+   - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
+   - **No task list. No menu. No options. Build first, show second, ask third.**
 
 ## Quick Orientation for a New Agent Session