ship-create 1.6.2 → 1.6.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/package.json +1 -1
  2. package/templates/.cursorrules +5 -3
  3. package/templates/.windsurfrules +5 -3
  4. package/templates/AGENTS.md +5 -3
  5. package/templates/CLAUDE.md +5 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ship-create",
3
- "version": "1.6.2",
3
+ "version": "1.6.3",
4
4
  "description": "Scaffold a new project the SHIP Method way — Structure, Human Flow, Instruction, Publish. No git clone, no API key, just one command.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/templates/.cursorrules CHANGED
@@ -62,14 +62,16 @@ All docs live under `docs/`:
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
64
  1. Read `docs/PROJECT.md` — learn what's being built and for whom.
65
- 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.
65
+ 2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
66
66
  3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
67
  4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
68
- 5. Then proceed with what the user asked, applying the rules above.
68
+
69
+ **If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
70
+ Do not present a menu of options. Do not ask what they want. Start `/build` automatically — ask "describe your idea in one sentence" (in the correct language) and begin. The user opened this project to build something; they don't need a list of choices first.
69
71
 
70
72
  **Shortcut commands available:**
71
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
72
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
73
75
 
74
76
  ## Source
75
77
 
package/templates/.windsurfrules CHANGED
@@ -62,14 +62,16 @@ All docs live under `docs/`:
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
64
  1. Read `docs/PROJECT.md` — learn what's being built and for whom.
65
- 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.
65
+ 2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
66
66
  3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
67
  4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
68
- 5. Then proceed with what the user asked, applying the rules above.
68
+
69
+ **If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
70
+ Do not present a menu of options. Do not ask what they want. Start `/build` automatically — ask "describe your idea in one sentence" (in the correct language) and begin. The user opened this project to build something; they don't need a list of choices first.
69
71
 
70
72
  **Shortcut commands available:**
71
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
72
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
73
75
 
74
76
  ## Source
75
77
 
package/templates/AGENTS.md CHANGED
@@ -62,14 +62,16 @@ All docs live under `docs/`:
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
64
  1. Read `docs/PROJECT.md` — learn what's being built and for whom.
65
- 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.
65
+ 2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
66
66
  3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
67
  4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
68
- 5. Then proceed with what the user asked, applying the rules above.
68
+
69
+ **If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
70
+ Do not present a menu of options. Do not ask what they want. Start `/build` automatically — ask "describe your idea in one sentence" (in the correct language) and begin. The user opened this project to build something; they don't need a list of choices first.
69
71
 
70
72
  **Shortcut commands available:**
71
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
72
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
73
75
 
74
76
  ## Source
75
77
 
package/templates/CLAUDE.md CHANGED
@@ -62,14 +62,16 @@ All docs live under `docs/`:
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
64
  1. Read `docs/PROJECT.md` — learn what's being built and for whom.
65
- 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.
65
+ 2. Check **Section 9 Technical Decisions** for `UI language`. If Thai (ภาษาไทย), switch to Thai immediately for all responses. If English, stay in English.
66
66
  3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
67
  4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
68
- 5. Then proceed with what the user asked, applying the rules above.
68
+
69
+ **If the user has not said anything yet and `docs/AI_BUILD_SPEC.md` does not exist:**
70
+ Do not present a menu of options. Do not ask what they want. Start `/build` automatically — ask "describe your idea in one sentence" (in the correct language) and begin. The user opened this project to build something; they don't need a list of choices first.
69
71
 
70
72
  **Shortcut commands available:**
71
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
72
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
73
75
 
74
76
  ## Source
75
77