ship-create 1.6.4 → 1.7.0

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 (7) hide show
  1. package/create.mjs +1 -1
  2. package/package.json +1 -1
  3. package/templates/.claude/skills/ship-method/SKILL.md +42 -16
  4. package/templates/.cursorrules +8 -7
  5. package/templates/.windsurfrules +8 -7
  6. package/templates/AGENTS.md +8 -7
  7. package/templates/CLAUDE.md +8 -7
package/create.mjs CHANGED
@@ -43,7 +43,7 @@ const PRODUCT_TYPES = [
43
43
  { key: "SAAS", name: "Web app / SaaS", desc: "users sign up and use a tool online", file: "SAAS_TEMPLATE.md" },
44
44
  { key: "CRM", name: "CRM / Sales pipeline", desc: "track leads, deals, and customers", file: "CRM_TEMPLATE.md" },
45
45
  { key: "MEMBERSHIP", name: "Membership / community", desc: "paid access to content or a community", file: "MEMBERSHIP_TEMPLATE.md" },
46
- { key: "LEADGEN", name: "Landing page / lead capture", desc: "get visitors to fill a form or book a call", file: "LEADGEN_TEMPLATE.md" },
46
+ { key: "LEADGEN", name: "Landing page", desc: "showcase a product or service — sell, capture leads, or book calls", file: "LEADGEN_TEMPLATE.md" },
47
47
  { key: "DIRECTORY", name: "Directory / listing site", desc: "browse and find providers, products, or places", file: "DIRECTORY_TEMPLATE.md" },
48
48
  { key: "DASHBOARD", name: "Dashboard / analytics", desc: "visualise data and KPIs for a team or business", file: "DASHBOARD_TEMPLATE.md" },
49
49
  { key: "INTERNAL_TOOL", name: "Internal tool", desc: "replaces a manual or spreadsheet-based process inside a company", file: "INTERNAL_TOOL_TEMPLATE.md" },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "ship-create",
3
- "version": "1.6.4",
3
+ "version": "1.7.0",
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
@@ -9,32 +9,57 @@ description: Use when starting any new product, feature, or "build me an app" re
9
9
  S — STRUCTURE → H — HUMAN FLOW → I — INSTRUCTION → P — PUBLISH
10
10
  ```
11
11
 
12
- ## When `/build` is invoked — do this immediately, in this order
12
+ ## Phase 1 — Build (runs automatically on first open, no prompts)
13
13
 
14
- **Do not create a task list. Do not plan. Act.**
14
+ **Do not ask anything. Do not show a menu. Just build.**
15
15
 
16
- ### 1. Read (no output, no tasks)
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. 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.
16
+ ### Step 1 — Read & decide (silent, no output)
17
+ Read `docs/PROJECT.md` and `docs/HUMAN_FLOW.md`. Extract:
18
+ - Product type, idea, target user, problem, value prop (already filled by `ship-create`)
19
+ - UI language from Section 9 — switch language now, use it for everything after this
20
+ - Auto-select the best theme from `theme-guide.md` for this product type — do not ask, just pick
18
21
 
19
- ### 2. Theme — first visible output
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.**
22
+ ### Step 2 — Build docs
23
+ Write `docs/AI_BUILD_SPEC.md` immediately — functional requirements for the 2–3 core MVP features + data model. Keep it tight, 1 page max.
21
24
 
22
- ### 3. Home screen — second visible output
23
- 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.
25
+ ### Step 3 — Build prototype
26
+ 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`.
24
27
 
25
- ### 4. Ask one question
26
- *"Which feature do you want to build first?"* Then build just that one.
28
+ ### Step 4 — Run
29
+ Run `npm run dev` (or `pnpm dev` if pnpm is available). Confirm the app compiles and is accessible at localhost:3000.
30
+
31
+ ### Step 5 — Show & ask one question
32
+ Tell the user (in the correct language):
33
+ - What was built and why (2–3 sentences max)
34
+ - Which theme was chosen and why (1 sentence)
35
+ - "เปิด localhost:3000 ดูได้เลย — ชอบทิศทางนี้ไหม?" (Thai) or "Open localhost:3000 — does this feel right?" (English)
36
+
37
+ **That's Phase 1. Wait for the user's answer before doing anything else.**
27
38
 
28
39
  ---
29
40
 
30
- **That's the entire flow.** Steps 1–3 are one session. Features are added one at a time after that.
41
+ ## Phase 2 — Review (after user responds)
42
+
43
+ **If the user likes it:**
44
+ 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`.
45
+
46
+ **If the user wants changes:**
47
+ Ask one focused question: "What feels off?" Make the adjustment, re-run, show again. Do not rebuild everything — change only what they point to.
48
+
49
+ **When the product feels complete to the user:**
50
+ 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.
51
+
52
+ ---
31
53
 
32
54
  ## Hard rules
33
55
 
34
- - **No task list at start.** Create tasks only when building a specific feature, and only 1–2 at a time.
35
- - **No spec before theme.** `docs/AI_BUILD_SPEC.md` is written after the home screen exists, not before.
36
- - **No gates that block visible output.** The only thing that can pause the flow is a missing answer to a direct question.
37
- - **If the user says "skip docs":** comply. Say once what's skipped. Never repeat.
56
+ - **No task list, ever.** Build directly — tasks are invisible internal steps, not output.
57
+ - **No questions before the prototype exists.** The only interaction before Step 5 is code being written.
58
+ - **Theme is chosen by the agent, not the user** — pick the best fit from `theme-guide.md` and explain briefly after.
59
+ - **Run the app before showing results.** Never say "done" without confirming it compiles.
60
+ - **One question at a time.** Never give a list of options or ask multiple things at once.
61
+
62
+ ---
38
63
 
39
64
  ## Reference files
40
65
 
@@ -42,7 +67,8 @@ Read `HUMAN_FLOW.md`. Replace `app/page.tsx` with the real entry point for this
42
67
  |---|---|
43
68
  | Vision, audience, MVP | `docs/PROJECT.md` |
44
69
  | User flow, screens | `docs/HUMAN_FLOW.md` |
45
- | Functional spec | `docs/AI_BUILD_SPEC.md` (written after home screen) |
70
+ | Functional spec | `docs/AI_BUILD_SPEC.md` |
46
71
  | Stack choices | `docs/tech-stack/STACK_DECISION_MATRIX.md` |
47
72
  | UI guidance | invoke `ui-ux-pro-max` skill |
48
73
  | Theme palette table | `theme-guide.md` (this skill folder) |
74
+ | QA before ship | `docs/QA_CHECKLIST.md` |
package/templates/.cursorrules CHANGED
@@ -51,13 +51,14 @@ All docs live under `docs/`:
51
51
 
52
52
  6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
53
53
 
54
- 7. **When `/build` is invoked: act immediately, no planning, no task list.**
55
- - **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.
56
- - **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.
57
- - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
58
- - **Then:** ask "which feature first?" and build just that one.
59
- - **No task list at start.** No spec before theme. No gate that blocks visible output.
60
- - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
54
+ 7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
55
+ - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
56
+ - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
57
+ - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
58
+ - Run `npm run dev` and confirm the app compiles.
59
+ - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
60
+ - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
61
+ - **No task list. No menu. No options. Build first, show second, ask third.**
61
62
 
62
63
  ## Quick Orientation for a New Agent Session
63
64
 
package/templates/.windsurfrules CHANGED
@@ -51,13 +51,14 @@ All docs live under `docs/`:
51
51
 
52
52
  6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
53
53
 
54
- 7. **When `/build` is invoked: act immediately, no planning, no task list.**
55
- - **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.
56
- - **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.
57
- - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
58
- - **Then:** ask "which feature first?" and build just that one.
59
- - **No task list at start.** No spec before theme. No gate that blocks visible output.
60
- - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
54
+ 7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
55
+ - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
56
+ - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
57
+ - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
58
+ - Run `npm run dev` and confirm the app compiles.
59
+ - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
60
+ - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
61
+ - **No task list. No menu. No options. Build first, show second, ask third.**
61
62
 
62
63
  ## Quick Orientation for a New Agent Session
63
64
 
package/templates/AGENTS.md CHANGED
@@ -51,13 +51,14 @@ All docs live under `docs/`:
51
51
 
52
52
  6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
53
53
 
54
- 7. **When `/build` is invoked: act immediately, no planning, no task list.**
55
- - **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.
56
- - **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.
57
- - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
58
- - **Then:** ask "which feature first?" and build just that one.
59
- - **No task list at start.** No spec before theme. No gate that blocks visible output.
60
- - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
54
+ 7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
55
+ - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
56
+ - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
57
+ - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
58
+ - Run `npm run dev` and confirm the app compiles.
59
+ - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
60
+ - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
61
+ - **No task list. No menu. No options. Build first, show second, ask third.**
61
62
 
62
63
  ## Quick Orientation for a New Agent Session
63
64
 
package/templates/CLAUDE.md CHANGED
@@ -51,13 +51,14 @@ All docs live under `docs/`:
51
51
 
52
52
  6. **Never invent business facts** (market size, pricing, real metrics, real user quotes). Draft clearly-labeled `[TBD: ...]` placeholders or ask the user.
53
53
 
54
- 7. **When `/build` is invoked: act immediately, no planning, no task list.**
55
- - **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.
56
- - **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.
57
- - **Third:** replace `app/page.tsx` with the real home screen from `HUMAN_FLOW.md`. User runs `npm run dev` and sees their product.
58
- - **Then:** ask "which feature first?" and build just that one.
59
- - **No task list at start.** No spec before theme. No gate that blocks visible output.
60
- - See `.claude/skills/ship-method/theme-guide.md` for product-type → palette reference.
54
+ 7. **On first open (no `docs/AI_BUILD_SPEC.md` yet): build autonomously, no questions.**
55
+ - Read PROJECT.md + HUMAN_FLOW.md silently. The idea is already there — do not ask again.
56
+ - Auto-pick the best theme from `theme-guide.md` for this product type. Do not ask the user to choose.
57
+ - Write `docs/AI_BUILD_SPEC.md` (tight, 1 page), apply theme, build home screen + first screens.
58
+ - Run `npm run dev` and confirm the app compiles.
59
+ - Then tell the user what was built and ask ONE question: "ชอบทิศทางนี้ไหม?" / "Does this feel right?"
60
+ - **After they answer:** if yes → build features one at a time. If no → ask "what feels off?" and adjust.
61
+ - **No task list. No menu. No options. Build first, show second, ask third.**
61
62
 
62
63
  ## Quick Orientation for a New Agent Session
63
64