launchframe 0.4.0 → 0.4.2

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.
@@ -0,0 +1,39 @@
1
+ <!-- AUTO-GENERATED from .claude/skills/launchframe/SKILL.md — do not edit directly.
2
+ Run `node scripts/sync-skills.mjs` to regenerate. -->
3
+
4
+
5
+ # Launchframe
6
+
7
+ Help the user create a **new** Launchframe project. The CLI is **parameterless**:
8
+
9
+ ```bash
10
+ npx launchframe@latest
11
+ ```
12
+
13
+ It unpacks the full template into the **current working directory** (the folder root where the user runs the command). They should `mkdir`, `cd` into an **empty** folder first.
14
+
15
+ ## What you do
16
+
17
+ 1. Ensure the user has an **empty** directory (no existing `package.json`, `src/`, or `next.config.ts` there). If the workspace is already a Launchframe/Next project, they may only need `/clone-website` instead — clarify.
18
+
19
+ 2. Run exactly:
20
+
21
+ ```bash
22
+ npx launchframe@latest
23
+ ```
24
+
25
+ Optional: `LAUNCHFRAME_SOURCE_URL` and `LAUNCHFRAME_SAAS_IDEA` environment variables in the same shell if they want values pre-filled without editing files later.
26
+
27
+ 3. **Never** run this with the output target **inside** the `launchframe` package directory (the npm-installed template). If the open folder is this monorepo/template, have them `mkdir ../my-app && cd ../my-app` (sibling path), then run `npx launchframe@latest` there.
28
+
29
+ 4. Optional flags (same as CLI): `--dir <path>` to scaffold into another folder instead of cwd, `--skip-install` to skip `npm install`.
30
+
31
+ 5. After it finishes: they should **`npm run dev`** from **that same folder** (no extra `cd` if they scaffolded into cwd). Then they edit **`src/lib/launchframe-config.ts`** for reference URL and SaaS idea, and run **`/clone-website`** with that URL.
32
+
33
+ ## If optional notes from the user after the slash command (the CLI itself needs no URL or SaaS strings) are present
34
+
35
+ The user may still paste a URL or idea in chat — **do not** require them for the CLI. Put any extra context into **`src/lib/launchframe-config.ts`** or `launchframe.context.json` for them after scaffold.
36
+
37
+ ## Fallback (local dev only)
38
+
39
+ From a checkout of this repo: `node bin/launchframe.mjs` with the same empty-folder rules (optionally `--dir` outside the package root).