[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77ZYXWNM4Z484R9PDWHD7HZ":3,"skill-same:01M77ZYXWNM4Z484R9PDWHD7HZ":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M77ZYXWNM4Z484R9PDWHD7HZ","effect-v4-cli",null,"Use when building or reviewing a command-line program on Effect v4 — effect\u002Fcli in core, its exit-code contract, and @effected\u002Fcli-kit, the presentation boundary that decides who the output is for (human, agent, CI), keeps stdout clean, reports failures on stderr, and adds prompts, Ink screens and live progress views — a TUI, wizard, picker or interactive prompt, and the tests that drive them.","spencerbeggs\u002Feffected","spencerbeggs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F109114?v=4","01M77ZTHB70K5Y2VVTRCFY50A5","C. Spencer Beggs","01M77ZTHCC41NXBT3X906K6QM1",8,"MIT","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: effect-v4-cli\ndescription: Use when building or reviewing a command-line program on Effect v4 — effect\u002Fcli in core, its exit-code contract, and @effected\u002Fcli-kit, the presentation boundary that decides who the output is for (human, agent, CI), keeps stdout clean, reports failures on stderr, and adds prompts, Ink screens and live progress views — a TUI, wizard, picker or interactive prompt, and the tests that drive them.\nwhen_to_use: effect\u002Fcli, Command, Flag, Argument, @effect\u002Fcli, exit code, findings exit code, usage error, --format json, --version, stdout vs stderr, stdin, CliLogger, CliRuntime, CliExit, CliColor, CliTest, @effected\u002Fcli-kit\u002Ftesting, NO_COLOR, FORCE_COLOR, TERM=dumb, bin-only package, emitDts false, Command.Environment, ChildProcess vs Command, --agent, --human, --ci, audience, CliAudience, CliEnv, CliTheme, CliMessage, CliLog, Doc, Render, CliFailure, CliPrompt, prompt fallback, interactive, CliUi, @effected\u002Fcli-kit\u002Fui, Ink, Select, MultiSelect, Confirm, TextInput, live view, spinner, progress, DocView, UiProvider, CliUiTest, TestTerminal, TUI, terminal UI, wizard, picker, menu, checkbox, interactive prompt, key bindings, KeyTable, useKeys, Tabs, Viewport, CliUi.lazy, jsx react-jsx, React is not defined, CliUi.map, CliUi.lazyView, masked input, secret prompt, span trail, snapshot serializer\n---\n\n# Effect v4 CLIs\n\nCore owns parsing: `effect\u002Fcli` is the whole framework — `Command`, `Flag`,\n`Argument`, `Prompt`, help, exit-code mapping. It owns nothing about who reads\nthe output or how it reaches them. `@effected\u002Fcli-kit` is the presentation\nboundary that fills that gap: it decides the **audience** (a person, an agent,\na CI job), what the terminal can do, the theme, how a document and a failure\nare drawn for that audience, and when a run may prompt. Its root is\nReact-free; interactive Ink screens and live views live behind\n`@effected\u002Fcli-kit\u002Fui`, whose `ink` and `react` peers are optional. It is\ndeliberately not a second framework: it adds no parser and no command model.\n\nThe one wiring:\n\n```ts\nconst root = Command.make(\"tool\").pipe(\n  Command.withSharedFlags(CliAudience.flags()),\n  Command.withSubcommands([init, verify]),\n)\n\nNodeRuntime.runMain(\n  CliRuntime.main(CliAudience.run(root, { version }), {\n    platform: NodeServices.layer,\n    env: { audienceEnvVar: \"TOOL_AUDIENCE\", log: { envVar: \"TOOL_LOG_LEVEL\" } },\n  }),\n)\n```\n\n| construct | import | reach for it when |\n| --- | --- | --- |\n| `Command`, `Flag`, `Argument`, `Prompt` | `effect\u002Fcli` | declaring the command tree, its flags, positional arguments and core's line prompts |\n| `ChildProcess`, `ChildProcessSpawner` | `effect\u002Fprocess` | building or running a spawned command — **not** `effect\u002Fcli`'s `Command`, which only declares your own CLI |\n| `CliRuntime.main`, `CliRuntime.reportFailures` | `@effected\u002Fcli-kit` | assembling `main`: platform, environment, failure reporting through your own logger, and the process exit code |\n| `CliAudience` | `@effected\u002Fcli-kit` | `--audience`\u002F`--human`\u002F`--agent`\u002F`--ci` on the root, resolved before core parses |\n| `CliEnv` | `@effected\u002Fcli-kit` | building audience, terminal, theme and links once, and deciding `CliInteractive` — normally via `main`'s `env`; `CliEnv.layerTest` fixes them in a test |\n| `Audience`, `TerminalEnv`, `CurrentRuntimeEnv`, `EnvOverride` | `@effected\u002Fenv` | reading who runs the program and what the terminal can do (colour level, width, hyperlinks) |\n| `CliInteractive` | `@effected\u002Fcli-kit` | asking whether this run may prompt a person |\n| `CliTheme`, `Token`, `Status`, `Glyphs` | `@effected\u002Fcli-kit` | painting by token, a typed status vocabulary, Unicode or ASCII glyphs |\n| `CliMessage` | `@effected\u002Fcli-kit` | a one-line themed outcome (\"created 3 files\") that no log level silences |\n| `CliLog.status`, `CliTheme.forAudience` | `@effected\u002Fcli-kit` | a status glyph that keeps its colour on the log channel; painting your own lines by the kit's audience rule |\n| `Doc`, `Render`, `Fmt`, `CliLinks` | `@effected\u002Fcli-kit` | building a report once and rendering it plain for agents, ANSI for people, markdown, or a GitHub Actions log |\n| `CliFormat.flag`, `CliFormat.print`, `CliFormat.printJson` | `@effected\u002Fcli-kit` | a `--format` flag (`auto`, a renderer by name, or `json`; plus `aliases` such as `{ human: \"auto\" }`, and `custom` formats the command renders itself) and the one print that honours it: the report built once as a `Doc`, the data once as a value. `print` takes no custom format, so branch on it first; `printJson` alone for a CLI that keeps its own `--json` |\n| `CliFailure` | `@effected\u002Fcli-kit` | drawing a failure as a document, or letting an error draw itself (`CliDoc`); its `in:` span trail (`spans`, `appModule`) |\n| `CliLog` | `@effected\u002Fcli-kit` | opt-in diagnostics: a level variable, NDJSON for agents and CI, a file sink, components |\n| `CliLog.parseLevel` | `@effected\u002Fcli-kit` | reading a level from your own flag or config with the answer `CliLog.layer` would give (`Option` of the level) |\n| `CliLogger` | `@effected\u002Fcli-kit` | the plain, level-routed logger on its own, for a program without `CliLog` |\n| `CliExit` | `@effected\u002Fcli-kit` | a findings command (a linter that found problems) exiting non-zero by succeeding, never by failing |\n| `CliColor` | `@effected\u002Fcli-kit` | the stdout colour decision as a boolean, and core's formatter coloured by it, in a program without `env` |\n| `CliPrompt.fallback` | `@effected\u002Fcli-kit` | a flag or argument that prompts with core's `Prompt` when missing — only when interactive |\n| `CliUi`, `Select`, `TextInput`, `MultiSelect`, `Confirm` | `@effected\u002Fcli-kit\u002Fui` | an Ink screen from a handler (`prompt`) or as a fallback (`fallback`), with a non-interactive default |\n| `CliUi.lazy` | `@effected\u002Fcli-kit\u002Fui` | mounting a screen of your own whose module holds the JSX, so a non-interactive run never loads React |\n| `CliUi.map` | `@effected\u002Fcli-kit\u002Fui` | mapping a screen's answer, e.g. a `Confirm` behind a `--yes` boolean flag |\n| `CliUi.live`, `CliUi.lazyView`, `DocView`, `UiProvider` | `@effected\u002Fcli-kit\u002Fui` | progress that redraws in place while work runs, its view loaded lazily and a `final` document for runs nobody watches, drawing the `Doc` IR inside Ink |\n| `CliUi.liveDetached` | `@effected\u002Fcli-kit\u002Fui` | a live view hosted by code not built on Effect (a test reporter, a bundler plugin): Promise `handle`\u002F`close`\u002F`exit`, its `render` given directly or as an Effect that reads `env`'s services |\n| `CliUi.routeStream` | `@effected\u002Fcli-kit\u002Fui` | a `Writable` to hand a library in place of a terminal stream, routing its lines above a live view's frame through `printAbove` |\n| `KeyTable`, `useKeys`, `KeyHelp`, `Styled`, `Viewport`, `Tabs` | `@effected\u002Fcli-kit\u002Fui` | writing your own screen: keys as data, themed text, a scrolling list, tabs |\n| `CliTest.sandbox`\u002F`run`\u002F`spawn`, `TestTerminal` | `@effected\u002Fcli-kit\u002Ftesting` | spawning a built bin hermetically (`run` waits and returns the result; `spawn` returns at once for a long-running bin); driving core prompts in a test |\n| `CliUiTest` | `@effected\u002Fcli-kit\u002Fui\u002Ftesting` | driving a screen or live view with keys and reading its frames and the terminal's transcript |\n| `MainOptions.distribution` | `@effected\u002Fcli-kit` | the carrier the bin was installed through: `main` provides engine's `CurrentDistribution` and ends `--version` with its `via \u003Cname> \u003Cversion>` suffix |\n| `CurrentDistribution`, `withDistributionVersion`, `distributionSuffix` | `@effected\u002Fkit` | reading the carrier inside the program, or decorating a `formatVersion` without `main` |\n| `SourceBoundary` | `@effected\u002Fworkspaces\u002Ftesting` | pinning which files may read `process` in a CLI's own tests |\n\n## Standards\n\n- Build the CLI on `effect\u002Fcli`, never `@effect\u002Fcli` — its releases still peer on `effect ^3.x`.\n- Wire every program the one way: share `CliAudience.flags()` on the root, run it with `CliAudience.run`, and pass `env` to `CliRuntime.main`.\n- Give every `Flag.Boolean` an explicit `Flag.withDefault` or `Flag.optional` — omission is a usage error, not `false`.\n- Provide `@effect\u002Fplatform-node`'s `NodeServices.layer` once, as `main`'s `platform`, to satisfy `Command.Environment`.\n- Fail a usage error (`Effect.fail(new CliError.UserError(...))`); succeed a query that legitimately matches nothing.\n- Write program output with `Console.log` or `Doc.print`, one-line outcomes with `CliMessage`, and diagnostics with `Effect.log*` — the streams must never trade places.\n- `CliFormat.flag`'s `markdown` is the kit's `Render.markdown` of your report `Doc`, so a CLI that prints its own markdown string offers it under another name in `custom` (`custom: [\"markdown\"]` throws: a built-in name cannot be custom) and branches on it before `CliFormat.print`.\n- Build a report as a `Doc` and let the audience pick the renderer; offer `--format` with `CliFormat.flag` and print through `CliFormat.print`; reach for `Render.markdown` only for a file or a step summary.\n- Ask for input only through `CliPrompt.fallback`, `CliUi.prompt` or `CliUi.fallback`, each with a non-interactive default.\n- Set `\"jsx\": \"react-jsx\"` for a `.tsx` screen, keep each screen in its own module with a default export, and mount it with `CliUi.lazy`, so JSX never loads in the command module.\n- Log through `handle.logConsole` while a live view is drawn, and not at all while a screen is mounted. Forward foreign output (a child's stderr) with `handle.printAbove(stream, line)`, which returns `false`, writing nothing, when no frame is mounted.\n- Paint a status glyph on a diagnostic with `CliLog.status`, and apply the audience rule to your own lines with `CliTheme.forAudience`; never copy the rule or hand-paint a glyph into `Effect.log*` (the logger strips it).\n- Pass `env: { appModule: import.meta.url }` to `CliRuntime.main` from a bin that is installed under `node_modules\u002F@effected\u002F`, so the failure report's span trail keeps its own spans.\n- Give a live view `render: CliUi.lazyView(() => import(\".\u002Fview.js\"))` and a `final` document, so `--help`, agent, CI and piped runs never load React or Ink.\n- Report findings by succeeding and calling `CliExit.set(code)`, never by failing or calling `process.exit` in a handler.\n- Set `emitDts = false` under `[package.build]` in `effected.toml` for a package whose `exports` is `\".\u002Fpackage.json\"` only.\n- Confine every `process` read (`env`, `argv`, `cwd`, `execPath`, `isTTY`) to `bin.ts`, `main.ts` or `version.ts`; pass it down as a plain value.\n\n## Footguns\n\n- No v4 line of `@effect\u002Fcli` exists — see `core-framework.md`.\n- `Flag.Boolean` has no implicit `false`; omission is `MissingOption` — see `core-framework.md`.\n- `CliRuntime.main` without `env` builds no environment: `CliInteractive` stays `false` and nothing ever prompts — see `presentation.md`.\n- `CliAudience.provide` alone misses fallback prompts and the failure report; use `CliAudience.run` — see `presentation.md`.\n- `CliUi.prompt` with a real `otherwise` has `Cancelled` alone as its error, but without one (or with `otherwise: undefined`) it keeps `NotInteractive`; a `CliUiTest.session` is 80 columns and truncates rows; `session.layer` goes inside `CliEnv.layerTest` — see `prompts-and-screens.md`, `testing-a-cli.md`.\n- Top-level `Doc` blocks print with no blank line between them; wrap in `Doc.section(undefined, [...])` — see `presentation.md`.\n- `FORCE_COLOR` beats `NO_COLOR`, and a terminal with no `TERM`\u002F`COLORTERM` gets no colour — see `presentation.md`.\n- `TERM=dumb` is not interactive: it gets what a pipe gets — see `presentation.md`.\n- An agent audience never gets an escape, even from an explicit `Render.ansi` — see `presentation.md`.\n- Under `env`, `main`'s formatter shadows one the platform sets; override through `env.formatter` — see `recipes.md`.\n- A `Logger.layer([...])` of your own beside `CliLog` replaces its whole logger set and silences diagnostics — see `presentation.md`.\n- JSX or an `ink`\u002F`react` import in the module that declares your commands loads React on every run, `--agent` and CI included; `@effected\u002Fcli-kit\u002Fui` itself never does — see `prompts-and-screens.md`.\n- `\"jsx\": \"react\"` (classic) crashes a screen at mount with `React is not defined` — see `prompts-and-screens.md`.\n- A cancel in a fallback prompt is a defect a handler's `catchTag` cannot see; `main` renders it, exit `130` — see `prompts-and-screens.md`.\n- A line written while a screen is mounted tears the frame (`patchConsole` is off) — see `prompts-and-screens.md`.\n- A screen that awaits another `CliUi.run` deadlocks, and `Confirm`'s `otherwise` is a whole `{ confirmed, toggles }`, never a boolean (wrap it in `CliUi.map` for a boolean flag) — see `prompts-and-screens.md`.\n- Ink delivers a whole stdin read of keys before React re-renders; a handler must step from current state — see `prompts-and-screens.md`.\n- React error boundaries do not catch errors thrown in Ink `useInput`\u002F`usePaste` handlers — see `prompts-and-screens.md`.\n- `CliUiTest`'s `press(\"y\")` dies (send `type(\"y\")` or `press({ char: \"y\" })`), its waits are real time (`it.live` for a test that sleeps), and under `main` with `env` the session's `interactive` is shadowed by `CliEnv` — see `testing-a-cli.md`.\n- A `TextInput` `mask` predicate latches from its first `true` until the value is emptied; match the giveaway anywhere (`\u002Fgh[pousr]_|github_pat_\u002F`), never as a prefix, and never echo the value in a `validate` message, which is drawn unmasked — see `prompts-and-screens.md`.\n- A share headline (`1\u002F3 repos`) reads a `{ one, other }` label by the total, a standalone count by its own `n` — see `presentation.md`.\n- The failure report's span trail defaults to `spans: \"app\"`, which leaves out spans defined under `node_modules\u002F@effected\u002F` and `node_modules\u002Feffect\u002F`; a bin installed there without `appModule` loses its own spans too — see `presentation.md`.\n- A human whose stream is not a terminal (`tool | grep`) gets an unbounded width; to keep one line whole at a narrow terminal, use `Doc.line(content, { wrap: false })` — see `presentation.md`.\n- Keep a live view's `LiveOptions` in a module the view does not import, or Biome's `noImportCycles` flags `CliUi.lazyView`'s dynamic import — see `live-view.md`.\n- `CliUiTest.session`'s `layer` is typed `Layer\u003CCliTheme>` but also supplies the streams and `CliInteractive` as references: provided where a presentation layer shadows it, it falls back quietly to the real streams — see `testing-a-cli.md`.\n- `PubSub.shutdown` and a bare scope close drop a live view's tail; end with `handle.close` or `PubSub.end`, and host a view outside Effect with `CliUi.liveDetached`, not by hand — see `live-view.md`.\n- A live view fed a forking stream subscribes late; pass the `PubSub.Subscription` itself — see `live-view.md`.\n- The default logger and `runMain`'s failure report both land on stdout, not stderr — see `output-and-logging.md`.\n- `errorReported: false` is what SUPPRESSES the runtime's own log, not what causes it — see `output-and-logging.md`.\n- `Cannot merge zero API models` means the package needs `emitDts: false`, not an `index.ts` — see `bin-only-package.md`.\n- A no-match result must succeed; only a usage error may fail — see `exit-codes.md`.\n- `it.effect` starts `TestClock` at the epoch, and `TestConsole.logLines` accumulates across a whole test — see `testing-a-cli.md`.\n- `Command.provide` builds its layer before the handler runs — a handler cannot pre-flight the value the layer depends on — see `gotchas.md`.\n- `Flag.File(name, { mustExist: true })` fails at parse time (a usage error, exit `1` under a bare `runMain`, `64` under `CliRuntime.main`), not as your own infrastructure error — see `gotchas.md`.\n- Two optional positionals bind in declaration order — the first one gets a lone argument, not whichever one \"makes sense\" — see `gotchas.md`.\n- `Schema.decodeUnknownSync` in a handler throws a defect, invisible to `catchTag` — use `Schema.decodeUnknownEffect` — see `gotchas.md`.\n- `Runtime.getErrorExitCode` returns `1` for both \"marked 1\" and \"unmarked\" — test the marker with `Runtime.errorExitCode in error` — see `gotchas.md`.\n- `Argument.Path` resolves a relative value against the process's own cwd, at parse time — `Flag.Path`\u002F`File`\u002F`Directory` share the same behavior — see `gotchas.md`.\n- The built-in global flags (`--help`, `--version`, `--wizard`, `--completions`, `--log-level`) are on by default, program-wide — trim them with `CliConfig.layer({ builtIns: [] })`, not per command — see `gotchas.md`.\n\n## Additional resources\n\n- [presentation.md](.\u002Freferences\u002Fpresentation.md) — the one wiring, audience and `CliInteractive`, `CliEnv` and its options, colour precedence, the theme vocabulary, `CliMessage`, the `Doc` IR and renderers, the failure report and `CliLog`. Load when: wiring `main`, deciding which channel a line goes to, rendering a report, or customising the failure report or diagnostics.\n- [prompts-and-screens.md](.\u002Freferences\u002Fprompts-and-screens.md) — setup (install line, peers, `jsx: react-jsx`), keeping React off non-interactive runs with `CliUi.lazy`, `CliPrompt.fallback` vs `CliUi`, the widgets and their options, a `Confirm` worked through (whole-`ConfirmResult` default, `CliUi.map` for a boolean flag), writing a screen with `KeyTable`\u002F`useKeys`\u002F`Viewport`\u002F`Tabs`, and the rules that keep a screen from tearing the terminal. Load when: setting up Ink screens, asking a person for input, or writing or reviewing an Ink screen.\n- [live-view.md](.\u002Freferences\u002Flive-view.md) — `CliUi.live`: runs, subscribing and ending without losing the tail, `logConsole`, non-interactive modes and the `final` document, a lazy view with `CliUi.lazyView`, a view hosted outside Effect with `CliUi.liveDetached` and `CliUi.routeStream`, `DocView` and `UiProvider`. Load when: drawing progress that updates in place, hosting a live view from a test reporter or bundler plugin, or hosting an Ink tree the kit did not mount.\n- [core-framework.md](.\u002Freferences\u002Fcore-framework.md) — the module inventory, PascalCase constructors, `Flag.Boolean`'s missing default, `Command.Environment`, and the two different `Command`s. Load when: writing or reviewing the `Command`\u002F`Flag`\u002F`Argument` declaration itself.\n- [output-and-logging.md](.\u002Freferences\u002Foutput-and-logging.md) — the three defaults core gets wrong at a terminal, the `CliLogger` implementation facts, exit-code reporting, and `CliColor`. Load when: wiring a logger by hand, or debugging a duplicate or missing failure report.\n- [bin-only-package.md](.\u002Freferences\u002Fbin-only-package.md) — `emitDts: false`, the `exports: \".\u002Fpackage.json\"` shape, and why `Cannot merge zero API models` is not an extractor bug. Load when: building a package whose only surface is a `bin`.\n- [exit-codes.md](.\u002Freferences\u002Fexit-codes.md) — the exit-code contract, `CliRuntime.main`'s assembly order, the code table and `exitCodes` by tag, and how a findings command exits non-zero by succeeding. Load when: deciding whether a code path should fail or succeed, assembling `main.ts`, or handling `CliError` exhaustively.\n- [testing-a-cli.md](.\u002Freferences\u002Ftesting-a-cli.md) — the two false-green traps, the `layerTest` doubles and a capturing `Console`, `TestTerminal`, `CliUiTest` for screens and live views (a worked `session` test of a whole wizard, the harness traps, the snapshot serializer), and `CliTest` for spawning a built bin. Load when: writing a test that asserts on CLI output, a prompt, a screen, a wizard, a live view, or a real subprocess's exit code and streams.\n- [gotchas.md](.\u002Freferences\u002Fgotchas.md) — seven traps that pass a type-check and a casual run: `Command.provide`'s build order, `Flag.File`'s parse-time existence check, positional binding order, `decodeUnknownSync`'s defect, the exit-code marker, `Argument.Path`\u002F`Flag.Path` resolution, and the on-by-default global flags. Load when: a handler isn't seeing the value you expect, or an exit code doesn't match what the handler did.\n- [recipes.md](.\u002Freferences\u002Frecipes.md) — patterns the kit deliberately does not package: the main-assembly file layout, the version constant and the carrier on `--version`, the JSON failure tap, reading stdin safely, process confinement, and an injectable clock. Load when: wiring up a new CLI front end from scratch.\n\nAnchors in this skill and its references cite the vendored tag at\n`.repos\u002Feffect\u002Fpackages\u002Feffect\u002Fsrc\u002F`; a consumer without that tree searches\n`node_modules\u002Feffect\u002Fsrc` by symbol name instead of by line number.\n\n## Related skills\n\n- **`effect-v4-module-index`** — which core module owns a capability, including\n  `effect\u002Fprocess` and the `NodeServices.layer` boundary.\n- **`effect-v4-idioms`** — `PlatformError`, typed errors and core patterns.\n- **`effect-v4-services-layers`** — providing `Command.Environment` once at the\n  boundary, and the memoization discipline.\n- **`effect-v4-testing`** — `TestClock`, `TestConsole`, and proving a suite can fail.\n- **`effected-packages`** — the `@effected\u002Fenv` and `@effected\u002Fcli-kit` rows and\n  their construct index.\n","# Effect v4 CLIs\n\nCore owns parsing: `effect\u002Fcli` is the whole framework — `Command`, `Flag`,\n`Argument`, `Prompt`, help, exit-code mapping. It owns nothing about who reads\nthe output or how it reaches them. `@effected\u002Fcli-kit` is the presentation\nboundary that fills that gap: it decides the **audience** (a person, an agent,\na CI job), what the terminal can do, the theme, how a document and a failure\nare drawn for that audience, and when a run may prompt. Its root is\nReact-free; interactive Ink screens and live views live behind\n`@effected\u002Fcli-kit\u002Fui`, whose `ink` and `react` peers are optional. It is\ndeliberately not a second framework: it adds no parser and no command model.\n\nThe one wiring:\n\n```ts\nconst root = Command.make(\"tool\").pipe(\n  Command.withSharedFlags(CliAudience.flags()),\n  Command.withSubcommands([init, verify]),\n)\n\nNodeRuntime.runMain(\n  CliRuntime.main(CliAudience.run(root, { version }), {\n    platform: NodeServices.layer,\n    env: { audienceEnvVar: \"TOOL_AUDIENCE\", log: { envVar: \"TOOL_LOG_LEVEL\" } },\n  }),\n)\n```\n\n| construct | import | reach for it when |\n| --- | --- | --- |\n| `Command`, `Flag`, `Argument`, `Prompt` | `effect\u002Fcli` | declaring the command tree, its flags, positional arguments and core's line prompts |\n| `ChildProcess`, `ChildProcessSpawner` | `effect\u002Fprocess` | building or running a spawned command — **not** `effect\u002Fcli`'s `Command`, which only declares your own CLI |\n| `CliRuntime.main`, `CliRuntime.reportFailures` | `@effected\u002Fcli-kit` | assembling `main`: platform, environment, failure reporting through your own logger, and the process exit code |\n| `CliAudience` | `@effected\u002Fcli-kit` | `--audience`\u002F`--human`\u002F`--agent`\u002F`--ci` on the root, resolved before core parses |\n| `CliEnv` | `@effected\u002Fcli-kit` | building audience, terminal, theme and links once, and deciding `CliInteractive` — normally via `main`'s `env`; `CliEnv.layerTest` fixes them in a test |\n| `Audience`, `TerminalEnv`, `CurrentRuntimeEnv`, `EnvOverride` | `@effected\u002Fenv` | reading who runs the program and what the terminal can do (colour level, width, hyperlinks) |\n| `CliInteractive` | `@effected\u002Fcli-kit` | asking whether this run may prompt a person |\n| `CliTheme`, `Token`, `Status`, `Glyphs` | `@effected\u002Fcli-kit` | painting by token, a typed status vocabulary, Unicode or ASCII glyphs |\n| `CliMessage` | `@effected\u002Fcli-kit` | a one-line themed outcome (\"created 3 files\") that no log level silences |\n| `CliLog.status`, `CliTheme.forAudience` | `@effected\u002Fcli-kit` | a status glyph that keeps its colour on the log channel; painting your own lines by the kit's audience rule |\n| `Doc`, `Render`, `Fmt`, `CliLinks` | `@effected\u002Fcli-kit` | building a report once and rendering it plain for agents, ANSI for people, markdown, or a GitHub Actions log |\n| `CliFormat.flag`, `CliFormat.print`, `CliFormat.printJson` | `@effected\u002Fcli-kit` | a `--format` flag (`auto`, a renderer by name, or `json`; plus `aliases` such as `{ human: \"auto\" }`, and `custom` formats the command renders itself) and the one print that honours it: the report built once as a `Doc`, the data once as a value. `print` takes no custom format, so branch on it first; `printJson` alone for a CLI that keeps its own `--json` |\n| `CliFailure` | `@effected\u002Fcli-kit` | drawing a failure as a document, or letting an error draw itself (`CliDoc`); its `in:` span trail (`spans`, `appModule`) |\n| `CliLog` | `@effected\u002Fcli-kit` | opt-in diagnostics: a level variable, NDJSON for agents and CI, a file sink, components |\n| `CliLog.parseLevel` | `@effected\u002Fcli-kit` | reading a level from your own flag or config with the answer `CliLog.layer` would give (`Option` of the level) |\n| `CliLogger` | `@effected\u002Fcli-kit` | the plain, level-routed logger on its own, for a program without `CliLog` |\n| `CliExit` | `@effected\u002Fcli-kit` | a findings command (a linter that found problems) exiting non-zero by succeeding, never by failing |\n| `CliColor` | `@effected\u002Fcli-kit` | the stdout colour decision as a boolean, and core's formatter coloured by it, in a program without `env` |\n| `CliPrompt.fallback` | `@effected\u002Fcli-kit` | a flag or argument that prompts with core's `Prompt` when missing — only when interactive |\n| `CliUi`, `Select`, `TextInput`, `MultiSelect`, `Confirm` | `@effected\u002Fcli-kit\u002Fui` | an Ink screen from a handler (`prompt`) or as a fallback (`fallback`), with a non-interactive default |\n| `CliUi.lazy` | `@effected\u002Fcli-kit\u002Fui` | mounting a screen of your own whose module holds the JSX, so a non-interactive run never loads React |\n| `CliUi.map` | `@effected\u002Fcli-kit\u002Fui` | mapping a screen's answer, e.g. a `Confirm` behind a `--yes` boolean flag |\n| `CliUi.live`, `CliUi.lazyView`, `DocView`, `UiProvider` | `@effected\u002Fcli-kit\u002Fui` | progress that redraws in place while work runs, its view loaded lazily and a `final` document for runs nobody watches, drawing the `Doc` IR inside Ink |\n| `CliUi.liveDetached` | `@effected\u002Fcli-kit\u002Fui` | a live view hosted by code not built on Effect (a test reporter, a bundler plugin): Promise `handle`\u002F`close`\u002F`exit`, its `render` given directly or as an Effect that reads `env`'s services |\n| `CliUi.routeStream` | `@effected\u002Fcli-kit\u002Fui` | a `Writable` to hand a library in place of a terminal stream, routing its lines above a live view's frame through `printAbove` |\n| `KeyTable`, `useKeys`, `KeyHelp`, `Styled`, `Viewport`, `Tabs` | `@effected\u002Fcli-kit\u002Fui` | writing your own screen: keys as data, themed text, a scrolling list, tabs |\n| `CliTest.sandbox`\u002F`run`\u002F`spawn`, `TestTerminal` | `@effected\u002Fcli-kit\u002Ftesting` | spawning a built bin hermetically (`run` waits and returns the result; `spawn` returns at once for a long-running bin); driving core prompts in a test |\n| `CliUiTest` | `@effected\u002Fcli-kit\u002Fui\u002Ftesting` | driving a screen or live view with keys and reading its frames and the terminal's transcript |\n| `MainOptions.distribution` | `@effected\u002Fcli-kit` | the carrier the bin was installed through: `main` provides engine's `CurrentDistribution` and ends `--version` with its `via \u003Cname> \u003Cversion>` suffix |\n| `CurrentDistribution`, `withDistributionVersion`, `distributionSuffix` | `@effected\u002Fkit` | reading the carrier inside the program, or decorating a `formatVersion` without `main` |\n| `SourceBoundary` | `@effected\u002Fworkspaces\u002Ftesting` | pinning which files may read `process` in a CLI's own tests |\n\n## Standards\n\n- Build the CLI on `effect\u002Fcli`, never `@effect\u002Fcli` — its releases still peer on `effect ^3.x`.\n- Wire every program the one way: share `CliAudience.flags()` on the root, run it with `CliAudience.run`, and pass `env` to `CliRuntime.main`.\n- Give every `Flag.Boolean` an explicit `Flag.withDefault` or `Flag.optional` — omission is a usage error, not `false`.\n- Provide `@effect\u002Fplatform-node`'s `NodeServices.layer` once, as `main`'s `platform`, to satisfy `Command.Environment`.\n- Fail a usage error (`Effect.fail(new CliError.UserError(...))`); succeed a query that legitimately matches nothing.\n- Write program output with `Console.log` or `Doc.print`, one-line outcomes with `CliMessage`, and diagnostics with `Effect.log*` — the streams must never trade places.\n- `CliFormat.flag`'s `markdown` is the kit's `Render.markdown` of your report `Doc`, so a CLI that prints its own markdown string offers it under another name in `custom` (`custom: [\"markdown\"]` throws: a built-in name cannot be custom) and branches on it before `CliFormat.print`.\n- Build a report as a `Doc` and let the audience pick the renderer; offer `--format` with `CliFormat.flag` and print through `CliFormat.print`; reach for `Render.markdown` only for a file or a step summary.\n- Ask for input only through `CliPrompt.fallback`, `CliUi.prompt` or `CliUi.fallback`, each with a non-interactive default.\n- Set `\"jsx\": \"react-jsx\"` for a `.tsx` screen, keep each screen in its own module with a default export, and mount it with `CliUi.lazy`, so JSX never loads in the command module.\n- Log through `handle.logConsole` while a live view is drawn, and not at all while a screen is mounted. Forward foreign output (a child's stderr) with `handle.printAbove(stream, line)`, which returns `false`, writing nothing, when no frame is mounted.\n- Paint a status glyph on a diagnostic with `CliLog.status`, and apply the audience rule to your own lines with `CliTheme.forAudience`; never copy the rule or hand-paint a glyph into `Effect.log*` (the logger strips it).\n- Pass `env: { appModule: import.meta.url }` to `CliRuntime.main` from a bin that is installed under `node_modules\u002F@effected\u002F`, so the failure report's span trail keeps its own spans.\n- Give a live view `render: CliUi.lazyView(() => import(\".\u002Fview.js\"))` and a `final` document, so `--help`, agent, CI and piped runs never load React or Ink.\n- Report findings by succeeding and calling `CliExit.set(code)`, never by failing or calling `process.exit` in a handler.\n- Set `emitDts = false` under `[package.build]` in `effected.toml` for a package whose `exports` is `\".\u002Fpackage.json\"` only.\n- Confine every `process` read (`env`, `argv`, `cwd`, `execPath`, `isTTY`) to `bin.ts`, `main.ts` or `version.ts`; pass it down as a plain value.\n\n## Footguns\n\n- No v4 line of `@effect\u002Fcli` exists — see `core-framework.md`.\n- `Flag.Boolean` has no implicit `false`; omission is `MissingOption` — see `core-framework.md`.\n- `CliRuntime.main` without `env` builds no environment: `CliInteractive` stays `false` and nothing ever prompts — see `presentation.md`.\n- `CliAudience.provide` alone misses fallback prompts and the failure report; use `CliAudience.run` — see `presentation.md`.\n- `CliUi.prompt` with a real `otherwise` has `Cancelled` alone as its error, but without one (or with `otherwise: undefined`) it keeps `NotInteractive`; a `CliUiTest.session` is 80 columns and truncates rows; `session.layer` goes inside `CliEnv.layerTest` — see `prompts-and-screens.md`, `testing-a-cli.md`.\n- Top-level `Doc` blocks print with no blank line between them; wrap in `Doc.section(undefined, [...])` — see `presentation.md`.\n- `FORCE_COLOR` beats `NO_COLOR`, and a terminal with no `TERM`\u002F`COLORTERM` gets no colour — see `presentation.md`.\n- `TERM=dumb` is not interactive: it gets what a pipe gets — see `presentation.md`.\n- An agent audience never gets an escape, even from an explicit `Render.ansi` — see `presentation.md`.\n- Under `env`, `main`'s formatter shadows one the platform sets; override through `env.formatter` — see `recipes.md`.\n- A `Logger.layer([...])` of your own beside `CliLog` replaces its whole logger set and silences diagnostics — see `presentation.md`.\n- JSX or an `ink`\u002F`react` import in the module that declares your commands loads React on every run, `--agent` and CI included; `@effected\u002Fcli-kit\u002Fui` itself never does — see `prompts-and-screens.md`.\n- `\"jsx\": \"react\"` (classic) crashes a screen at mount with `React is not defined` — see `prompts-and-screens.md`.\n- A cancel in a fallback prompt is a defect a handler's `catchTag` cannot see; `main` renders it, exit `130` — see `prompts-and-screens.md`.\n- A line written while a screen is mounted tears the frame (`patchConsole` is off) — see `prompts-and-screens.md`.\n- A screen that awaits another `CliUi.run` deadlocks, and `Confirm`'s `otherwise` is a whole `{ confirmed, toggles }`, never a boolean (wrap it in `CliUi.map` for a boolean flag) — see `prompts-and-screens.md`.\n- Ink delivers a whole stdin read of keys before React re-renders; a handler must step from current state — see `prompts-and-screens.md`.\n- React error boundaries do not catch errors thrown in Ink `useInput`\u002F`usePaste` handlers — see `prompts-and-screens.md`.\n- `CliUiTest`'s `press(\"y\")` dies (send `type(\"y\")` or `press({ char: \"y\" })`), its waits are real time (`it.live` for a test that sleeps), and under `main` with `env` the session's `interactive` is shadowed by `CliEnv` — see `testing-a-cli.md`.\n- A `TextInput` `mask` predicate latches from its first `true` until the value is emptied; match the giveaway anywhere (`\u002Fgh[pousr]_|github_pat_\u002F`), never as a prefix, and never echo the value in a `validate` message, which is drawn unmasked — see `prompts-and-screens.md`.\n- A share headline (`1\u002F3 repos`) reads a `{ one, other }` label by the total, a standalone count by its own `n` — see `presentation.md`.\n- The failure report's span trail defaults to `spans: \"app\"`, which leaves out spans defined under `node_modules\u002F@effected\u002F` and `node_modules\u002Feffect\u002F`; a bin installed there without `appModule` loses its own spans too — see `presentation.md`.\n- A human whose stream is not a terminal (`tool | grep`) gets an unbounded width; to keep one line whole at a narrow terminal, use `Doc.line(content, { wrap: false })` — see `presentation.md`.\n- Keep a live view's `LiveOptions` in a module the view does not import, or Biome's `noImportCycles` flags `CliUi.lazyView`'s dynamic import — see `live-view.md`.\n- `CliUiTest.session`'s `layer` is typed `Layer\u003CCliTheme>` but also supplies the streams and `CliInteractive` as references: provided where a presentation layer shadows it, it falls back quietly to the real streams — see `testing-a-cli.md`.\n- `PubSub.shutdown` and a bare scope close drop a live view's tail; end with `handle.close` or `PubSub.end`, and host a view outside Effect with `CliUi.liveDetached`, not by hand — see `live-view.md`.\n- A live view fed a forking stream subscribes late; pass the `PubSub.Subscription` itself — see `live-view.md`.\n- The default logger and `runMain`'s failure report both land on stdout, not stderr — see `output-and-logging.md`.\n- `errorReported: false` is what SUPPRESSES the runtime's own log, not what causes it — see `output-and-logging.md`.\n- `Cannot merge zero API models` means the package needs `emitDts: false`, not an `index.ts` — see `bin-only-package.md`.\n- A no-match result must succeed; only a usage error may fail — see `exit-codes.md`.\n- `it.effect` starts `TestClock` at the epoch, and `TestConsole.logLines` accumulates across a whole test — see `testing-a-cli.md`.\n- `Command.provide` builds its layer before the handler runs — a handler cannot pre-flight the value the layer depends on — see `gotchas.md`.\n- `Flag.File(name, { mustExist: true })` fails at parse time (a usage error, exit `1` under a bare `runMain`, `64` under `CliRuntime.main`), not as your own infrastructure error — see `gotchas.md`.\n- Two optional positionals bind in declaration order — the first one gets a lone argument, not whichever one \"makes sense\" — see `gotchas.md`.\n- `Schema.decodeUnknownSync` in a handler throws a defect, invisible to `catchTag` — use `Schema.decodeUnknownEffect` — see `gotchas.md`.\n- `Runtime.getErrorExitCode` returns `1` for both \"marked 1\" and \"unmarked\" — test the marker with `Runtime.errorExitCode in error` — see `gotchas.md`.\n- `Argument.Path` resolves a relative value against the process's own cwd, at parse time — `Flag.Path`\u002F`File`\u002F`Directory` share the same behavior — see `gotchas.md`.\n- The built-in global flags (`--help`, `--version`, `--wizard`, `--completions`, `--log-level`) are on by default, program-wide — trim them with `CliConfig.layer({ builtIns: [] })`, not per command — see `gotchas.md`.\n\n## Additional resources\n\n- [presentation.md](.\u002Freferences\u002Fpresentation.md) — the one wiring, audience and `CliInteractive`, `CliEnv` and its options, colour precedence, the theme vocabulary, `CliMessage`, the `Doc` IR and renderers, the failure report and `CliLog`. Load when: wiring `main`, deciding which channel a line goes to, rendering a report, or customising the failure report or diagnostics.\n- [prompts-and-screens.md](.\u002Freferences\u002Fprompts-and-screens.md) — setup (install line, peers, `jsx: react-jsx`), keeping React off non-interactive runs with `CliUi.lazy`, `CliPrompt.fallback` vs `CliUi`, the widgets and their options, a `Confirm` worked through (whole-`ConfirmResult` default, `CliUi.map` for a boolean flag), writing a screen with `KeyTable`\u002F`useKeys`\u002F`Viewport`\u002F`Tabs`, and the rules that keep a screen from tearing the terminal. Load when: setting up Ink screens, asking a person for input, or writing or reviewing an Ink screen.\n- [live-view.md](.\u002Freferences\u002Flive-view.md) — `CliUi.live`: runs, subscribing and ending without losing the tail, `logConsole`, non-interactive modes and the `final` document, a lazy view with `CliUi.lazyView`, a view hosted outside Effect with `CliUi.liveDetached` and `CliUi.routeStream`, `DocView` and `UiProvider`. Load when: drawing progress that updates in place, hosting a live view from a test reporter or bundler plugin, or hosting an Ink tree the kit did not mount.\n- [core-framework.md](.\u002Freferences\u002Fcore-framework.md) — the module inventory, PascalCase constructors, `Flag.Boolean`'s missing default, `Command.Environment`, and the two different `Command`s. Load when: writing or reviewing the `Command`\u002F`Flag`\u002F`Argument` declaration itself.\n- [output-and-logging.md](.\u002Freferences\u002Foutput-and-logging.md) — the three defaults core gets wrong at a terminal, the `CliLogger` implementation facts, exit-code reporting, and `CliColor`. Load when: wiring a logger by hand, or debugging a duplicate or missing failure report.\n- [bin-only-package.md](.\u002Freferences\u002Fbin-only-package.md) — `emitDts: false`, the `exports: \".\u002Fpackage.json\"` shape, and why `Cannot merge zero API models` is not an extractor bug. Load when: building a package whose only surface is a `bin`.\n- [exit-codes.md](.\u002Freferences\u002Fexit-codes.md) — the exit-code contract, `CliRuntime.main`'s assembly order, the code table and `exitCodes` by tag, and how a findings command exits non-zero by succeeding. Load when: deciding whether a code path should fail or succeed, assembling `main.ts`, or handling `CliError` exhaustively.\n- [testing-a-cli.md](.\u002Freferences\u002Ftesting-a-cli.md) — the two false-green traps, the `layerTest` doubles and a capturing `Console`, `TestTerminal`, `CliUiTest` for screens and live views (a worked `session` test of a whole wizard, the harness traps, the snapshot serializer), and `CliTest` for spawning a built bin. Load when: writing a test that asserts on CLI output, a prompt, a screen, a wizard, a live view, or a real subprocess's exit code and streams.\n- [gotchas.md](.\u002Freferences\u002Fgotchas.md) — seven traps that pass a type-check and a casual run: `Command.provide`'s build order, `Flag.File`'s parse-time existence check, positional binding order, `decodeUnknownSync`'s defect, the exit-code marker, `Argument.Path`\u002F`Flag.Path` resolution, and the on-by-default global flags. Load when: a handler isn't seeing the value you expect, or an exit code doesn't match what the handler did.\n- [recipes.md](.\u002Freferences\u002Frecipes.md) — patterns the kit deliberately does not package: the main-assembly file layout, the version constant and the carrier on `--version`, the JSON failure tap, reading stdin safely, process confinement, and an injectable clock. Load when: wiring up a new CLI front end from scratch.\n\nAnchors in this skill and its references cite the vendored tag at\n`.repos\u002Feffect\u002Fpackages\u002Feffect\u002Fsrc\u002F`; a consumer without that tree searches\n`node_modules\u002Feffect\u002Fsrc` by symbol name instead of by line number.\n\n## Related skills\n\n- **`effect-v4-module-index`** — which core module owns a capability, including\n  `effect\u002Fprocess` and the `NodeServices.layer` boundary.\n- **`effect-v4-idioms`** — `PlatformError`, typed errors and core patterns.\n- **`effect-v4-services-layers`** — providing `Command.Environment` once at the\n  boundary, and the memoization discipline.\n- **`effect-v4-testing`** — `TestClock`, `TestConsole`, and proving a suite can fail.\n- **`effected-packages`** — the `@effected\u002Fenv` and `@effected\u002Fcli-kit` rows and\n  their construct index.\n",{"name":5,"description":7,"when_to_use":24},"effect\u002Fcli, Command, Flag, Argument, @effect\u002Fcli, exit code, findings exit code, usage error, --format json, --version, stdout vs stderr, stdin, CliLogger, CliRuntime, CliExit, CliColor, CliTest, @effected\u002Fcli-kit\u002Ftesting, NO_COLOR, FORCE_COLOR, TERM=dumb, bin-only package, emitDts false, Command.Environment, ChildProcess vs Command, --agent, --human, --ci, audience, CliAudience, CliEnv, CliTheme, CliMessage, CliLog, Doc, Render, CliFailure, CliPrompt, prompt fallback, interactive, CliUi, @effected\u002Fcli-kit\u002Fui, Ink, Select, MultiSelect, Confirm, TextInput, live view, spinner, progress, DocView, UiProvider, CliUiTest, TestTerminal, TUI, terminal UI, wizard, picker, menu, checkbox, interactive prompt, key bindings, KeyTable, useKeys, Tabs, Viewport, CliUi.lazy, jsx react-jsx, React is not defined, CliUi.map, CliUi.lazyView, masked input, secret prompt, span trail, snapshot serializer","main","11d6b3ae59538b0e16ad67c315ecb0c25fcb0125","plugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli",2,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected","https:\u002F\u002Fgithub.com\u002Fspencerbeggs","2026-11-14 07:03:25",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add spencerbeggs\u002Feffected --skill effect-v4-cli",{"tool":38,"command":39},"bunx","bunx skills add spencerbeggs\u002Feffected --skill effect-v4-cli",{"tool":41,"command":42},"pnpm","pnpm dlx skills add spencerbeggs\u002Feffected --skill effect-v4-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002FSKILL.md",true,[46,52,56,60,64,68,72,76,80,84],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fbin-only-package.md","REFERENCE","参考文档",4589,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fbin-only-package.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcore-framework.md",10601,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fcore-framework.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fexit-codes.md",9781,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fexit-codes.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fgotchas.md",9925,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fgotchas.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Flive-view.md",15553,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Flive-view.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Foutput-and-logging.md",9273,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Foutput-and-logging.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fpresentation.md",21619,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fpresentation.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fprompts-and-screens.md",22562,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Fprompts-and-screens.md",{"path":81,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Frecipes.md",15729,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Frecipes.md",{"path":85,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Ftesting-a-cli.md",27806,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fbuilds\u002Fclaude\u002Fskills\u002Feffect-v4-cli\u002Freferences\u002Ftesting-a-cli.md",[89,96,103,110,117,124],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M780NVTD800KMFV869YNZED6","testing-actions","Use when writing or reviewing tests for @effected\u002Fgithub-actions, @effected\u002Fgithub, @effected\u002Fsbom or @effected\u002Fcommands — stubbing the GitHub API, writing a service's layerTest or makeTest double, testing the pre\u002Fmain\u002Fpost lifecycle through Action.run, or debugging why a test hits the real network or hangs.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Ftesting-actions\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M780NPDSGFC0FCP7696NW11J","supply-chain-attestation","Use when generating a CycloneDX SBOM, checking NTIA minimum elements, building an in-toto statement or a SLSA provenance predicate, signing into a Sigstore DSSE bundle, or uploading an attestation to GitHub.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fsupply-chain-attestation\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M780NGP4QNZDH8T8Q8WZ18SA","structuring-an-action","Use when laying out a new GitHub Action repository on the @effected suite, deciding where a piece of code belongs (an entry point, a step, a shared service, a shim), or reviewing an existing action's file structure against the canonical shape.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fstructuring-an-action\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M780NCD52H1Y03FS83WJ8BT5","running-commands-and-tools","Use when running a subprocess in Effect v4, spawning a command, capturing stdout\u002Fstderr\u002Fexit code, checking whether a CLI tool is installed or which copy to run, running a package-manager script through the project's launcher, detaching a background process, or redacting a secret from argv or captured output.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Frunning-commands-and-tools\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M780N823DWNRMSY5X2NT5MSR","release-and-publish","Use when publishing a package to npm, reading the npm registry from Effect v4, checking whether a version is already published, cutting a release tag or GitHub release from an action, applying a release-age gate, or deriving tracking tags for GitHub Actions distribution.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Frelease-and-publish\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M780MXRF6H20KCESTSSFB3HQ","hardening-a-parser-port","Use when porting or writing a recursive-descent parser, lexer, or tree-walker over untrusted text in the @effected monorepo — the class of hardening the cloud reviewer scans for on every migration. Covers stack-overflow depth guards (on EVERY recursion surface, which a facade has N of — not two), numeric bound guards that must reject NaN and non-integers, code-point range checks scoped to formats with wide escapes, prototype-pollution, control-character rejection, and the invariant that malformed input must fail through the typed error channel, never as an unhandled defect.","https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fhardening-a-parser-port\u002FSKILL.md",[],[]]