@g3nomaly/g3n-skills 0.1.6 → 0.1.8

package/.claude-plugin/marketplace.json

@@ -17,14 +17,24 @@
     {
       "name": "coding",
       "source": "./skills/coding",
-      "description": "How to write, check and document code, per language, query a repository with analyze, and keep its glossary.",
+      "description": "How to write, check and document code, per language, and keep its glossary.",
       "skills": [
         "./code",
         "./document",
-        "./analyze",
         "./vocabulary"
       ]
     },
+    {
+      "name": "g3n",
+      "source": "./skills/g3n",
+      "description": "The g3n tools: query a repository with analyze, and install skills, mods and components with their installers.",
+      "skills": [
+        "./analyze",
+        "./g3n-skills",
+        "./g3n-mods",
+        "./g3n-ui"
+      ]
+    },
     {
       "name": "grilling",
       "source": "./skills/grilling",

package/README.md

@@ -1,6 +1,6 @@
 # @g3nomaly/g3n-skills
 
-The g3n skills for Claude Code and Codex: 38 skills in 9 groups. This package holds the skills and has no CLI. Install them with [`@g3nomaly/skills`](https://www.npmjs.com/package/@g3nomaly/skills), which reads this package as its built-in source, or read it as a Claude Code plugin marketplace.
+The g3n skills for Claude Code and Codex: 40 skills in 10 groups. This package holds the skills and has no CLI. Install them with [`@g3nomaly/skills`](https://www.npmjs.com/package/@g3nomaly/skills), which reads this package as its built-in source, or read it as a Claude Code plugin marketplace.
 
 Some skills carry their own hooks. A hook is a TypeScript file in the skill's `hooks/` folder, and the agent runs it with `bun`. The task-manager hooks keep plans, phases and tasks as Markdown files that the agent reaches only through those hooks. The workflow hooks decide when a step of a phase is finished.
 
@@ -46,46 +46,49 @@ There is one known gap. Claude Code caches each plugin in its own folder, so the
 
 Skills marked _manual_ run only when you type their command, such as `/grill-me`. The agent loads the others when the task calls for them.
 
-| Group | Skill | What it does |
-|---|---|---|
-| `agent` | `bootstrap` | Session start checks (read `CLAUDE.md`, compare the file tree, state the branch) and the agent's boundaries |
-| `agent` | `worktrees` | Work in a git worktree on a feature branch and land it on the home branch as clean commits on top of `main`, ready to merge one commit at a time |
-| `agent` | `commit` | Commit messages with no attribution trailers, personal data or AI references, checked by a hook before each commit |
-| `coding` | `code` | Rules for writing and checking code, with a toolchain reference per language |
-| `coding` | `document` | Docstrings and comments for functions and classes, and where the reasons behind code go |
-| `coding` | `analyze` | Query a repository's model with `g3n-analyze` and rebuild its documentation site in `analyze_out/` |
-| `coding` | `vocabulary` | One word per concept, recorded in `docs/glossary.md`, so names don't drift between sessions |
-| `grilling` | `grilling` | Interview the user relentlessly to stress-test a plan, decision or idea |
-| `grilling` | `grill-me` | _Manual._ Starts a `/grilling` session |
-| `grilling` | `grill-with-docs` | _Manual._ A grilling session that writes ADRs and a glossary as it goes |
-| `grilling` | `domain-modeling` | Pin down a project's terms and record its architectural decisions |
-| `speech` | `emphasise` | What bold, italics and backticks mean in Markdown that an agent reads |
-| `speech` | `unslop` | Cut AI tells from any writing |
-| `speech` | `plain-language` | Write text readers can find, understand and use on the first read, following ISO 24495-1 |
-| `speech` | `no-questions` | Replies end without questions or offers; a Stop hook refuses a reply that asks one |
-| `task-manager` | `task-manager` | Query plans, phases and tasks and change their status through hooks |
-| `task-manager` | `decisions` | Record and look up a plan's decisions as numbered files inside the plan |
-| `teach` | `teaching` | The teaching principles every teach skill follows: real work, causality, mental models and guidance per concept |
-| `teach` | `learn-by-building` | Learn a subject while completing a real task on the user's own system |
-| `teach` | `explain` | Explain existing material through its purpose, mental model, flow and failure modes |
-| `teach` | `deep-dive` | Trace the layers beneath an abstraction, only as deep as the question needs |
-| `teach` | `architecture` | Reason from forces and options to an architecture decision and its consequences |
-| `teach` | `guided-debugging` | Find a failure's root cause through hypotheses and small experiments, teaching the method |
-| `teach` | `guided-review` | Review work by consequence and explain the principle behind each finding |
-| `using-hooks` | `hook-pre-tool-use` | _Manual._ Writing a `PreToolUse` hook, which can allow, deny or escalate a tool call |
-| `using-hooks` | `hook-post-tool-use` | _Manual._ Writing a `PostToolUse` hook, which reacts to a finished tool call |
-| `using-hooks` | `hook-stop` | _Manual._ Writing a `Stop` hook, which can refuse to let the agent end its turn |
-| `using-hooks` | `hook-user-prompt-submit` | _Manual._ Writing a `UserPromptSubmit` hook, which can add context to a prompt or reject it |
-| `workflow` | `run` | Work one phase through plan, execute, review and sync, one fresh agent per step |
-| `workflow` | `plan` | Turn a phase into task files an agent can execute without asking anything |
-| `workflow` | `execute` | Carry out a phase's tasks, each in its own worktree, and hand each one to review |
-| `workflow` | `review` | Check each in-review task against its requirements, then complete it or send it back |
-| `workflow` | `sync` | Merge a reviewed phase's branches, remove its worktrees, record its decisions and terms, and close it |
-| `workflow` | `orchestrator` | _Manual._ Run a whole plan phase by phase, starting each phase once the phases it depends on are done |
-| `workflow` | `worktree` | Set up, merge and remove the git worktrees tasks are worked in, one per task |
-| `writing` | `writing-great-hooks` | Add, change or debug a hook script or a lifecycle hook |
-| `writing` | `writing-great-skills` | Write or edit a skill, its `SKILL.md`, references and hooks |
-| `writing` | `writing-great-tasks` | Write a task that doesn't leave its executor guessing about scope |
+| Group          | Skill                     | What it does                                                                                                                                     |
+| -------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `agent`        | `bootstrap`               | Session start checks (read `CLAUDE.md`, compare the file tree, state the branch) and the agent's boundaries                                      |
+| `agent`        | `worktrees`               | Work in a git worktree on a feature branch and land it on the home branch as clean commits on top of `main`, ready to merge one commit at a time |
+| `agent`        | `commit`                  | Commit messages with no attribution trailers, personal data or AI references, checked by a hook before each commit                               |
+| `coding`       | `code`                    | Rules for writing and checking code, with a toolchain reference per language                                                                     |
+| `coding`       | `document`                | Docstrings and comments for functions and classes, and where the reasons behind code go                                                          |
+| `coding`       | `vocabulary`              | One word per concept, recorded in `docs/glossary.md`, so names don't drift between sessions                                                      |
+| `g3n`          | `analyze`                 | Query a repository's model with `g3n-analyze` and rebuild its documentation site in `analyze_out/`                                               |
+| `g3n`          | `g3n-skills`              | Install, update and remove skills with `@g3nomaly/skills`, never by copying folders, and audit what they add before it runs                      |
+| `g3n`          | `g3n-mods`                | Install, update and remove Claude Code mods with `@g3nomaly/mods`, never by copying folders, after auditing the mod in its source                |
+| `g3n`          | `g3n-ui`                  | Install, update and remove React components with `@g3nomaly/ui`, and audit them before they run or their packages install                        |
+| `grilling`     | `grilling`                | Interview the user relentlessly to stress-test a plan, decision or idea                                                                          |
+| `grilling`     | `grill-me`                | _Manual._ Starts a `/grilling` session                                                                                                           |
+| `grilling`     | `grill-with-docs`         | _Manual._ A grilling session that writes ADRs and a glossary as it goes                                                                          |
+| `grilling`     | `domain-modeling`         | Pin down a project's terms and record its architectural decisions                                                                                |
+| `speech`       | `emphasise`               | What bold, italics and backticks mean in Markdown that an agent reads                                                                            |
+| `speech`       | `unslop`                  | Cut AI tells from any writing                                                                                                                    |
+| `speech`       | `plain-language`          | Write text readers can find, understand and use on the first read, following ISO 24495-1                                                         |
+| `speech`       | `no-questions`            | Replies end without questions or offers; a Stop hook refuses a reply that asks one                                                               |
+| `task-manager` | `task-manager`            | Query plans, phases and tasks and change their status through hooks                                                                              |
+| `task-manager` | `decisions`               | Record and look up a plan's decisions as numbered files inside the plan                                                                          |
+| `teach`        | `teaching`                | The teaching principles every teach skill follows: real work, causality, mental models and guidance per concept                                  |
+| `teach`        | `learn-by-building`       | Learn a subject while completing a real task on the user's own system                                                                            |
+| `teach`        | `explain`                 | Explain existing material through its purpose, mental model, flow and failure modes                                                              |
+| `teach`        | `deep-dive`               | Trace the layers beneath an abstraction, only as deep as the question needs                                                                      |
+| `teach`        | `architecture`            | Reason from forces and options to an architecture decision and its consequences                                                                  |
+| `teach`        | `guided-debugging`        | Find a failure's root cause through hypotheses and small experiments, teaching the method                                                        |
+| `teach`        | `guided-review`           | Review work by consequence and explain the principle behind each finding                                                                         |
+| `using-hooks`  | `hook-pre-tool-use`       | _Manual._ Writing a `PreToolUse` hook, which can allow, deny or escalate a tool call                                                             |
+| `using-hooks`  | `hook-post-tool-use`      | _Manual._ Writing a `PostToolUse` hook, which reacts to a finished tool call                                                                     |
+| `using-hooks`  | `hook-stop`               | _Manual._ Writing a `Stop` hook, which can refuse to let the agent end its turn                                                                  |
+| `using-hooks`  | `hook-user-prompt-submit` | _Manual._ Writing a `UserPromptSubmit` hook, which can add context to a prompt or reject it                                                      |
+| `workflow`     | `run`                     | Work one phase through plan, execute, review and sync, one fresh agent per step                                                                  |
+| `workflow`     | `plan`                    | Turn a phase into task files an agent can execute without asking anything                                                                        |
+| `workflow`     | `execute`                 | Carry out a phase's tasks, each in its own worktree, and hand each one to review                                                                 |
+| `workflow`     | `review`                  | Check each in-review task against its requirements, then complete it or send it back                                                             |
+| `workflow`     | `sync`                    | Merge a reviewed phase's branches, remove its worktrees, record its decisions and terms, and close it                                            |
+| `workflow`     | `orchestrator`            | _Manual._ Run a whole plan phase by phase, starting each phase once the phases it depends on are done                                            |
+| `workflow`     | `worktree`                | Set up, merge and remove the git worktrees tasks are worked in, one per task                                                                     |
+| `writing`      | `writing-great-hooks`     | Add, change or debug a hook script or a lifecycle hook                                                                                           |
+| `writing`      | `writing-great-skills`    | Write or edit a skill, its `SKILL.md`, references and hooks                                                                                      |
+| `writing`      | `writing-great-tasks`     | Write a task that doesn't leave its executor guessing about scope                                                                                |
 
 The `commit` hook refuses your git `user.name` and `user.email`. To keep another name out of messages without writing it into the repository, add it to your global git config: `git config --global --add g3n.privateName "<name>"`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@g3nomaly/g3n-skills",
-  "version": "0.1.6",
+  "version": "0.1.8",
   "description": "The g3n skills, each with its own hooks: a skill source for @g3nomaly/skills and a Claude Code plugin marketplace.",
   "type": "module",
   "files": [
@@ -15,7 +15,7 @@
     "test:clean": "CLEAN_TMP=1 bun test"
   },
   "devDependencies": {
-    "@g3nomaly/core": "^0.3.5",
+    "@g3nomaly/core": "^0.3.7",
     "@types/bun": "^1.4.0",
     "typescript": "~7.0.2",
     "zod": "^4.4.3"

package/skills/coding/.claude-plugin/plugin.json

@@ -1,7 +1,11 @@
 {
   "name": "coding",
-  "description": "How to write, check and document code, per language, query a repository with analyze, and keep its glossary.",
-  "version": "0.1.0",
+  "description": "How to write, check and document code, per language, and keep its glossary.",
+  "version": "0.1.7",
   "license": "UNLICENSED",
-  "skills": ["./code", "./document", "./analyze", "./vocabulary"]
+  "skills": [
+    "./code",
+    "./document",
+    "./vocabulary"
+  ]
 }

package/skills/coding/code/SKILL.md

@@ -23,9 +23,9 @@ Apply SOLID principles, DRY, and KISS. Use descriptive names for variables, func
 
 Each language has a reference that names its toolchain, its commands and its rules.
 
-| Language | Reference | Files |
-|---|---|---|
-| TypeScript | [`references/typescript.md`](references/typescript.md) | `.ts` `.tsx` |
-| Python | [`references/python.md`](references/python.md) | `.py` |
-| C++ | [`references/cpp.md`](references/cpp.md) | `.cpp` `.cc` `.hpp` `.h` |
-| Rust | [`references/rust.md`](references/rust.md) | `.rs` |
+| Language   | Reference                                              | Files                    |
+| ---------- | ------------------------------------------------------ | ------------------------ |
+| TypeScript | [`references/typescript.md`](references/typescript.md) | `.ts` `.tsx`             |
+| Python     | [`references/python.md`](references/python.md)         | `.py`                    |
+| C++        | [`references/cpp.md`](references/cpp.md)               | `.cpp` `.cc` `.hpp` `.h` |
+| Rust       | [`references/rust.md`](references/rust.md)             | `.rs`                    |

package/skills/coding/code/references/cpp.md

@@ -2,21 +2,21 @@
 
 CMake configures and builds with clang. vcpkg supplies dependencies in manifest mode, from `vcpkg.json`. Run commands from inside the project directory, where `CMakeLists.txt` lives.
 
-| Task | Command |
-|---|---|
-| Configure | `cmake --preset <preset>` when `CMakePresets.json` exists, otherwise `cmake -S . -B build -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_TOOLCHAIN_FILE="$VCPKG_ROOT/scripts/buildsystems/vcpkg.cmake" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON` |
-| Add a dependency | `vcpkg add port <pkg>`, then `find_package` and `target_link_libraries` in `CMakeLists.txt` |
-| Build | `cmake --build build` |
-| Run | the target's binary under `build/` |
+| Task             | Command                                                                                                                                                                                                                          |
+| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Configure        | `cmake --preset <preset>` when `CMakePresets.json` exists, otherwise `cmake -S . -B build -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_TOOLCHAIN_FILE="$VCPKG_ROOT/scripts/buildsystems/vcpkg.cmake" -DCMAKE_EXPORT_COMPILE_COMMANDS=ON` |
+| Add a dependency | `vcpkg add port <pkg>`, then `find_package` and `target_link_libraries` in `CMakeLists.txt`                                                                                                                                      |
+| Build            | `cmake --build build`                                                                                                                                                                                                            |
+| Run              | the target's binary under `build/`                                                                                                                                                                                               |
 
 ## Checks
 
-| Check | Command | When |
-|---|---|---|
-| Build | `cmake --build build` | always |
-| Format | `clang-format --dry-run --Werror <files>`, or `clang-format -i <files>` to fix | always |
-| Lint | see [clang-tidy](#clang-tidy) | always |
-| Test | `ctest --test-dir build --output-on-failure` | when the project has tests |
+| Check  | Command                                                                        | When                       |
+| ------ | ------------------------------------------------------------------------------ | -------------------------- |
+| Build  | `cmake --build build`                                                          | always                     |
+| Format | `clang-format --dry-run --Werror <files>`, or `clang-format -i <files>` to fix | always                     |
+| Lint   | see [clang-tidy](#clang-tidy)                                                  | always                     |
+| Test   | `ctest --test-dir build --output-on-failure`                                   | when the project has tests |
 
 ## clang-tidy
 

package/skills/coding/code/references/python.md

@@ -2,22 +2,22 @@
 
 uv handles install, run and build. Run commands from inside the project directory, where `pyproject.toml` lives.
 
-| Task | Command |
-|---|---|
-| Install | `uv sync` |
+| Task             | Command                                         |
+| ---------------- | ----------------------------------------------- |
+| Install          | `uv sync`                                       |
 | Add a dependency | `uv add <pkg>`, or `uv add --dev <pkg>` for dev |
-| Run a file | `uv run <file>` |
-| Run a tool once | `uvx <tool>` |
-| Build | `uv build` |
+| Run a file       | `uv run <file>`                                 |
+| Run a tool once  | `uvx <tool>`                                    |
+| Build            | `uv build`                                      |
 
 ## Checks
 
-| Check | Command | When |
-|---|---|---|
-| Typecheck | `uv run ty check` | always |
-| Lint | `uv run ruff check --fix`, then fix what remains by hand | always |
-| Format | `uv run ruff format --check`, or `uv run ruff format` to fix | always |
-| Test | `uv run pytest` | when the project has tests |
+| Check     | Command                                                      | When                       |
+| --------- | ------------------------------------------------------------ | -------------------------- |
+| Typecheck | `uv run ty check`                                            | always                     |
+| Lint      | `uv run ruff check --fix`, then fix what remains by hand     | always                     |
+| Format    | `uv run ruff format --check`, or `uv run ruff format` to fix | always                     |
+| Test      | `uv run pytest`                                              | when the project has tests |
 
 ## Rules
 

package/skills/coding/code/references/rust.md

@@ -2,21 +2,21 @@
 
 Cargo handles install, run, test and build. Run commands from inside the crate or workspace directory, where `Cargo.toml` lives.
 
-| Task | Command |
-|---|---|
-| Install | `cargo fetch`, or let `cargo build` fetch |
+| Task             | Command                                                   |
+| ---------------- | --------------------------------------------------------- |
+| Install          | `cargo fetch`, or let `cargo build` fetch                 |
 | Add a dependency | `cargo add <crate>`, or `cargo add --dev <crate>` for dev |
-| Run | `cargo run` |
-| Build | `cargo build`, or `cargo build --release` |
+| Run              | `cargo run`                                               |
+| Build            | `cargo build`, or `cargo build --release`                 |
 
 ## Checks
 
-| Check | Command | When |
-|---|---|---|
-| Typecheck | `cargo check` | always |
-| Lint | `cargo clippy --all-targets -- -D warnings` | always |
-| Format | `cargo fmt --check`, or `cargo fmt` to fix | always |
-| Test | `cargo test` | when the crate has tests |
+| Check     | Command                                     | When                     |
+| --------- | ------------------------------------------- | ------------------------ |
+| Typecheck | `cargo check`                               | always                   |
+| Lint      | `cargo clippy --all-targets -- -D warnings` | always                   |
+| Format    | `cargo fmt --check`, or `cargo fmt` to fix  | always                   |
+| Test      | `cargo test`                                | when the crate has tests |
 
 ## Rules
 

package/skills/coding/code/references/typescript.md

@@ -2,22 +2,22 @@
 
 Bun handles install, run, test and build. Run commands from inside the package directory.
 
-| Task | Command |
-|---|---|
-| Install | `bun install` |
+| Task             | Command                                        |
+| ---------------- | ---------------------------------------------- |
+| Install          | `bun install`                                  |
 | Add a dependency | `bun add <pkg>`, or `bun add -d <pkg>` for dev |
-| Run a file | `bun <file>` |
-| Run a script | `bun run <script>` |
-| Run a tool once | `bunx <pkg>` |
-| Build | `bun run build` |
+| Run a file       | `bun <file>`                                   |
+| Run a script     | `bun run <script>`                             |
+| Run a tool once  | `bunx <pkg>`                                   |
+| Build            | `bun run build`                                |
 
 ## Checks
 
-| Check | Command | When |
-|---|---|---|
-| Typecheck | `bun run typecheck` | always |
-| Lint | `bun run lint` | when the package defines it |
-| Test | `bun test` | when the package has tests |
+| Check     | Command             | When                        |
+| --------- | ------------------- | --------------------------- |
+| Typecheck | `bun run typecheck` | always                      |
+| Lint      | `bun run lint`      | when the package defines it |
+| Test      | `bun test`          | when the package has tests  |
 
 ## Rules
 

package/skills/coding/document/SKILL.md

@@ -14,7 +14,7 @@ Line 1 of every file is a comment with its relative path. No file-level docstrin
 
 ## Docstrings
 
-Functions, classes and other type declarations get a docstring; the language reference lists which. **A property, field or enum member is a tag in the docstring of its owner**, not a docstring of its own. 
+Functions, classes and other type declarations get a docstring; the language reference lists which. **A property, field or enum member is a tag in the docstring of its owner**, not a docstring of its own.
 
 A _tag_ is a marked line in a docstring that documents one thing, such as `@param` in TypeScript.
 

package/skills/coding/document/references/cpp.md

@@ -77,12 +77,14 @@ struct Resolution {
     std::vector<std::string> unknown; ///< Requests no source offers.
 };
 ```
+
 A trailing `///<` docstring on a member. Members go in the struct's docstring as `@property` tags.
 
 ```cpp
 // Retrieves a user by id.
 std::optional<User> get_user(std::int64_t user_id);
 ```
+
 A plain `//` comment in place of a docstring. Doxygen and clangd only read `/** */`.
 
 ```cpp
@@ -93,6 +95,7 @@ A plain `//` comment in place of a docstring. Doxygen and clangd only read `/**
  */
 [[nodiscard]] Tree parse_file(const std::filesystem::path& path);
 ```
+
 The exception is prose inside `@return`, with no type. Each exception gets its own `@throws` tag, as in `parse_file` above.
 
 ```cpp
@@ -102,4 +105,5 @@ The exception is prose inside `@return`, with no type. Each exception gets its o
  * @param preferred Source to take a key from when several offer it.
  */
 ```
+
 More than one line without `@brief`. It opens with `@brief Resolves the dependencies...`.

package/skills/coding/document/references/python.md

@@ -77,6 +77,7 @@ class Resolution:
     entries: dict[str, SourceOffer]
     """Resolved entries by key."""
 ```
+
 A docstring on a field. Fields go in the class docstring under `Attributes:`.
 
 ```python
@@ -84,6 +85,7 @@ def get_user(user_id: int) -> User | None:
     # Looks the user up by surrogate key.
     """Retrieves a user by id."""
 ```
+
 A comment that says what a tag can say. It goes under `Args:`.
 
 ```python
@@ -92,4 +94,5 @@ def matches(request: EntryRequest, offers: Sequence[SourceOffer]) -> Match:
     Finds the entries one request names.
     """
 ```
+
 The summary starts on line 2, and the custom types `EntryRequest`, `SourceOffer` and `Match` have no `Args:` or `Returns:` entry.

package/skills/coding/document/references/rust.md

@@ -5,11 +5,11 @@ Rustdoc: a `/** */` block directly above the item, written in Markdown. Never `/
 - **Line 1**: `// src/users/store.rs`, the relative path. No `//!` or `/*! */` module or crate docs.
 - **Declarations with a docstring**: functions, methods, structs, enums, traits and type aliases.
 - **Summary**: `/** Adds two numbers. */` on one line. The first line is the `@brief`: a longer block opens with the summary, then a blank ` *` line.
-- **Tags**: Markdown sections `# Arguments`, `# Returns`, `# Errors`, `# Panics` and `# Examples`. Arguments are a list of `` * `name` - text ``.
+- **Tags**: Markdown sections `# Arguments`, `# Returns`, `# Errors`, `# Panics` and `# Examples`. Arguments are a list of ``* `name` - text``.
 - **Fields and variants**: Rust has no field tag, so this is the one exception to the owner rule. Each struct field and enum variant gets its own one-line `/** */`. Rustdoc and analyze both read it from there.
 - **Examples**: a fenced block under `# Examples`. `cargo test` compiles and runs it, so it must build. Setup lines start with `# `, which hides them from the rendered docs.
 
-```rust
+````rust
 /** Adds two numbers. */
 pub fn add(a: i32, b: i32) -> i32 {
     a + b
@@ -69,7 +69,7 @@ pub struct Resolution {
     /** Why an entry nobody named is in the set, e.g. `("vocabulary", "dep of plan")`. */
     pub notes: HashMap<String, String>,
 }
-```
+````
 
 `harbor` in the example stands for the crate's own name. Doctests use the crate from outside, so `crate::` does not work there.
 
@@ -83,6 +83,7 @@ Each one next to what is wrong with it. The examples above show the fix.
 /// Adds two numbers.
 pub fn add(a: i32, b: i32) -> i32
 ```
+
 A `///` comment. Use `/** Adds two numbers. */`.
 
 ```rust
@@ -97,15 +98,17 @@ pub struct Resolution {
     pub entries: HashMap<String, SourceOffer>,
 }
 ```
+
 Fields listed in the struct's docstring. Neither rustdoc nor analyze reads them there. The `/** */` goes on the field.
 
 ```rust
 /** Parses a file. */
 pub fn parse_file(path: &Path) -> Result<Tree, FileValidationError>
 ```
+
 Returns `Result` with no `# Errors` section.
 
-```rust
+````rust
 /**
  * # Examples
  *
@@ -113,10 +116,12 @@ Returns `Result` with no `# Errors` section.
  * let error = FileValidationError::new(path, vec![issue]);
  * ```
  */
-```
+````
+
 `path` and `issue` are never defined and the type is never imported, so `cargo test` fails on it.
 
 ```rust
 /*! User storage. */
 ```
+
 A module docstring. Line 1 is the path comment, and the items carry the docs.

package/skills/coding/document/references/typescript.md

@@ -14,7 +14,7 @@ export function add(a: number, b: number): number {
 
 /**
  * @brief Retrieves a user by id.
- * 
+ *
  * @param userId - Surrogate key from the `users` table, not the auth provider's id.
  * @returns Custom User class used by the authentication service, or `undefined` when no row matches.
  */
@@ -72,12 +72,14 @@ Each one next to what is wrong with it. The examples above show the fix.
 /** Holds the installed skills read from `skills.json`. */
 export class SkillRegistry {}
 ```
+
 Too thin. It leaves out what the class holds, who creates and consumes it, and how to make one.
 
 ```ts
 /** @param file - Path of the file that was read. */
 constructor(file: string, issues: FileValidationIssue[])
 ```
+
 `file` doesn't say absolute or relative. `issues` is missing, while its type hides what goes in it.
 
 ```ts
@@ -86,6 +88,7 @@ constructor(file: string, issues: FileValidationIssue[])
  *   as it reads in the file, such as `phases.0.status`, or `(whole file)`.
  */
 ```
+
 Prose about the type. One example value shows it faster: `` e.g. `{ field: "phases.0.status", message: "is required" }` ``.
 
 ```ts
@@ -95,14 +98,19 @@ Prose about the type. One example value shows it faster: `` e.g. `{ field: "phas
  * @param b - The second number.
  * @returns The sum.
  */
-export function add(a: number, b: number): number
+export function add(a: number, b: number): number;
 ```
+
 The tags repeat the signature. The summary line is enough.
 
 ```ts
 /** Entries one request names. */
-function matchRequest(request: EntryRequest, offers: readonly SourceOffer[]): Match
+function matchRequest(
+  request: EntryRequest,
+  offers: readonly SourceOffer[],
+): Match;
 ```
+
 A noun phrase that names the result, and no tags. The summary says what the function does: _Finds the entries one request names_. `EntryRequest`, `SourceOffer` and `Match` are custom types, so `request`, `offers` and the return value each need a tag.
 
 ```ts
@@ -114,6 +122,7 @@ export interface Resolution {
   unknown: string[];
 }
 ```
+
 A docstring on each property. Properties go in the interface's docstring as `@property` tags, as in `Resolution` above.
 
 ```ts
@@ -123,9 +132,11 @@ A docstring on each property. Properties go in the interface's docstring as `@pr
  * @param preferred - Source to take a key from when several offer it.
  */
 ```
+
 More than one line without `@brief`. It opens with `@brief Resolves the dependencies...`.
 
 ```ts
 /** Loads a user by id. Uses a surrogate key because auth ids changed format in 2024. */
 ```
+
 The _why_ belongs in `decisions.md`. The docstring says what and how.

package/skills/g3n/.claude-plugin/plugin.json

@@ -0,0 +1,12 @@
+{
+  "name": "g3n",
+  "description": "The g3n tools: query a repository with analyze, and install skills, mods and components with their installers.",
+  "version": "0.1.8",
+  "license": "UNLICENSED",
+  "skills": [
+    "./analyze",
+    "./g3n-skills",
+    "./g3n-mods",
+    "./g3n-ui"
+  ]
+}

package/skills/{coding → g3n}/analyze/SKILL.md

@@ -8,21 +8,26 @@ disable-model-invocation: false
 
 ## Query
 
-1. **Find** the node: `search <words>`. It matches names first, then meaning. Done when a hit's `id` names what you want.
-2. **Read** it: `show <id>`. Text, signature, parameters, fields and every edge.
-3. **Follow** its edges: `refs <id>`. Add `--incoming` for what uses it, `--outgoing` for what it uses, `--edge <kind>` to keep one kind, such as `type` or `affects`.
-4. **Narrow** any of these with `--kind`, `--section` and `-n`. `list --kind <kind>` lists every node of a kind.
+1. **Find** the node: `search <words>`. It matches names first, then meaning, and lists the hits of each section under its own heading, at most 5 each. Short keywords find code best; add `--section code` to search the code only. Done when a hit's `id` names what you want.
+2. **Read** it: `show <id>`. Text, signature, parameters, fields and every edge. `file:` gives the lines it spans, such as `src/app.ts:29-45`, to read just that range.
+3. **Follow** its edges: `refs <id>`. Add `--incoming` for what uses it, `--outgoing` for what it uses, `--edge <kind>` to keep one kind, such as `calls` or `affects`. `--depth <n>` follows the edges `n` hops, such as every caller of every caller with `--incoming --edge calls --depth 3`.
+4. **Connect** two nodes: `path <from> <to>` prints the shortest chain of edges between them. It follows edges the way they point, so try the other order when it finds none.
+5. **Narrow** any of these with `--kind`, `--section` and `-n`. `list --kind <kind>` lists every node of a kind.
 
-Add `--json` when a script reads the output. A `<node>` may be an `id`, a file path or a name; a name that fits several nodes prints the candidates.
+Add `--json` when a script reads the output. A `<node>` may be an `id`, a file path or a name. A name that fits several nodes prints the candidates, and one that fits none suggests the closest names.
 
-A _member_, a parameter, field, operation or definition, is found by search but returns its _owner_: the function, the type or the file. Its exact `id` opens the member itself.
+`refs` lists at most 50 references, over every hop, and says how many it left out. Narrow it with `--edge` and a direction before raising `-n`, so the output stays small.
+
+A _member_, a parameter, field, operation or definition, is found by search but returns its _owner_: the function, the type or the file, with the member named beside it, as in `interface InstallerIO (field hashFile)`. Its exact `id` opens the member itself.
+
+A function handed on without being called, such as a callback or the entry of a command map, links as `passes`, not `calls`. Calls made at the top level of a file, outside every function, link nowhere.
 
 Flags, kinds and edge kinds: [`references/commands.md`](references/commands.md).
 
 ## Update
 
 - **Queries rescan by themselves.** The scan is cached in `analyze_out/cache/` and redone when a file changes. `--no-cache` forces it.
-- **Rebuild the site** with `create_docs`. It writes `analyze_out/index.html` and nothing else.
+- **Rebuild the site** with `create_docs`. It writes `analyze_out/index.html` and nothing else; `--out <file>` writes the site there instead, and nothing in the repository.
 - **Change what is scanned** in `.analyzeignore` at the root, written with the defaults on the first run. `--exclude <glob>` skips more for one run.
 - **Never edit `analyze_out/`.** It is output.