@stage5/lumine 0.1.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.
- package/README.md +52 -0
- package/bin/lumine.js +1429 -0
- package/package.json +20 -0
package/README.md
ADDED
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# Lumine CLI
|
|
2
|
+
|
|
3
|
+
Launch Twinkle Lumine builds from any terminal.
|
|
4
|
+
|
|
5
|
+
```bash
|
|
6
|
+
npx @stage5/lumine@latest
|
|
7
|
+
npx @stage5/lumine@latest login
|
|
8
|
+
npx @stage5/lumine@latest projects
|
|
9
|
+
npx @stage5/lumine@latest pull
|
|
10
|
+
npx @stage5/lumine@latest save
|
|
11
|
+
npx @stage5/lumine@latest save --publish
|
|
12
|
+
npx @stage5/lumine@latest launch https://www.twin-kle.com/app/123
|
|
13
|
+
```
|
|
14
|
+
|
|
15
|
+
Run `lumine` with no subcommand for the easiest flow: sign in when needed,
|
|
16
|
+
choose one of your owned or team projects, and pull the saved project files into
|
|
17
|
+
a local folder.
|
|
18
|
+
|
|
19
|
+
For team projects, Lumine mirrors the website workspace flow: choosing or
|
|
20
|
+
pulling the owner's main project creates or reuses your contribution branch and
|
|
21
|
+
checks out that branch locally. Saves go to your branch, so the project owner
|
|
22
|
+
can merge or replace main from Twinkle.
|
|
23
|
+
|
|
24
|
+
After editing pulled files, run `lumine save` from that folder. The CLI saves
|
|
25
|
+
through Twinkle's normal workspace project-file route, creates a project artifact
|
|
26
|
+
version, records the same save metadata, and marks public builds as having
|
|
27
|
+
unpublished changes. For projects you own, run `lumine launch` to publish the
|
|
28
|
+
saved changes, or `lumine save --publish` to save and publish in one step.
|
|
29
|
+
|
|
30
|
+
Pulled workspaces include `AGENTS.md` and `CLAUDE.md` guides for local coding
|
|
31
|
+
agents, plus `.twinkle/lumine-project.json` metadata that tells agents whether
|
|
32
|
+
the checkout is writable, publishable, or a contribution branch. These guide
|
|
33
|
+
files are not uploaded by `lumine save`. Build apps run in sandboxed iframes
|
|
34
|
+
without native form submission, so use JavaScript-handled inputs and buttons
|
|
35
|
+
instead of `<form>` elements.
|
|
36
|
+
|
|
37
|
+
After pulling a project, run an agent from the pulled folder:
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
codex "Read AGENTS.md, then make the requested change."
|
|
41
|
+
claude "Read CLAUDE.md, then make the requested change."
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
The login command uses a browser approval code and stores a scoped token and the
|
|
45
|
+
selected project at `~/.twinkle/lumine-cli-auth.json`.
|
|
46
|
+
|
|
47
|
+
`lumine login` opens the Twinkle approval page automatically. If you are running
|
|
48
|
+
in SSH, CI, or an agent environment, use:
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
npx @stage5/lumine@latest login --no-open
|
|
52
|
+
```
|