ship-create 1.6.1 → 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 (6) hide show
  1. package/package.json +1 -1
  2. package/templates/.claude/skills/ship-method/SKILL.md +1 -1
  3. package/templates/.cursorrules +8 -5
  4. package/templates/.windsurfrules +8 -5
  5. package/templates/AGENTS.md +8 -5
  6. package/templates/CLAUDE.md +8 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ship-create",
3
- "version": "1.6.1",
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/.claude/skills/ship-method/SKILL.md CHANGED
@@ -14,7 +14,7 @@ S — STRUCTURE → H — HUMAN FLOW → I — INSTRUCTION → P — PUBLI
14
14
  **Do not create a task list. Do not plan. Act.**
15
15
 
16
16
  ### 1. Read (no output, no tasks)
17
- 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.
17
+ 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.
18
18
 
19
19
  ### 2. Theme — first visible output
20
20
  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 CHANGED
@@ -61,14 +61,17 @@ All docs live under `docs/`:
61
61
 
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
- 1. Read `docs/PROJECT.md` to learn what's being built and for whom.
65
- 2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
66
- 3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
67
- 4. Then proceed with what the user asked, applying the rules above.
64
+ 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
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
+ 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
+ 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
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.
68
71
 
69
72
  **Shortcut commands available:**
70
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
71
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
72
75
 
73
76
  ## Source
74
77
 
package/templates/.windsurfrules CHANGED
@@ -61,14 +61,17 @@ All docs live under `docs/`:
61
61
 
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
- 1. Read `docs/PROJECT.md` to learn what's being built and for whom.
65
- 2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
66
- 3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
67
- 4. Then proceed with what the user asked, applying the rules above.
64
+ 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
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
+ 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
+ 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
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.
68
71
 
69
72
  **Shortcut commands available:**
70
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
71
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
72
75
 
73
76
  ## Source
74
77
 
package/templates/AGENTS.md CHANGED
@@ -61,14 +61,17 @@ All docs live under `docs/`:
61
61
 
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
- 1. Read `docs/PROJECT.md` to learn what's being built and for whom.
65
- 2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
66
- 3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
67
- 4. Then proceed with what the user asked, applying the rules above.
64
+ 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
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
+ 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
+ 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
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.
68
71
 
69
72
  **Shortcut commands available:**
70
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
71
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
72
75
 
73
76
  ## Source
74
77
 
package/templates/CLAUDE.md CHANGED
@@ -61,14 +61,17 @@ All docs live under `docs/`:
61
61
 
62
62
  ## Quick Orientation for a New Agent Session
63
63
 
64
- 1. Read `docs/PROJECT.md` to learn what's being built and for whom.
65
- 2. Read `docs/HUMAN_FLOW.md` to understand the user experience.
66
- 3. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
67
- 4. Then proceed with what the user asked, applying the rules above.
64
+ 1. Read `docs/PROJECT.md` — learn what's being built and for whom.
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
+ 3. Read `docs/HUMAN_FLOW.md` to understand the user experience.
67
+ 4. Check if `docs/AI_BUILD_SPEC.md` exists — if yes, read it for the technical contract.
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.
68
71
 
69
72
  **Shortcut commands available:**
70
73
  - `/ship` — interactive gate-by-gate guide through Structure → Human Flow → Instruction → Publish
71
- - `/build` — assumes docs are filled, creates build spec and starts coding the MVP
74
+ - `/build` — start building immediately: idea → theme → home screen → first feature
72
75
 
73
76
  ## Source
74
77