ship-create 1.6.1 → 1.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ship-create",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "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`. If core sections are empty, ask the user one question: *"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. 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.
 
 ### 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

@@ -61,10 +61,11 @@ All docs live under `docs/`:
 
 ## Quick Orientation for a New Agent Session
 
-1. Read `docs/PROJECT.md` to learn what's being built and for whom.
-2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
-3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-4. Then proceed with what the user asked, applying the rules above.
+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.
+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.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish

package/templates/.windsurfrules

@@ -61,10 +61,11 @@ All docs live under `docs/`:
 
 ## Quick Orientation for a New Agent Session
 
-1. Read `docs/PROJECT.md` to learn what's being built and for whom.
-2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
-3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-4. Then proceed with what the user asked, applying the rules above.
+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.
+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.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish

package/templates/AGENTS.md

@@ -61,10 +61,11 @@ All docs live under `docs/`:
 
 ## Quick Orientation for a New Agent Session
 
-1. Read `docs/PROJECT.md` to learn what's being built and for whom.
-2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
-3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-4. Then proceed with what the user asked, applying the rules above.
+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.
+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.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish

package/templates/CLAUDE.md

@@ -61,10 +61,11 @@ All docs live under `docs/`:
 
 ## Quick Orientation for a New Agent Session
 
-1. Read `docs/PROJECT.md` to learn what's being built and for whom.
-2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
-3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
-4. Then proceed with what the user asked, applying the rules above.
+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.
+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.
 
 **Shortcut commands available:**
 - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish