@litfamily/litgravity 0.1.9 → 0.1.10

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.
@@ -11,27 +11,40 @@ This file keeps the id. `lit motion …`, `lit film …`, `lit video …`, `lit
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install lit-typographic-motion` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named lit-typographic-motion sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?lit-typographic-motion"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/lit-typographic-motion ] || [ -L ~/.gemini/config/skills/lit-typographic-motion ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/lit-typographic-motion "$b/" && echo "moved to $b/lit-typographic-motion"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/lit-typographic-motion ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" ~/.gemini/config/skills/lit-typographic-motion
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-typographic-motion "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/lit-typographic-motion/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named lit-typographic-motion that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/lit-typographic-motion ] || [ -L .agents/skills/lit-typographic-motion ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/lit-typographic-motion "$b/" && echo "moved to $b/lit-typographic-motion"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/lit-typographic-motion ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" .agents/skills/lit-typographic-motion
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' lit-typographic-motion "<path to your wjgoarxiv-skills clone>/variants/litgravity/lit-typographic-motion" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/lit-typographic-motion/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (readme-studio, which places a motion cover in a README) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-typographic-motion`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-typographic-motion`, the copy is `lit-typographic-motion`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (readme-studio, which places a motion cover in a README) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/lit-typographic-motion`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:lit-typographic-motion`, the copy is `lit-typographic-motion`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/lit-typographic-motion/SKILL.md`, then `.agents/skills/lit-typographic-motion/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what lit-typographic-motion did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-typographic-motion/`), the install line above, and that you made nothing yet. Do not make the film another way in its place (an ffmpeg slideshow, a CSS animation recorded by hand).
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-typographic-motion not installed` once in the ledger and the reply with the install line, finish the parts that need no film, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what lit-typographic-motion did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/lit-typographic-motion/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not make the film another way in its place (an ffmpeg slideshow, a CSS animation recorded by hand).
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `lit-typographic-motion not installed` once in the ledger and the reply with the install lines, finish the parts that need no film, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  LitGravity no longer holds a motion turn open until a render passes: that check left with the engine. The installed copy runs that check itself: `node <its folder>/scripts/motion.mjs done <output folder>` before it calls a film finished. Its engine installs with `node <its folder>/scripts/motion-runtime.mjs install`.
32
45
 
33
46
  ## Hard stops
34
47
 
35
- - Give the install line with the placeholder; never a path from this machine.
48
+ - Give the install lines with the placeholder; never a path from this machine.
36
49
  - Never say a film exists unless the installed copy made it and you looked at the result.
37
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
50
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit readme …`, `lit readme-studio …`, and `/litgrav
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install readme-studio` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named readme-studio sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?readme-studio"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/readme-studio ] || [ -L ~/.gemini/config/skills/readme-studio ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/readme-studio "$b/" && echo "moved to $b/readme-studio"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/readme-studio ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" ~/.gemini/config/skills/readme-studio
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' readme-studio "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/readme-studio/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named readme-studio that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/readme-studio ] || [ -L .agents/skills/readme-studio ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/readme-studio "$b/" && echo "moved to $b/readme-studio"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/readme-studio ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" .agents/skills/readme-studio
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' readme-studio "<path to your wjgoarxiv-skills clone>/variants/litgravity/readme-studio" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/readme-studio/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-typographic-motion, which renders the optional motion cover) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/readme-studio`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:readme-studio`, the copy is `readme-studio`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (lit-typographic-motion, which renders the optional motion cover) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/readme-studio`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:readme-studio`, the copy is `readme-studio`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/readme-studio/SKILL.md`, then `.agents/skills/readme-studio/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what readme-studio did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/readme-studio/`), the install line above, and that you made nothing yet. A plain README edit the user asks for by line can still be made directly; a new or refreshed README from this skill cannot.
29
- 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `readme-studio not installed` once in the ledger and the reply with the install line, finish the parts that need no README, and mark the part that needs it BLOCKED, not done.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what readme-studio did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/readme-studio/`), the `extensions install` command and the install lines above, and that you made nothing yet. A plain README edit the user asks for by line can still be made directly; a new or refreshed README from this skill cannot.
42
+ 4. **Not found, inside a workflow.** Inside a lit workflow (lit-loop, litwork, start-work, review-work) that reached this skill, write `readme-studio not installed` once in the ledger and the reply with the install lines, finish the parts that need no README, and mark the part that needs it BLOCKED, not done.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a README exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.
@@ -11,25 +11,38 @@ This file keeps the id. `lit visual-qa …`, `/litgravity:visual-qa`, review-wor
11
11
 
12
12
  ## Install it in agy
13
13
 
14
- wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then copy the skill folder into agy's user skills, which every workspace sees:
14
+ The short route is LitGravity's own command, run in a terminal: `npx @litfamily/litgravity extensions install visual-qa` prints what it would do, and the same with `--yes` does it (`--project` for one workspace). It fetches the skill, stops if another skill named visual-qa sits where agy loads skills, moves an old copy aside and writes the receipt; `extensions update`, `remove` and `check` do the rest. The lines below are the same steps by hand.
15
+
16
+ wjgoarxiv-skills is public at https://github.com/wjgoarxiv/wjgoarxiv-skills. Clone it (`git clone https://github.com/wjgoarxiv/wjgoarxiv-skills`), then paste these four lines one at a time (zsh or bash) in the workspace you use agy in. They put the skill in agy's user skills, which every workspace sees:
15
17
 
16
18
  ```bash
17
- mkdir -p ~/.gemini/config/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" ~/.gemini/config/skills/
19
+ find .agents/skills _agents/skills ~/.gemini/config/skills ~/.gemini/skills -maxdepth 2 -name SKILL.md -exec grep -l -E '^name: *"?visual-qa"? *$' {} + 2>/dev/null
20
+ if [ -e ~/.gemini/config/skills/visual-qa ] || [ -L ~/.gemini/config/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S); mkdir -p "$b" && mv ~/.gemini/config/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi
21
+ mkdir -p ~/.gemini/config/skills && [ ! -e ~/.gemini/config/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" ~/.gemini/config/skills/visual-qa
22
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > ~/.gemini/config/skills/visual-qa/.litfamily-extension.json
18
23
  ```
19
24
 
20
- For one workspace only, run this in its root instead: `mkdir -p .agents/skills && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" .agents/skills/`.
25
+ Line one only looks: it prints every `SKILL.md` named visual-qa that agy could load, and nothing when there is none. agy keeps one same-name skill without a word, a workspace copy first, so move any other one it names aside too. Line two moves an existing copy whole into a dated folder under `~/.gemini/extension-backups/`, which agy never loads; line three copies into the emptied place; line four writes the receipt `.litfamily-extension.json` inside the copy.
26
+
27
+ For one workspace only, run line one, then these three in the workspace root:
28
+
29
+ ```bash
30
+ if [ -e .agents/skills/visual-qa ] || [ -L .agents/skills/visual-qa ]; then b=~/.gemini/extension-backups/$(date +%Y%m%d-%H%M%S)-project; mkdir -p "$b" && mv .agents/skills/visual-qa "$b/" && echo "moved to $b/visual-qa"; fi
31
+ mkdir -p .agents/skills && [ ! -e .agents/skills/visual-qa ] && cp -R "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" .agents/skills/visual-qa
32
+ printf '{"id":"%s","source":"%s","variant":"litgravity","installed_at":"%s"}\n' visual-qa "<path to your wjgoarxiv-skills clone>/variants/litgravity/visual-qa" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" > .agents/skills/visual-qa/.litfamily-extension.json
33
+ ```
21
34
 
22
- The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (frontend-ui-ux, the builder this check accepts work from) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/visual-qa`, and `lit` prompts that reach this stub hand over to it. To update it, delete the copied folder and copy it again. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:visual-qa`, the copy is `visual-qa`.
35
+ The folder is the whole skill, with its own scripts, references and engine locks. Its neighbours (frontend-ui-ux, the builder this check accepts work from) install the same way, one folder each. Start a new conversation, or type `/skills reload`; the skill then answers as `/visual-qa`, and `lit` prompts that reach this stub hand over to it. To update it, run the same lines again: the old copy moves to a new dated backup and the receipt is rewritten. To remove it, run the second line alone. Nothing is deleted; clear old backups out of `~/.gemini/extension-backups/` when you no longer need them. The LitGravity installer writes only its own plugin folder, so upgrading or removing LitGravity leaves the copy alone, and the names never clash: this stub is `litgravity:visual-qa`, the copy is `visual-qa`.
23
36
 
24
37
  ## When this stub is read
25
38
 
26
39
  1. Look for the installed copy with `read_file`: first `~/.gemini/config/skills/visual-qa/SKILL.md`, then `.agents/skills/visual-qa/SKILL.md` in the workspace.
27
40
  2. **Found.** Read it and follow it for this task; its folder is the root for every relative path it names. It was written for agy and needs no LitGravity hook: every check it names is a command it tells you to run.
28
- 3. **Not found, asked directly.** Reply in a few lines: what visual-qa did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/visual-qa/`), the install line above, and that you made nothing yet. Do not describe the page from its source and call that a visual check.
41
+ 3. **Not found, asked directly.** Reply in a few lines: what visual-qa did, that it is a LitFamily extension now, kept in wjgoarxiv-skills (`variants/litgravity/visual-qa/`), the `extensions install` command and the install lines above, and that you made nothing yet. Do not describe the page from its source and call that a visual check.
29
42
  4. **Not found, inside a workflow.** Inside review-work or litwork, record `visual-qa not installed` in the lane and give no visual verdict: the surface stays unchecked, not passed.
30
43
 
31
44
  ## Hard stops
32
45
 
33
- - Give the install line with the placeholder; never a path from this machine.
46
+ - Give the install lines with the placeholder; never a path from this machine.
34
47
  - Never say a visual check exists unless the installed copy made it and you looked at the result.
35
- - A headless run (`agy -p`) never copies the skill in itself: give the install line and stop.
48
+ - A headless run (`agy -p`) never copies the skill in itself: give the install lines and stop.