@litfamily/litgrok 1.0.9 → 1.0.11

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.
@@ -7,7 +7,7 @@ Engine
7
7
  The page shaders carry simplex noise by Ashima Arts and Stefan Gustavson (MIT).
8
8
 
9
9
  Engine dependencies (installed by `litgrok-ai motion-runtime install`, not shipped here)
10
- opentype.js 1.3.4 (MIT), ws 8.18.3 (MIT), string.prototype.codepointat 0.2.1 (MIT),
10
+ opentype.js 1.3.4 (MIT), ws 8.22.0 (MIT), string.prototype.codepointat 0.2.1 (MIT),
11
11
  tiny-inflate 1.0.3 (MIT); licence texts install with each package in the motion cache.
12
12
  Tier 2 only: librosa and the packages pinned in requirements-audio.txt, installed with
13
13
  `--audio`; each package's licence installs with it in the audio venv.
@@ -7,7 +7,7 @@
7
7
  "name": "litgrok-motion-runtime",
8
8
  "dependencies": {
9
9
  "opentype.js": "1.3.4",
10
- "ws": "8.18.3"
10
+ "ws": "8.22.0"
11
11
  }
12
12
  },
13
13
  "node_modules/opentype.js": {
@@ -39,9 +39,9 @@
39
39
  "license": "MIT"
40
40
  },
41
41
  "node_modules/ws": {
42
- "version": "8.18.3",
43
- "resolved": "https://registry.npmjs.org/ws/-/ws-8.18.3.tgz",
44
- "integrity": "sha512-PEIGCY5tSlUt50cqyMXfCzX+oOPqN0vuGqWzbcJ2xvnkzkq46oOpz7dQaTDBdfICb4N14+GARUDw2XV2N4tvzg==",
42
+ "version": "8.22.0",
43
+ "resolved": "https://registry.npmjs.org/ws/-/ws-8.22.0.tgz",
44
+ "integrity": "sha512-Ydggc987+RO0AnWtZ/7Wq9FtNvcrL1b/RO0ud9mWjUPgDrsAAwQSF51sm2hm1XofbU/4jkpGEsLFsZZxU+1DOg==",
45
45
  "license": "MIT",
46
46
  "engines": {
47
47
  "node": ">=10.0.0"
@@ -5,6 +5,6 @@
5
5
  "description": "Pinned engine dependencies for lit-typographic-motion, installed only by litgrok-ai motion-runtime install.",
6
6
  "dependencies": {
7
7
  "opentype.js": "1.3.4",
8
- "ws": "8.18.3"
8
+ "ws": "8.22.0"
9
9
  }
10
10
  }
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "litgrok",
3
- "version": "1.0.9",
3
+ "version": "1.0.11",
4
4
  "description": "Grok Build skills, project rules, and bounded lifecycle hooks for evidence-first lit work.",
5
5
  "author": {
6
6
  "name": "LitGrok contributors"
package/CHANGELOG.md CHANGED
@@ -2,6 +2,16 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ ## 1.0.11 — 2026-09-29
6
+
7
+ - The READMEs and the npm install page, in English and Korean, are rewritten in plainer language, with the reason before each switch. The npm page stays a short install card that links to the full guide on GitHub.
8
+
9
+ ## 1.0.10 — 2026-09-29
10
+
11
+ - lit-typographic-motion: the motion runtime now pins `ws` 8.22.0, which fixes a memory-exhaustion denial of service and an uninitialized-memory disclosure in 8.18.3. Run `litgrok-ai motion-runtime install` again after upgrading.
12
+ - The npm package no longer picks up Python bytecode (`__pycache__`, `.pyc`) left in the lit-pptx and lit-docx script folders.
13
+ - The READMEs are rewritten in plainer language, and GitHub and npmjs now get different pages: the full guide with the skills gallery stays on GitHub, and npmjs shows a shorter install-first page from `docs/npm/`, swapped in when the package is packed.
14
+
5
15
  ## 1.0.9 — 2026-09-28
6
16
 
7
17
  - lit-pptx: the second rich render style id is now `green`.
package/CONTRIBUTING.md CHANGED
@@ -17,6 +17,8 @@ The suite includes package, installer, ownership, hooks, and static documentatio
17
17
 
18
18
  For a behavior change, preserve a failing regression and test the corrected path plus a meaningful refusal case. Exercise installations in a disposable project and HOME with separate TMPDIR and npm cache. Interactive writes require a terminal; CI and no-color modes remain no-write previews even with `--yes`. Never use a real user profile as a fixture. Preserve unrelated settings, changed skills, and unsafe destinations; clean only your own temporary resources.
19
19
 
20
+ GitHub and npmjs show different READMEs. `README.md` and `README_ko-KR.md` are the GitHub pages and use repository-relative paths. The shorter npm pages live in `docs/npm/` and pin every image and file link to the package version on jsDelivr. `npm pack` swaps them in through the `prepack` and `postpack` scripts and puts the GitHub pages back afterwards. A release that packs or publishes with `--ignore-scripts` skips those scripts, so run `node scripts/readme-for-npm.mjs apply` right before it and `node scripts/readme-for-npm.mjs restore` right after it; run the test suite before `apply`, because the tests read the GitHub pages. `npm run check:npm-readme` checks the npm pages on their own.
21
+
20
22
  Keep npm identity separate from executable aliases and ownership IDs. Do not add dependencies, undocumented host surfaces, or an updater to solve a documentation change. Keep vendor bytes, license notices, accepted artwork, and unrelated changes intact. Product versions and release actions require a separate maintainer decision; CI validates only.
21
23
 
22
24
  In a pull request, state the trigger and resulting behavior, changed scope, checks with results, unresolved limitations, and cleanup. Remove secrets, transcript excerpts, identifying paths, and credentials from reports. See [security](./SECURITY.md), [privacy](./docs/privacy.md), and the [code of conduct](./CODE_OF_CONDUCT.md).
package/README.md CHANGED
@@ -1,435 +1,110 @@
1
- <p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/cover-motion.webp" width="100%" alt="LitFamily motion cover: five armored robots power on one by one, the LitGrok robot wakes with glowing eyes and a lit frame, then LITFAMILY and KEEP THE WORK LIT. light up." /></picture></p>
2
-
3
- <p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/ascii-readme.svg" width="480" alt="LIT ASCII B mark — Grok" /></p>
4
-
5
- <details>
6
- <summary>Copy ASCII logo</summary>
7
-
8
- ```text
9
- ▄▄▄▄
10
- ▗███▌ ▗██████▖
11
- ▗▄▄▄▄▄ ▗▟████▌ ▝██████▘
12
- ▐█████ ▗▟██████▌ ▝▀▜█▀▘
13
- ▐█████ ▗▟███████▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
14
- ▐█████ ▗▟█████████████████████████ ▐█▀
15
- ▐█████ ████████████████████████████▀
16
- ▐█████ ██▛▘ ▄ ▄▄▄▄▖▄▄▄▄▄▄▄▄▄▄▄▄▄▖
17
- ▐█████ ▀ ▄██ ████▌█████████████▌
18
- ▐█████ ▄████ ████▌█████████████▌
19
- ▐█████ ▄█████▛
20
- ▐█████ ▗▟█████▀▘ ▄▄▄▄▄ ▗▖
21
- ▐█████ ▐█████▀ █████ ▐▛▀
22
- ▐█████ ▐███▀ █████
23
- ▐█████ ▐█▀ █████
24
- ▐█████ ▝ █████
25
- ▐█████▄▄▄▄▄▄▄▖ █████
26
- ▐███████████▛ █████
27
- ▐██████████▀ █████
28
-
29
-
30
- grok
31
- ```
32
-
33
- </details>
1
+ <p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/cover-motion.webp" width="100%" alt="LitFamily motion cover: five armored robots power on one by one, the LitGrok robot wakes with glowing eyes and a lit frame, then LITFAMILY and KEEP THE WORK LIT. light up." /></picture></p>
34
2
 
35
3
  <h1 align="center">LitGrok</h1>
36
4
  <p align="center"><strong>Keep the work lit.</strong></p>
37
5
 
38
6
  Make something useful in Grok Build. Leave the checked result and the next step with your project.
39
7
 
40
- [한국어](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/README_ko-KR.md) · [Install](#install-in-30-seconds) · [Quick start](#quick-start) · [Skills](#skills-at-a-glance) · [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md)
8
+ **[Full guide and skills gallery on GitHub](https://github.com/wjgoarxiv/litgrok#readme)** · [한국어](https://github.com/wjgoarxiv/litgrok/blob/main/README_ko-KR.md) · [Install](#install-in-30-seconds) · [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/reference.md)
41
9
 
42
10
  <p align="center">
43
- <a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/badge-version.svg" alt="1.0.9" /></a>
44
- <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
11
+ <a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/readme/badge-version.svg" alt="1.0.11" /></a>
12
+ <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
45
13
  </p>
46
14
 
47
- <p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> &nbsp; <a href="#install-in-30-seconds">Install</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Cover motion</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
15
+ <p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/reference.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> &nbsp; <a href="#install-in-30-seconds">Install</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Cover motion</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
16
+
17
+ LitGrok gives Grok Build a way of working: plan the change, build it, check it, and leave a handoff the next session can read. It ships 38 skills, 11 agents, one project rule, and eleven hook registrations. Grok Build still runs the session and chooses the model.
48
18
 
49
19
  ## Install in 30 seconds
50
20
 
51
- With Node.js and Grok Build available, use an open interactive terminal in the project you want to try. The primary install uses the scoped package:
21
+ You need Node.js and Grok Build. In an interactive terminal, from the project you want to try:
52
22
 
53
23
  ```bash
54
24
  npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
55
25
  ```
56
26
 
57
- For an optional isolated trial, set the actual absolute path of the supplied local package, then run these two lines separately:
27
+ The files land in `<project>/.grok/`. Add `--user` to install under `~/.grok/` instead, or use `--package @litfamily/litgrok@1.0.11` to pin this release. Add `--dry-run` to see every destination before anything is written.
28
+
29
+ Trying a local package instead? Put its real absolute path in a variable, then run these two lines separately:
58
30
 
59
31
  ```bash
60
32
  LITGROK_PACK='/absolute/path/to/the-provided-package.tgz'
61
33
  npm exec --yes --package "$LITGROK_PACK" -- litgrok install
62
34
  ```
63
35
 
64
- The default destination is `<project>/.grok/`. Use `--package @litfamily/litgrok@1.0.9` for a pinned install, or add `--user` to install under `~/.grok/`. [Install and upgrade details](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#install).
65
-
66
- The persistent Grok status row is optional and user-level only. Opt in with:
67
-
68
- ```bash
69
- npm exec --yes --package @litfamily/litgrok@latest -- litgrok install --user --status-line
70
- ```
71
-
72
- This adds `[ui.status_line]` to `~/.grok/config.toml` with a two-second refresh. If a config already exists, LitGrok backs it up before changing it; an existing `ui.status_line` is preserved. `uninstall --user` removes only the unchanged LitGrok-managed value. Grok reads this setting from user or administrator configuration, not from project or plugin configuration ([status-line docs](https://docs.x.ai/build/features/status-line), [settings reference](https://docs.x.ai/build/settings/reference)). Example rows are `🔥 LIT IGNITED · lit-plan 🔥 │ grok-4 │ ctx 42%` and `LIT · grok │ grok-4 │ ctx 42%`. The first visible prompt match among `lit-scientific-visualization`, `lit-handoff`, `autoconference`, `autoresearch`, `lit-plan`, and `litwork` sets the discipline; bare `lit` maps to `litwork`, and inline or fenced Markdown code is ignored. With color enabled, the active `LIT IGNITED · <discipline>` label is bold with a per-character truecolor gradient `#FF6337 → #FF2D95 → #00E5FF`; the flames and model/context segment remain unstyled. `NO_COLOR` (including an empty value) or `LITGROK_HUD_COLOR=0` keeps the row plain. Truecolor, bold and emoji rendering in the status row were confirmed on Grok Build 1.0.13. This adds a status command, not another hook registration; LitGrok still ships eleven hook registrations.
36
+ ## The first thing to type
73
37
 
74
- ### Safety and uninstall
75
-
76
- Preview the exact destinations before writing:
77
-
78
- ```bash
79
- npm exec --yes --package "$LITGROK_PACK" -- litgrok install --dry-run
80
- ```
81
-
82
- The installer verifies file ownership before upgrades or removal. Modified, foreign, or unsafe destination files cause the operation to refuse rather than overwrite them. `CI`, `NO_COLOR` (even empty), `--no-color`, and `--dry-run` are no-write previews regardless of `--yes`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, it proceeds without a TTY as long as none of the above apply.
83
-
84
- For a local-package install, remove it with the same package in the same project. Add `--user` only to remove an installation made with `--user`.
85
-
86
- ```bash
87
- npm exec --yes --package "$LITGROK_PACK" -- litgrok uninstall
88
- ```
89
-
90
- Registry uninstall commands:
91
-
92
- ```bash
93
- npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall
94
- npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
95
- ```
96
-
97
- User-level uninstall backs up `~/.grok/config.toml` before removing the unchanged LitGrok-managed status-line keys; other settings and a user-edited status line are preserved. Match the scope used for installation. Re-run `install` to update. The installer does not grant hook trust, create a Git root, write login state or API keys, or choose a model. The hedge guard is fail-open on host errors; a passing package test does not prove live Grok behavior. Check `/hooks` and `grok inspect --json` from the repository root in your own session. [Host boundaries and verification](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#verify).
98
-
99
- ## Quick start
100
-
101
- Open or restart Grok Build at the installed project’s Git root. Review and trust its project hooks with `/hooks-trust`, or, on the observed Grok Build 1.0.23 host, use `grok --trust inspect --json`. A plain folder can still load skills and rules while hooks remain unavailable. Check `/skills` for the installed catalog and `/hooks` for hook registrations. LitGrok does not create a Git root or change trust.
102
-
103
- Start with a small task that needs no external service or existing test suite. Send this in Grok Build:
38
+ Open (or restart) Grok Build from the project's Git root. Grok runs project hooks only after you trust them, so review and trust them in `/hooks-trust`; on Grok Build 1.0.23, `grok --trust inspect --json` did the same. In a plain folder without Git, the skills and rules load but the hooks stay off. Then send:
104
39
 
105
40
  ```text
106
41
  /litwork Build a to-do list in one index.html with no external dependencies. Implement add, complete, and delete. Leave the checks performed and the next step. Do not open a browser automatically; give me the steps to check it myself.
107
42
  ```
108
43
 
109
- Open the generated `index.html` yourself and try adding, completing, and deleting an item. Creating a file and checking its behavior are separate steps. Leave any unrun checks marked unverified; report actual errors back to the session.
44
+ Then open `index.html` yourself and add, complete and delete an item. That click-through is the real test; anything you didn't try stays marked unverified.
110
45
 
111
- ### Carry the spark into the next session
46
+ ## Carry the work into the next session
112
47
 
113
- ```text
114
- Plan → Build → Verify → Hand off
115
- ```
116
-
117
- For a larger change, start with `/lit-plan`, review the saved plan, then invoke `/start-work <plan path>`. Before stopping, ask:
48
+ For a larger change, start with `/lit-plan`, read the plan it saves, then run `/start-work <plan path>`. Before you stop, ask:
118
49
 
119
50
  ```text
120
51
  /lit-handoff Record what we built, what we checked, and what remains. Tell me where you saved the handoff.
121
52
  ```
122
53
 
123
- In the next session, supply that returned path and ask Grok Build to read it and check the current files before continuing. The default is `.handoff/HANDOFF.md` in a new Git project or `HANDOFF.md` in a non-Git workspace. An existing root handoff is reused. [Destination and handoff guidance](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/.grok/skills/lit-handoff/SKILL.md).
124
-
125
- **Keeping the spark means leaving work another session can pick up.** These are skill-guided steps in your session; LitGrok does not schedule background work or continue after the session ends.
54
+ Next time, give Grok Build the path it returned and ask it to read the handoff and check the current files before it continues.
126
55
 
127
- ## Key features
56
+ ## Routes people use
128
57
 
129
- > **A spark has been placed in your hands. Put it to work.**
130
- >
131
- > A bug you want fixed. A screen you want built. A project you want to finish.
132
- >
133
- > Starting takes a line. When the session changes, the harder part is finding where you left off. LIT guides you through leaving a goal, a plan, a checked result, and a next step with your project.
134
- >
135
- > **Leave something the next session can pick up.**
136
-
137
- It ships 38 skills, 11 agents, one project rule, and eleven hook registrations. The installer copies the complete payload into your project; Grok Build runs the session and owns model selection.
58
+ | Type this | What happens |
59
+ | --- | --- |
60
+ | `/litwork` | Starts the shipped work checklist for a bounded task. |
61
+ | `handoff` or `/lit-handoff` | Carries the checked result and the next step into another session. |
62
+ | `/lit-plan` | Writes a plan with concrete checks. |
63
+ | `/start-work <approved-plan>` | Executes a plan you approved. |
64
+ | `/review-work` | Reviews a change and its evidence. |
65
+ | `/litresearch` | Runs bounded, source-traceable research without overstating the evidence. |
138
66
 
139
- Use `lit-humanizer` for longer edits or a Korean deep review. The pre-write guard checks newly added reader-facing prose: clear block-tier matches must be revised before saving, while warning-tier matches stay advisory. Created DOCX and PPTX files are checked after the tool runs; PDFs are checked with `pdftotext` when it is available. A missing extractor leaves the output unchanged and reports the inspection boundary.
67
+ `/skills` lists everything your session loaded. The [skills gallery on GitHub](https://github.com/wjgoarxiv/litgrok#skills-at-a-glance) shows all 38 with a picture of each result.
140
68
 
141
- Check browser automation with `npm run probe:browser-drive`. LitGrok names [agent-browser](https://github.com/vercel-labs/agent-browser) as its CLI engine but never installs it for you. If the probe reports it missing, install it yourself with `npm install -g agent-browser` followed by `agent-browser install`.
69
+ Beyond code, `lit-pptx` makes slide decks, `lit-docx` makes reports and Word documents, `/frontend-ui-ux` builds and checks interfaces, `/readme-studio` writes source-checked READMEs, and `lit-humanizer` rewrites stiff English or Korean prose.
142
70
 
143
- Package: `@litfamily/litgrok` · Version: `1.0.9` · [MIT](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/LICENSE)
71
+ ## What changes after install
144
72
 
145
- The scientific visualization corpus is packaged at `.grok/vendor/scientific-visualization/`; the numeric `045_scientific-visualization` label remains only in license and provenance filenames.
73
+ The installer copies the skills, agents, project rule, and hooks into `.grok/`. The eleven hook registrations in [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/hooks/hooks.json) run only in a trusted Git root, and they log the order of events in `.grok/litgrok/session-ledger/`. Everything runs inside your Grok session, and nothing runs in the background; when the session ends, the work waits for the next one.
146
74
 
147
- These route examples are static guidance, not proof of live host behavior.
75
+ If you'd like a status row showing the active LitGrok skill, the model and how much context is used, add it with `install --user --status-line`. It writes `[ui.status_line]` into `~/.grok/config.toml` and backs up an existing file first.
148
76
 
149
- The five activation contracts ask the model to start each activated response with exactly one line before other response content. For `/litwork`, the requested line is:
77
+ ## Safety and uninstall
150
78
 
151
- 🔥 **LIT IGNITED · litwork** 🔥
79
+ Before it upgrades or removes a file, the installer checks that the file is one it put there. If any file was edited, belongs to something else or looks unsafe, it stops before writing anything and names that file.
152
80
 
153
- This is advisory prompt guidance; it does not verify native host display.
81
+ Some runs only preview: the installer lists what it would do, prints `no files written`, and stops, even with `--yes`. That happens with:
154
82
 
155
- The retained `docs/assets/cover.svg` remains editable vector artwork; the README uses a still frame of the motion cover when reduced motion is preferred.
83
+ - `--dry-run`, when you want to see the plan first;
84
+ - `--no-color`, or `NO_COLOR` in the environment, even empty (unset it when you mean to install);
85
+ - `CI` in the environment, so CI jobs always get a preview.
156
86
 
157
- ### How it fits inside Grok Build
87
+ Without `--yes`, a run with no terminal attached, such as a script, is a preview too.
158
88
 
159
- The installer puts files in the project's `.grok/` directory. `/litwork` provides a checklist for the current session; Grok Build owns execution and model selection. These are the main connections.
89
+ Uninstall with the same scope you installed with:
160
90
 
161
- ```mermaid
162
- flowchart TD
163
- I["litgrok install"] --> P["Project .grok/ files"]
164
- P --> S["skills · /litwork"]
165
- P --> R["rules · project guidance"]
166
- P --> H["hooks · /hooks-trust required"]
167
- S --> G["Grok Build session"]
168
- R --> G
169
- G -->|Trusted hook events| H
170
- H --> L["session-ledger · event chronology"]
171
- G -->|Check work · /lit-handoff| N["Project working notes and handoff"]
172
- N -.->|User supplies the path| G
91
+ ```bash
92
+ npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall
93
+ npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
173
94
  ```
174
95
 
175
- The hooks' `.grok/litgrok/session-ledger/` records event order. Judge success from the artifact and its checks. The user supplies the handoff path in the next session; having a record does not automatically resume work.
176
-
177
- [Checklist and hook boundaries](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/.grok/skills/litwork/SKILL.md) · [Handoff destinations](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/.grok/skills/lit-handoff/SKILL.md) · [Install details](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#install)
178
-
179
- ### Design and README production
180
-
181
- Use `/frontend-ui-ux <surface and outcome>` to build and inspect an authorized interface. A clear brief proceeds to working code; material ambiguity prompts a focused question. Review-only and plan-only requests remain read-only.
182
-
183
- Use the `/lit-diagram-drawer` skill for conceptual and technical diagrams. Its exact slash route is a candidate until verified in Grok Build; `/skills` is the discovery surface. Ordinary interfaces stay with `/frontend-ui-ux`, and measured-data plots stay with `/lit-scientific-visualization`.
184
-
185
- Use `lit-pptx` for slides and `lit-docx` for reports and Word documents. With bare `lit`, the project rule asks Grok Build to select one or both from the request wording. The deck defaults to AZURE-PRO with Pretendard; a Korean document defaults to korean-generic. The package includes the engines, templates, QA scripts, and pinned first-use cache installers. Slides require Node.js 20.9+; the DOCX workflow and base installer remain separate. Check the skill pages for commands and optional render tools. Skill selection is host guidance until observed in a Grok session.
186
-
187
- Use `/readme-studio <repository and outcome>` for a source-checked README, outlined Pretendard/Meslo typography, and portable cover/motion recipes. Check `/skills` after installation. Native image generation depends on the tools exposed in your Grok session; `IMAGE_GENERATION_UNAVAILABLE` permits an explicitly supplied background path. Fonts and renderers are task-local prerequisites. Local output is separate from live host and GitHub/npm acceptance. [README Studio](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/.grok/skills/readme-studio/SKILL.md).
188
-
189
- The cover is brand motion made with the LitFamily motion skill, not a recording of a Grok task execution.
190
-
191
- ## Skills at a glance
192
-
193
- All 38 skills, one row each. The route is the one the skill documents; `/skills` shows what your Grok Build session loaded. [Rename compatibility](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#skill-rename-compatibility) covers the one-release aliases; old slash routes are not guaranteed.
194
-
195
- <table>
196
- <tr><th>What it looks like</th><th>Skill</th><th>What you get</th></tr>
197
- <tr>
198
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/litwork.webp" width="240" alt="A bounded session checklist. LitGrok's hooks log each step to a local ledger." /></td>
199
- <td><code>litwork</code><br /><sub><code>/litwork &lt;goal&gt;</code></sub></td>
200
- <td>A bounded session checklist. LitGrok's hooks log each step to a local ledger.</td>
201
- </tr>
202
- <tr>
203
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-plan.webp" width="240" alt="A plan file with numbered rows that /start-work can run. Nothing is edited yet." /></td>
204
- <td><code>lit-plan</code><br /><sub><code>/lit-plan &lt;objective&gt;</code></sub></td>
205
- <td>A plan file with numbered rows that <code>/start-work</code> can run. Nothing is edited yet.</td>
206
- </tr>
207
- <tr>
208
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/start-work.webp" width="240" alt="Runs a plan row by row. A row is checked only after gates A to F pass." /></td>
209
- <td><code>start-work</code><br /><sub><code>/start-work &lt;plan path&gt;</code></sub></td>
210
- <td>Runs a plan row by row. A row is checked only after gates A to F pass.</td>
211
- </tr>
212
- <tr>
213
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/review-work.webp" width="240" alt="Six read-only review lanes rank what they find by evidence." /></td>
214
- <td><code>review-work</code><br /><sub><code>/review-work &lt;target&gt;</code></sub></td>
215
- <td>Six read-only review lanes rank what they find by evidence.</td>
216
- </tr>
217
- <tr>
218
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/litgoal.webp" width="240" alt="Shapes one checkable goal and hands you a native /goal line to run. LitGrok stores no goal state." /></td>
219
- <td><code>litgoal</code><br /><sub><code>/litgoal &lt;request&gt;</code></sub></td>
220
- <td>Shapes one checkable goal and hands you a native <code>/goal</code> line to run. LitGrok stores no goal state.</td>
221
- </tr>
222
- <tr>
223
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-recap.webp" width="240" alt="A short account with evidence, rebuilt from Grok Build session history." /></td>
224
- <td><code>lit-recap</code><br /><sub><code>/lit-recap</code></sub></td>
225
- <td>A short account with evidence, rebuilt from Grok Build session history.</td>
226
- </tr>
227
- <tr>
228
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-handoff.webp" width="240" alt="Type handoff for a resume file the next session can read. Secrets stay out." /></td>
229
- <td><code>lit-handoff</code><br /><sub><code>handoff</code> · <code>/lit-handoff</code></sub></td>
230
- <td>Type <code>handoff</code> for a resume file the next session can read. Secrets stay out.</td>
231
- </tr>
232
- <tr>
233
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/deep-interview.webp" width="240" alt="One question at a time, in a fixed order, until the request is clear enough to plan." /></td>
234
- <td><code>deep-interview</code><br /><sub><code>/deep-interview &lt;request&gt;</code></sub></td>
235
- <td>One question at a time, in a fixed order, until the request is clear enough to plan.</td>
236
- </tr>
237
- <tr>
238
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/litresearch.webp" width="240" alt="Bounded research with every claim traced to a source and no evidence overstated." /></td>
239
- <td><code>litresearch</code><br /><sub><code>/litresearch &lt;question&gt;</code></sub></td>
240
- <td>Bounded research with every claim traced to a source and no evidence overstated.</td>
241
- </tr>
242
- <tr>
243
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-crucible.webp" width="240" alt="Pressure-tests a brief before planning. Only the risks that survive critique reach the plan." /></td>
244
- <td><code>lit-crucible</code><br /><sub><code>/lit-crucible &lt;approach&gt;</code></sub></td>
245
- <td>Pressure-tests a brief before planning. Only the risks that survive critique reach the plan.</td>
246
- </tr>
247
- <tr>
248
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-init.webp" width="240" alt="Finds the project guidance that exists, flags conflicts and gaps, and proposes a layout. Nothing is written until you approve." /></td>
249
- <td><code>lit-init</code><br /><sub><code>/lit-init &lt;path&gt;</code></sub></td>
250
- <td>Finds the project guidance that exists, flags conflicts and gaps, and proposes a layout. Nothing is written until you approve.</td>
251
- </tr>
252
- <tr>
253
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-comprehend.webp" width="240" alt="An explainer page for agent-written work: intuition first, then the walkthrough, then a short quiz." /></td>
254
- <td><code>lit-comprehend</code><br /><sub><code>/lit-comprehend &lt;scope&gt;</code></sub></td>
255
- <td>An explainer page for agent-written work: intuition first, then the walkthrough, then a short quiz.</td>
256
- </tr>
257
- <tr>
258
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-humanizer.webp" width="240" alt="Rewrites stiff model prose in English or Korean. Facts and hedges stay; filler goes." /></td>
259
- <td><code>lit-humanizer</code><br /><sub><code>/lit-humanizer &lt;draft or file&gt;</code></sub></td>
260
- <td>Rewrites stiff model prose in English or Korean. Facts and hedges stay; filler goes.</td>
261
- </tr>
262
- <tr>
263
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-diagram-drawer.webp" width="240" alt="A checked, editable diagram for slides and documents, with PNG and Office-safe SVG exports." /></td>
264
- <td><code>lit-diagram-drawer</code><br /><sub><code>/lit-diagram-drawer &lt;brief&gt;</code></sub></td>
265
- <td>A checked, editable diagram for slides and documents, with PNG and Office-safe SVG exports.</td>
266
- </tr>
267
- <tr>
268
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-pptx.webp" width="240" alt="An editable PowerPoint deck with its Markdown source, AZURE-PRO and Pretendard by default. A QA gate runs on the file, and slides are inspected when LibreOffice is present." /></td>
269
- <td><code>lit-pptx</code><br /><sub><code>/lit-pptx &lt;presentation request&gt;</code></sub></td>
270
- <td>An editable PowerPoint deck with its Markdown source, AZURE-PRO and Pretendard by default. A QA gate runs on the file, and slides are inspected when LibreOffice is present.</td>
271
- </tr>
272
- <tr>
273
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-docx.webp" width="240" alt="A styled Word document with its Markdown source; Korean reports use korean-generic. Prose lint and a DOCX audit run, and pages are inspected when LibreOffice is present." /></td>
274
- <td><code>lit-docx</code><br /><sub><code>/lit-docx &lt;document request&gt;</code></sub></td>
275
- <td>A styled Word document with its Markdown source; Korean reports use korean-generic. Prose lint and a DOCX audit run, and pages are inspected when LibreOffice is present.</td>
276
- </tr>
277
- <tr>
278
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/frontend-ui-ux.webp" width="240" alt="Builds a working interface, then a probe renders it in seven views: four widths, dark, reduced motion and 200% zoom." /></td>
279
- <td><code>frontend-ui-ux</code><br /><sub><code>/frontend-ui-ux &lt;surface and outcome&gt;</code></sub></td>
280
- <td>Builds a working interface, then a probe renders it in seven views: four widths, dark, reduced motion and 200% zoom.</td>
281
- </tr>
282
- <tr>
283
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/readme-studio.webp" width="240" alt="A factual README with a cover, outlined type and local motion." /></td>
284
- <td><code>readme-studio</code><br /><sub><code>/readme-studio &lt;repository and outcome&gt;</code></sub></td>
285
- <td>A factual README with a cover, outlined type and local motion.</td>
286
- </tr>
287
- <tr>
288
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-typographic-motion.webp" width="240" alt="A finished short film from a treatment, rendered by LitGrok's own type engine or stage capture and checked by its QA gate." /></td>
289
- <td><code>lit-typographic-motion</code><br /><sub><code>/lit-typographic-motion &lt;request&gt;</code></sub></td>
290
- <td>A finished short film from a treatment, rendered by LitGrok's own type engine or stage capture and checked by its QA gate.</td>
291
- </tr>
292
- <tr>
293
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-scientific-visualization.webp" width="240" alt="A publication-ready figure and caption from verified data. The chart type follows the data." /></td>
294
- <td><code>lit-scientific-visualization</code><br /><sub><code>/lit-scientific-visualization</code></sub></td>
295
- <td>A publication-ready figure and caption from verified data. The chart type follows the data.</td>
296
- </tr>
297
- <tr>
298
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-team.webp" width="240" alt="Splits work into bounded task packets for Grok Build's built-in subagents. The parent integrates and verifies." /></td>
299
- <td><code>lit-team</code><br /><sub><code>/lit-team</code></sub></td>
300
- <td>Splits work into bounded task packets for Grok Build's built-in subagents. The parent integrates and verifies.</td>
301
- </tr>
302
- <tr>
303
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/autoresearch.webp" width="240" alt="A bounded research campaign: subagents, evidence gates, one synthesis." /></td>
304
- <td><code>autoresearch</code><br /><sub><code>/autoresearch &lt;mode&gt; &lt;objective&gt;</code></sub></td>
305
- <td>A bounded research campaign: subagents, evidence gates, one synthesis.</td>
306
- </tr>
307
- <tr>
308
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/autoconference.webp" width="240" alt="Subagent lanes deliberate on evidence, and the synthesis keeps disagreement." /></td>
309
- <td><code>autoconference</code><br /><sub><code>/autoconference &lt;mode&gt; &lt;topic&gt;</code></sub></td>
310
- <td>Subagent lanes deliberate on evidence, and the synthesis keeps disagreement.</td>
311
- </tr>
312
- <tr>
313
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/wikify.webp" width="240" alt="A local project knowledge map with sources, kept under .grok/." /></td>
314
- <td><code>wikify</code><br /><sub><code>/wikify &lt;mode&gt;</code></sub></td>
315
- <td>A local project knowledge map with sources, kept under <code>.grok/</code>.</td>
316
- </tr>
317
- <tr>
318
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/debugging.webp" width="240" alt="Reproduces the bug, tests at least three explanations, and fixes only the confirmed cause." /></td>
319
- <td><code>debugging</code><br /><sub><code>/debugging &lt;symptom&gt;</code></sub></td>
320
- <td>Reproduces the bug, tests at least three explanations, and fixes only the confirmed cause.</td>
321
- </tr>
322
- <tr>
323
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/refactor.webp" width="240" alt="Restructures code in an isolated worktree while tests pin its behavior." /></td>
324
- <td><code>refactor</code><br /><sub><code>/refactor &lt;target&gt;</code></sub></td>
325
- <td>Restructures code in an isolated worktree while tests pin its behavior.</td>
326
- </tr>
327
- <tr>
328
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-burnoff.webp" width="240" alt="Cleans AI-written bloat out of a change set after tests lock what it does." /></td>
329
- <td><code>lit-burnoff</code><br /><sub><code>/lit-burnoff &lt;scope&gt;</code></sub></td>
330
- <td>Cleans AI-written bloat out of a change set after tests lock what it does.</td>
331
- </tr>
332
- <tr>
333
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-burnoff-file.webp" width="240" alt="Cleans generated prose patterns out of one file and checks the diff." /></td>
334
- <td><code>lit-burnoff-file</code><br /><sub><code>/lit-burnoff-file &lt;path&gt;</code></sub></td>
335
- <td>Cleans generated prose patterns out of one file and checks the diff.</td>
336
- </tr>
337
- <tr>
338
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-code.webp" width="240" alt="Strict implementation rules: tests first, typed boundaries, small files." /></td>
339
- <td><code>lit-code</code><br /><sub><code>/lit-code &lt;task&gt;</code></sub></td>
340
- <td>Strict implementation rules: tests first, typed boundaries, small files.</td>
341
- </tr>
342
- <tr>
343
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lit-commit.webp" width="240" alt="Splits your changes into atomic commits in the repo's own style and leaves unrelated work alone." /></td>
344
- <td><code>lit-commit</code><br /><sub><code>/lit-commit &lt;operation&gt;</code></sub></td>
345
- <td>Splits your changes into atomic commits in the repo's own style and leaves unrelated work alone.</td>
346
- </tr>
347
- <tr>
348
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lsp.webp" width="240" alt="Turns on Grok Build's built-in LSP code-intel tool, which is off by default." /></td>
349
- <td><code>lsp</code><br /><sub><code>/lsp</code></sub></td>
350
- <td>Turns on Grok Build's built-in LSP code-intel tool, which is off by default.</td>
351
- </tr>
352
- <tr>
353
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/lsp-setup.webp" width="240" alt="Checks which language servers Grok Build can see and names the fallback when diagnostics are not exposed." /></td>
354
- <td><code>lsp-setup</code><br /><sub><code>/lsp-setup &lt;path or extension&gt;</code></sub></td>
355
- <td>Checks which language servers Grok Build can see and names the fallback when diagnostics are not exposed.</td>
356
- </tr>
357
- <tr>
358
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/structural-search.webp" width="240" alt="Traces code structure with search, read and optional LSP references. It does not invent an engine." /></td>
359
- <td><code>structural-search</code><br /><sub><code>/structural-search &lt;pattern&gt;</code></sub></td>
360
- <td>Traces code structure with search, read and optional LSP references. It does not invent an engine.</td>
361
- </tr>
362
- <tr>
363
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/visual-qa.webp" width="240" alt="A screenshot-backed review of a rendered interface." /></td>
364
- <td><code>visual-qa</code><br /><sub><code>/visual-qa &lt;target&gt;</code></sub></td>
365
- <td>A screenshot-backed review of a rendered interface.</td>
366
- </tr>
367
- <tr>
368
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/browser-drive.webp" width="240" alt="Drives a real page after verifying the browser driver. If there is none, it says so." /></td>
369
- <td><code>browser-drive</code><br /><sub><code>/browser-drive &lt;url&gt;</code></sub></td>
370
- <td>Drives a real page after verifying the browser driver. If there is none, it says so.</td>
371
- </tr>
372
- <tr>
373
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/comment-checker.webp" width="240" alt="Reviews the comments an edit added: reasons stay, narration goes." /></td>
374
- <td><code>comment-checker</code><br /><sub><code>/comment-checker &lt;path&gt;</code></sub></td>
375
- <td>Reviews the comments an edit added: reasons stay, narration goes.</td>
376
- </tr>
377
- <tr>
378
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/rules.webp" width="240" alt="Explains which guidance Grok Build loads for this folder, in what order, and whether hooks are trusted." /></td>
379
- <td><code>rules</code><br /><sub><code>/rules</code></sub></td>
380
- <td>Explains which guidance Grok Build loads for this folder, in what order, and whether hooks are trusted.</td>
381
- </tr>
382
- <tr>
383
- <td><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/assets/skills/litgrok.webp" width="240" alt="Explains what the LitGrok package installs, and what it does not." /></td>
384
- <td><code>litgrok</code><br /><sub><code>/litgrok</code></sub></td>
385
- <td>Explains what the LitGrok package installs, and what it does not.</td>
386
- </tr>
387
- </table>
388
-
389
- ## Command and hook table
390
-
391
- ### Prompt or route
392
-
393
- Grok Build uses the explicit `/litwork` route for a bounded task. It owns model execution; LitGrok leaves skills, rules, and checked next steps in the project.
394
-
395
- | Prompt or route | Effect |
396
- | --- | --- |
397
- | `/litwork` | Start the shipped work checklist in Grok Build. |
398
- | `handoff` or `/lit-handoff` | Carry the checked result and next step into another session. |
399
- | `/lit-plan` | Write a plan with concrete checks. |
400
- | `/start-work <approved-plan>` | Execute an approved plan. |
401
- | `/review-work` | Review a change and its evidence. |
402
- | `/litresearch` | Run bounded, source-traceable research without overstating evidence. |
403
-
404
- ### Project hooks
405
-
406
- | Surface | Registration and boundary |
407
- | --- | --- |
408
- | Project hooks | Eleven registrations are declared in [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/hooks/hooks.json). They require a trusted Git root and `/hooks-trust`; a plain folder may load skills and rules without hooks. |
409
-
410
- ## Troubleshooting
411
-
412
- ### Project hooks
413
-
414
- Project hooks need a trusted Git project root in Grok Build. A plain folder can still load the installed skills and rules while hooks remain unavailable. For a new disposable project, run `git init` yourself before trusting it; for an existing repository, open Grok Build from its actual root. The installer never runs `git init` or changes trust. In the observed Grok Build 1.0.23 host, `grok --trust inspect --json` accepted the trust-and-inspect route even though `--trust` was omitted from `grok --help`; this is version-specific behavior.
415
-
416
- ### Install preview
417
-
418
- If `CI` or `NO_COLOR` is set, even to an empty value, installation is a no-write preview. So is `--no-color`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, installation proceeds without a TTY as long as none of the above apply. Check that the installer reports actual writes before continuing.
419
-
420
- **Status row missing:** the persistent row is optional and uses user or administrator configuration; project and plugin configuration are not read for this setting. See the [status-line reference](https://docs.x.ai/build/features/status-line).
96
+ The installer never runs `git init`, trusts hooks, signs in or picks a model for you; those steps, and your API keys, stay with you in Grok Build. The package tests check the files we ship. To see what your own session loaded, open it from the repository root and check `/hooks` and `grok inspect --json`.
421
97
 
422
- For host limits and current verification steps, see the [operational reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#verify).
98
+ ## If something does not work
423
99
 
424
- ## Links
100
+ - **No hooks:** Grok runs hooks only from a trusted Git project root. For a new project, run `git init` yourself, then trust it; for an existing one, open Grok Build from its real root.
101
+ - **Nothing was written:** the output says `no files written` and names the reason (`DRY RUN`, `NO COLOR` or `NON-INTERACTIVE`). Fix that case from the list above and run the install again.
102
+ - **No status row:** Grok reads the row from user or administrator configuration, not from a project or plugin, so add it with `install --user --status-line`.
425
103
 
426
- - [Operational reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md): installation, hooks, terminal output, payload checks, and source provenance.
427
- - [Project rule](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/.grok/rules/00-litgrok.md) and [skill catalog](https://github.com/wjgoarxiv/litgrok/tree/main/.grok/skills).
428
- - [Changelog](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/CHANGELOG.md) and [license](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/LICENSE).
104
+ ---
429
105
 
430
- - [Contributing](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/CONTRIBUTING.md), [security](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/SECURITY.md), [conduct](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/CODE_OF_CONDUCT.md), and [support](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/SUPPORT.md).
431
- - [Privacy and local data](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/privacy.md); [migration from the old npm name](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.9/docs/reference.md#npm-package-migration).
106
+ **[Full guide, skills gallery and troubleshooting on GitHub →](https://github.com/wjgoarxiv/litgrok#readme)**
432
107
 
433
- ### LITFAMILY
108
+ [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/reference.md) · [Changelog](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/CHANGELOG.md) · [Privacy](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/docs/privacy.md) · [MIT license](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.11/LICENSE)
434
109
 
435
- The motion cover at the top shows five armored robots representing the products. Each works independently in its own host; they do not need to be installed together or connected to one another.
110
+ The cover is brand motion made with the LitFamily motion skill: animated artwork, with no Grok session recorded in it.