@onexeor/lumo 0.0.2 → 0.0.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.
- package/README.md +18 -0
- package/package.json +2 -2
- package/skill/SKILL.md +9 -1
- package/src/index.js +1 -1
package/README.md
CHANGED
|
@@ -42,6 +42,24 @@ Under the hood the installer:
|
|
|
42
42
|
The installer never modifies anything outside `~/.lumo`, the chosen
|
|
43
43
|
client's skill directory, and the chosen client's MCP config file.
|
|
44
44
|
|
|
45
|
+
## Publishing (maintainers only)
|
|
46
|
+
|
|
47
|
+
The installer ships with no npm lifecycle scripts on purpose — Socket.dev
|
|
48
|
+
and similar supply-chain scanners penalise packages that auto-execute
|
|
49
|
+
code on install or pack, even when that code is benign. To publish a
|
|
50
|
+
new version:
|
|
51
|
+
|
|
52
|
+
```bash
|
|
53
|
+
cd installer
|
|
54
|
+
bash scripts/release.sh --dry-run # bundles /skill into installer/skill, npm pack --dry-run
|
|
55
|
+
bash scripts/release.sh # same, but actually publishes
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
`release.sh` is the only sanctioned way to build the tarball. Running
|
|
59
|
+
`npm pack` or `npm publish` directly will produce a broken tarball
|
|
60
|
+
without the bundled `SKILL.md`, so `lumo init` would fail
|
|
61
|
+
post-install. The script makes the bundling explicit and Socket-clean.
|
|
62
|
+
|
|
45
63
|
## License
|
|
46
64
|
|
|
47
65
|
MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@onexeor/lumo",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.3",
|
|
4
4
|
"description": "Install Lumo — mobile UI/UX design intelligence for AI coding assistants (Claude Code, Cursor, Codex, MCP clients).",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
},
|
|
18
18
|
"scripts": {
|
|
19
19
|
"start": "node src/index.js",
|
|
20
|
-
"
|
|
20
|
+
"bundle-skill": "node scripts/bundle-skill.js"
|
|
21
21
|
},
|
|
22
22
|
"keywords": [
|
|
23
23
|
"mobile",
|
package/skill/SKILL.md
CHANGED
|
@@ -43,7 +43,15 @@ mobile UI concern, stay out.
|
|
|
43
43
|
|
|
44
44
|
Lumo ships with Python tools. Each tool has a single CLI entry-point with
|
|
45
45
|
deterministic output. Invoke via Bash. Tools live in `tools/lumo/<area>/cli.py`
|
|
46
|
-
and are exposed as console scripts after `pip install -e tools
|
|
46
|
+
and are exposed as console scripts after `pip install -e tools/` or
|
|
47
|
+
`pipx install lumo-mobile`.
|
|
48
|
+
|
|
49
|
+
When running inside an MCP-aware client (Cursor, Continue, Aider, Goose,
|
|
50
|
+
Zed, Codex, or Claude Code with MCP enabled), the same four tools are
|
|
51
|
+
also exposed as MCP functions: `lumo_wcag_check`, `lumo_wcag_fix`,
|
|
52
|
+
`lumo_theory_check`, `lumo_parity_diff`. Prefer the MCP function over
|
|
53
|
+
spawning a Bash subprocess when available — the structured response is
|
|
54
|
+
already JSON and the user does not see noisy command output.
|
|
47
55
|
|
|
48
56
|
### `lumo-wcag` — WCAG contrast validator + OKLCH auto-correct
|
|
49
57
|
|