ship-create 1.6.2 → 1.6.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ship-create",
-  "version": "1.6.2",
+  "version": "1.6.4",
   "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

@@ -14,7 +14,7 @@ S — STRUCTURE  →  H — HUMAN FLOW  →  I — INSTRUCTION  →  P — PUBLI
 **Do not create a task list. Do not plan. Act.**
 
 ### 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. If core sections are empty, ask the user one question (in the correct language): *"Describe your idea in one sentence."* Fill the docs from their answer, then continue.
+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.
 
 ### 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.**

package/templates/.cursorrules

@@ -62,14 +62,16 @@ All docs live under `docs/`:
 ## Quick Orientation for a New Agent Session
 
 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
-2. Check **Section 9 Technical Decisions** in `PROJECT.md` for `UI language`. If it says Thai (ภาษาไทย), switch to Thai immediately and use Thai for all responses, questions, and output for the rest of this session. If English, stay in English.
+2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-5. Then proceed with what the user asked, applying the rules above.
+
+**If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
+Do not present a menu of options. Do not ask what they want. Do not ask them to describe their idea — it is already in `docs/PROJECT.md` Section 10 (Original Idea) and Section 1 (Product Vision). Start `/build` automatically using what is already there. The user described their idea during `npx ship-create`; asking again is unnecessary friction.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
-- `/build` — assumes docs are filled, creates build spec and starts coding the MVP
+- `/build` — start building immediately: idea → theme → home screen → first feature
 
 ## Source
 

package/templates/.windsurfrules

@@ -62,14 +62,16 @@ All docs live under `docs/`:
 ## Quick Orientation for a New Agent Session
 
 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
-2. Check **Section 9 Technical Decisions** in `PROJECT.md` for `UI language`. If it says Thai (ภาษาไทย), switch to Thai immediately and use Thai for all responses, questions, and output for the rest of this session. If English, stay in English.
+2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-5. Then proceed with what the user asked, applying the rules above.
+
+**If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
+Do not present a menu of options. Do not ask what they want. Do not ask them to describe their idea — it is already in `docs/PROJECT.md` Section 10 (Original Idea) and Section 1 (Product Vision). Start `/build` automatically using what is already there. The user described their idea during `npx ship-create`; asking again is unnecessary friction.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
-- `/build` — assumes docs are filled, creates build spec and starts coding the MVP
+- `/build` — start building immediately: idea → theme → home screen → first feature
 
 ## Source
 

package/templates/AGENTS.md

@@ -62,14 +62,16 @@ All docs live under `docs/`:
 ## Quick Orientation for a New Agent Session
 
 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
-2. Check **Section 9 Technical Decisions** in `PROJECT.md` for `UI language`. If it says Thai (ภาษาไทย), switch to Thai immediately and use Thai for all responses, questions, and output for the rest of this session. If English, stay in English.
+2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-5. Then proceed with what the user asked, applying the rules above.
+
+**If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
+Do not present a menu of options. Do not ask what they want. Do not ask them to describe their idea — it is already in `docs/PROJECT.md` Section 10 (Original Idea) and Section 1 (Product Vision). Start `/build` automatically using what is already there. The user described their idea during `npx ship-create`; asking again is unnecessary friction.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
-- `/build` — assumes docs are filled, creates build spec and starts coding the MVP
+- `/build` — start building immediately: idea → theme → home screen → first feature
 
 ## Source
 

package/templates/CLAUDE.md

@@ -62,14 +62,16 @@ All docs live under `docs/`:
 ## Quick Orientation for a New Agent Session
 
 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
-2. Check **Section 9 Technical Decisions** in `PROJECT.md` for `UI language`. If it says Thai (ภาษาไทย), switch to Thai immediately and use Thai for all responses, questions, and output for the rest of this session. If English, stay in English.
+2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-5. Then proceed with what the user asked, applying the rules above.
+
+**If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
+Do not present a menu of options. Do not ask what they want. Do not ask them to describe their idea — it is already in `docs/PROJECT.md` Section 10 (Original Idea) and Section 1 (Product Vision). Start `/build` automatically using what is already there. The user described their idea during `npx ship-create`; asking again is unnecessary friction.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
-- `/build` — assumes docs are filled, creates build spec and starts coding the MVP
+- `/build` — start building immediately: idea → theme → home screen → first feature
 
 ## Source