@automaton-labs/aib 0.0.6 → 0.0.8

package/dist/help/dsl/topics/recipe.unfamiliar-area.md

@@ -0,0 +1,62 @@
+The same task can be solved with broad output dumps or with structured narrowing.
+Use this recipe to spend context on signal: boundaries, candidate files, then exact slices.
+
+Start with directory structure and boundaries.
+Use `inspect.tree` with directories first:
+
+tree <scope> depth=3 +onlyDirs limit=120
+
+If the task explicitly requires a hidden/dependency/vendor/generated area, keep the scope narrow and only then disable excludes:
+
+tree <narrow-scope> depth=3 +onlyDirs limit=120 +ned +nec
+
+Do not start with broad `+ned +nec` over the repo root.
+
+Localize candidate files.
+If you have a concrete term, symbol, package name, error text, import specifier, or config key, use count search before full match output:
+
+aib rg -- -c "<pattern>" <scope>
+
+Use counts to pick a small set of candidate files before reading matches or file content.
+
+If you do not have a concrete search pattern yet, inspect the file layout instead of inventing broad patterns:
+
+tree <narrow-scope> depth=4 only=["**/*.ts","**/*.tsx","**/*.js","**/*.json"] limit=160
+
+Use the file layout to pick likely files or narrower directories, then continue with focused inspect or focused search.
+
+Map candidate files before implementation reads.
+For TS/JS candidates, inspect the strongest candidates first.
+
+Run:
+aib inspect --stdin
+
+Input:
+file <candidate-a.ts>
+file <candidate-b.ts>
+
+Use file output for declarations and ranges.
+
+Add imports only when dependency, wrapper, source, or "where does this come from" questions matter:
+
+imports <candidate-a.ts>
+
+Add exports only for public module surface, barrels, re-exports, export *, or boundary questions:
+
+exports <candidate-index.ts> +resolveStar
+
+Then read exact implementation slices with qr:
+
+aib qr <candidate-a.ts> s=<range-a>,<range-b>
+
+For non-TS/JS candidates, start with small qr windows:
+
+aib qr <candidate> h=80
+
+Then narrow with `s=` or `r=` as needed.
+Avoid `all` for files whose size/content is unknown.
+
+Read implementation only after you have a narrowed scope, candidate files, and ranges or windows.
+
+Focused help:
+aib help inspect.tree inspect.file inspect.imports inspect.exports qr rg

package/dist/help/dsl/topics/recipes.md

@@ -0,0 +1,18 @@
+Run as:
+aib help <recipe...>
+
+Read and use a recipe when one of these situations appears during regular work.
+
+Opportunistic triggers:
+
+- Trigger: you create, change, or adopt a barrel/import boundary
+  Read: recipe.import-boundary
+
+- Trigger: you are about to change file layout, move files, or rename files
+  Read: recipe.file-layout
+
+- Trigger: you are about to debug, modify, or extend code in an unfamiliar area
+  Read: recipe.unfamiliar-area
+
+- Trigger: you are about to run a tool or runtime probe against a generated, bundled, minified, dependency/vendor, lock/patch, or huge-line artifact
+  Read: recipe.safe-artifact-probing

package/dist/help/dsl/topics/rename.md

@@ -1,6 +1,11 @@
-Modes: preview/apply or execute.
-Use execute for routine changes.
-Use preview/apply when learning a mutation command or inspecting a large multi-step request before writing files.
+Run mutation DSL through aib mutate.
+Use execute for routine changes.
+Use preview/apply when you want to review intent before writing.
+
+Common commands:
+aib mutate preview --stdin
+aib mutate execute --stdin
+aib mutate apply <mutateId>
 
 If a name is ambiguous, use selectors.
 Run help selectors to refresh selector syntax.
@@ -9,17 +14,12 @@ Rename is for semantic symbol renames.
 It follows TypeScript references.
 It is not plain-text replacement.
 
-Single rename:
-rename preview <file> <entity> <newName>
-rename execute <file> <entity> <newName>
-rename apply <previewId>
-
-Use preview/apply when you want to inspect the planned change before writing files.
-Use execute when you want to write immediately.
+Syntax:
+rename <oldName>-><newName> <oldName2>-><newName2>
+
+Run:
+aib mutate execute --stdin
 
-Run:
-aib rename execute --stdin
-
-Input:
-@file src/service.ts
+Input:
+@source src/service.ts
 rename oldName->newName OldService->NewService

package/dist/help/dsl/topics/renameFile.md

@@ -0,0 +1,34 @@
+Run mutation DSL through aib mutate.
+Use execute for routine changes.
+Use preview/apply when you want to review intent before writing.
+
+Common commands:
+aib mutate preview --stdin
+aib mutate execute --stdin
+aib mutate apply <mutateId>
+
+renameFile renames whole files.
+Use it when the filesystem layout is the intent.
+
+Syntax:
+renameFile <sourceFile>-><targetFile> <sourceFile2>-><targetFile2>
+
+Run:
+aib mutate execute --stdin
+
+Input:
+@base src
+renameFile svc/ws-cli.ts->cli.ts svc/ws-command.ts->command.ts
+renameFile svc/core/opt-build.ts->builder.ts
+
+How this resolves:
+- source files resolve from @base;
+- target names without a directory stay beside each source file.
+
+Rules:
+- @base sets the base directory for source files.
+- source file paths resolve from @base; cwd-relative paths are accepted when the @base path does not exist.
+- target names without a directory stay beside each source file.
+- target paths with a directory resolve from @base.
+- source paths and target paths may use `..`.
+- renameFile supports files, not directories.

package/dist/help/dsl/topics/rg.md

@@ -0,0 +1,20 @@
+aib rg
+
+Run ripgrep through AIB.
+
+Regular rg:
+  rg <args>
+
+AIB rg:
+  aib rg -- <args>
+
+Everything after `--` is passed as normal ripgrep arguments.
+Use the same args you would pass to `rg`.
+Use normal paths in input. Do not use AIB path aliases here.
+
+Examples:
+  rg -n "TODO" src/core
+  aib rg -- -n "TODO" src/core
+
+  rg -n --column "SomeValue" ws/commands ws/config
+  aib rg -- -n --column "SomeValue" ws/commands ws/config

package/dist/help/dsl/topics/rules.md

@@ -0,0 +1,24 @@
+Set the command timeout to 5 minutes for AIB requests.
+
+Use `aib rg -- <args>` instead of `rg <args>`.
+Do not use AIB aliases in `aib rg` arguments.
+
+Use aliases from `aib config aliases` as the normal path form for AIB requests.
+Exception: `aib rg` takes real shell paths.
+If AIB maps a full path to an alias in output, use the alias in the next request.
+
+Use matching recipes when their trigger appears during work.
+Do not treat `aib help recipes` as documentation only.
+
+Use `aib qr` for compact text reads: ts, js, cmd, sh, json, log, txt, etc.
+Use AIB path aliases when available.
+Batch paths and combine windows for the same file instead of repeating the path.
+Use `s=A:B,C:D,E` for inclusive slices.
+Use `r=A:B,C:D,E` for start+line-count ranges; a single start like `E` uses default 80 lines.
+Avoid `all` for files whose size/content is unknown; it can dump unnecessary context.
+
+Example:
+aib qr @svc/users.ts s=3:42,66:84,92 @scripts/a.txt h=80 @scripts/b.py r=300:50,500 .prettierrc all
+
+When AIB output shows `// aib-signal`, adjust the next request or workflow.
+Do not repeat the same inefficient pattern unchanged.

package/dist/help/dsl/topics/selectors.md

@@ -16,6 +16,7 @@ c-Name  class
 i-Name  interface
 t-Name  type
 v-name  variable
-e-Name  enum
-m-name  method, usually with parent
+e-Name  enum
+ns-Name namespace
+m-name  method, usually with parent
 p-name  property, usually with parent

package/dist/help/dsl/topics/session.md

@@ -2,7 +2,7 @@ Start by creating or selecting your session.
 Create it once, then reuse it.
 Do not create a new session for every command or subtask.
 
-Session stores saved artifacts, aliases, and prefs.
+Session stores saved artifacts and aliases.
 
 Prefer short session names:
 aa, tr, qa, a2