[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M780F7KEBBC0C2C9YA7EQN8P":3,"skill-same:01M780F7KEBBC0C2C9YA7EQN8P":80},{"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},"01M780F7KEBBC0C2C9YA7EQN8P","design-patterns",null,"Use when choosing or applying a proven architecture pattern for a project built on Effect v4 \u002F the @effected kit — splitting a tool into cli + mcp + lsp packages, deciding how a monorepo ships its bins, making \"install one package\" true for a consumer, a Claude Code or Copilot plugin launching a project's own bins, or threading one version identity through several front ends. This skill indexes patterns as loadable references; consult it before inventing an architecture the kit's own consumers have already worked out.","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\u002Fskills\u002Fdesign-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: design-patterns\ndescription: Use when choosing or applying a proven architecture pattern for a project built on Effect v4 \u002F the @effected kit — splitting a tool into cli + mcp + lsp packages, deciding how a monorepo ships its bins, making \"install one package\" true for a consumer, a Claude Code or Copilot plugin launching a project's own bins, or threading one version identity through several front ends. This skill indexes patterns as loadable references; consult it before inventing an architecture the kit's own consumers have already worked out.\nwhen_to_use: carrier package, meta-package, one package to install, bins missing from node_modules\u002F.bin, cli + mcp + lsp split, front end vs engine, keeping the package graph acyclic, plugin loader script, version threading, distribution, engine_version, manifest DAG test, packed-install e2e, tool closure, pin kit dependencies exactly, workspace:* vs workspace:^ for a tool, tool on an older kit release, two copies of a kit package, does not provide an export named, breaking peer floor\n---\n\n# Design patterns\n\nProven architecture patterns for building on Effect v4 and the `@effected`\nkit, distilled from real multi-package tools and indexed as loadable\nreferences. This skill routes; depth lives in `references\u002F`.\n\n## Pattern index\n\n| Pattern | Reach for it when | Reference |\n| --- | --- | --- |\n| Carrier package — core\u002Fengine\u002Ffront ends → carrier | a tool ships more than one bin (CLI, MCP server, LSP server, …) and you want \"install one package\" to be true, or you're debugging why a consumer's `node_modules\u002F.bin` is missing a bin that resolves fine as a dependency | [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md), [carrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md), [carrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md), [carrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md), [carrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md), [carrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md), [carrier-app-and-schemas.md](.\u002Freferences\u002Fcarrier-app-and-schemas.md) (optional), [carrier-case-studies.md](.\u002Freferences\u002Fcarrier-case-studies.md) |\n\nMore rows land here as more patterns are distilled. A pattern earns a row\nonce it has shipped in more than one real tool and the trade-offs are\nsettled, not on first use.\n\n## Kit exports\n\nThe carrier pattern's references teach the shape; where a piece of that\nshape has shipped as a kit export, reach for the export instead of\nhand-rolling the recipe again.\n\n| construct | import | reach for it when |\n| --- | --- | --- |\n| `CurrentDistribution`, `DistributionField`, `distributionSuffix` | `@effected\u002Fkit` | threading which meta-package a front end was installed through |\n| `LaunchContext` | `@effected\u002Fkit` | resolving an agent-launched project directory from `argv`\u002F`env`\u002F`cwd` |\n| `CliRuntime.main` | `@effected\u002Fcli-kit` | assembling a CLI front end's `main.ts` |\n| `McpStdio` | `@effected\u002Fmcp-kit` | assembling an MCP front end's `main.ts` — launch, stdio boundary, teardown |\n| `ProcessGuard`, `McpGuard` | `@effected\u002Fkit\u002Fguard`, `@effected\u002Fmcp-kit\u002Fguard` | crash guards in a server front end's `main.ts` before its graph loads — any transport (an LSP), or MCP with the launch built in |\n| `WorkspaceLayering`, `LayerPolicy` | `@effected\u002Fworkspaces\u002Ftesting` | the manifest DAG test that holds the package graph to a committed policy |\n| `SourceBoundary` | `@effected\u002Fworkspaces\u002Ftesting` | a package's own `process`\u002Fimport boundary test |\n| `PackedInstall` | `@effected\u002Fworkspaces\u002Ftesting` | the cross-package-manager packed-install e2e |\n| `McpProbe` | `@effected\u002Fmcp-kit\u002Ftesting` | the MCP half of a packed-install proof |\n\n## Standards\n\n- **Name the layer, not the file.** \"Front end\", \"engine\", \"carrier\" are\n  roles a package plays, not folder names — a repo may fold a role into an\n  existing package (the carrier as a library) as long as the edges still\n  point one way.\n- **Keep every edge pointing down.** A pattern that needs a same-layer or\n  upward edge to work is the wrong shape for the problem, not a reason to\n  add an exception.\n- **Verify a pattern against a real tool before applying it**, the same\n  evidence discipline as any other platform claim — a pattern description\n  is a distillation, not a substitute for reading the case study it came\n  from.\n- **Prefer adding a package over introducing a back-edge.** Smaller,\n  focused packages composed acyclically have proven more reliable than a\n  shared package importing \"up\" for convenience.\n\n## Footguns\n\n- Bin-linking is direct-dependency-only in every package manager — see\n  [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md) for why hoisting\n  and hand-rolled hoist patterns don't fix it.\n- A carrier's front ends belong in `dependencies`, never\n  `peerDependencies` — see\n  [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md).\n- A tool package that takes the kit at caret ranges changes under its own\n  version and can bind a kit peer across its closure; pin every kit\n  dependency of a tool package exactly — see\n  [carrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md).\n- An MCP `main.ts` that imports its server graph statically runs that graph\n  before its crash guards exist: Node prints the throw and exits `1` on its\n  own, but the server's own handler never runs — `McpStdio.launch` does not\n  remove this requirement, it sits around it — see\n  [carrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md) and\n  `effect-v4-mcp`'s `server-wiring.md#crash-guards`.\n- A package.json read for \"my own version\" reports the wrong package's\n  version once code moves to a shared engine — `CurrentDistribution` fixes\n  the identity-threading half of this, not the build-time-literal half —\n  see [carrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md).\n- A plugin loader that dispatches through `pnpm exec` \u002F `bunx` \u002F\n  `npm exec` resolves bins differently per package manager — see\n  [carrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md).\n- A manifest DAG test with no positive-control fixture can pass while\n  checking nothing — `WorkspaceLayering`'s own `edgeCount` guard is that\n  control; a hand-rolled `LAYER_RANKS` table has to add it itself — see\n  [carrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md).\n\n## Additional resources\n\n- [references\u002Fcarrier-package.md](.\u002Freferences\u002Fcarrier-package.md) — the\n  problem the carrier pattern solves, its roles and edge direction, the\n  carrier-as-library deviation, the dependencies-vs-peers rule, and the\n  release model. Load when: deciding whether a multi-bin tool needs this\n  shape at all, or reviewing a package's `dependencies` vs\n  `peerDependencies` split.\n- [references\u002Fcarrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md)\n  — the four-file front-end contract (`bin.ts`\u002F`main.ts`\u002F`index.ts`\u002F`version.ts`),\n  the carrier's bin shims, who declares a bin (carrier-only, recommended;\n  or shared, at the cost of provenance), and the MCP crash-guard\n  requirement. Load\n  when: scaffolding a new front-end package or a carrier's bin shims.\n- [references\u002Fcarrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md)\n  — build-time version literals, the `Distribution` `Context.Reference`,\n  `engine_version` as the comparable version, and the `--version` format.\n  Load when: a tool needs to report which meta-package it was installed\n  through, or two front ends disagree about \"the version.\"\n- [references\u002Fcarrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md)\n  — the Claude Code \u002F Copilot plugin loader shape (`node_modules\u002F.bin`\n  first, install hint, major-pinned `npx -p` fallback through the carrier)\n  and the hook CLI\n  resolution order. Load when: writing or reviewing a plugin's\n  `mcpServers`\u002F`lspServers` loader script or a hook that shells out to a\n  project's own CLI.\n- [references\u002Fcarrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md)\n  — the manifest DAG test with non-vacuity, source boundary tests, and the\n  packed-install e2e across package managers. Load when: adding the\n  repo-shape checks to a multi-package tool — uses the kit's checks, not\n  copied tests.\n- [references\u002Fcarrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md) — a\n  tool owns its dependency closure: exact kit pins on every tool package,\n  why a library keeps carets and peers instead, what pinning does not seal,\n  and the breaking-floor rule for a library's own releases. Load when:\n  choosing `workspace:*` or `workspace:^` (or exact or caret) for a tool\n  package, a tool breaks beside a repository on a newer kit release, or a\n  library release moves a peer floor.\n- [references\u002Fcarrier-app-and-schemas.md](.\u002Freferences\u002Fcarrier-app-and-schemas.md)\n  — the OPTIONAL extension: where the app layer (platform + config\n  discovery) and a published config-file JSON Schema belong — core owns\n  shape\u002Fversion\u002Fhosted identity, the engine owns platform + discovery,\n  front ends only pass in process-derived inputs. Load when: the tool has\n  a user config file a person hand-edits, or publishes a JSON Schema for\n  it — cross-links `building-schemastore-schemas` for the generation and\n  drift-gate mechanics rather than re-teaching them here.\n- [references\u002Fcarrier-case-studies.md](.\u002Freferences\u002Fcarrier-case-studies.md)\n  — okfit, vitest-agent and systems: what each does best, what each is\n  missing, and the deviations each made and why. Load when: you want a\n  worked, citable example instead of the prescriptive rule alone.\n\n## Related skills\n\n- **`effect-v4-cli`** and **`effect-v4-mcp`** own each front end's own depth\n  — assembling `main.ts`, exit codes, protocol wiring, tool definitions and\n  testing. This skill teaches the shape a multi-front-end tool takes; the\n  two front-end skills teach what happens inside each front end. Knowledge\n  stays split rather than duplicated across all three.\n","# Design patterns\n\nProven architecture patterns for building on Effect v4 and the `@effected`\nkit, distilled from real multi-package tools and indexed as loadable\nreferences. This skill routes; depth lives in `references\u002F`.\n\n## Pattern index\n\n| Pattern | Reach for it when | Reference |\n| --- | --- | --- |\n| Carrier package — core\u002Fengine\u002Ffront ends → carrier | a tool ships more than one bin (CLI, MCP server, LSP server, …) and you want \"install one package\" to be true, or you're debugging why a consumer's `node_modules\u002F.bin` is missing a bin that resolves fine as a dependency | [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md), [carrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md), [carrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md), [carrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md), [carrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md), [carrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md), [carrier-app-and-schemas.md](.\u002Freferences\u002Fcarrier-app-and-schemas.md) (optional), [carrier-case-studies.md](.\u002Freferences\u002Fcarrier-case-studies.md) |\n\nMore rows land here as more patterns are distilled. A pattern earns a row\nonce it has shipped in more than one real tool and the trade-offs are\nsettled, not on first use.\n\n## Kit exports\n\nThe carrier pattern's references teach the shape; where a piece of that\nshape has shipped as a kit export, reach for the export instead of\nhand-rolling the recipe again.\n\n| construct | import | reach for it when |\n| --- | --- | --- |\n| `CurrentDistribution`, `DistributionField`, `distributionSuffix` | `@effected\u002Fkit` | threading which meta-package a front end was installed through |\n| `LaunchContext` | `@effected\u002Fkit` | resolving an agent-launched project directory from `argv`\u002F`env`\u002F`cwd` |\n| `CliRuntime.main` | `@effected\u002Fcli-kit` | assembling a CLI front end's `main.ts` |\n| `McpStdio` | `@effected\u002Fmcp-kit` | assembling an MCP front end's `main.ts` — launch, stdio boundary, teardown |\n| `ProcessGuard`, `McpGuard` | `@effected\u002Fkit\u002Fguard`, `@effected\u002Fmcp-kit\u002Fguard` | crash guards in a server front end's `main.ts` before its graph loads — any transport (an LSP), or MCP with the launch built in |\n| `WorkspaceLayering`, `LayerPolicy` | `@effected\u002Fworkspaces\u002Ftesting` | the manifest DAG test that holds the package graph to a committed policy |\n| `SourceBoundary` | `@effected\u002Fworkspaces\u002Ftesting` | a package's own `process`\u002Fimport boundary test |\n| `PackedInstall` | `@effected\u002Fworkspaces\u002Ftesting` | the cross-package-manager packed-install e2e |\n| `McpProbe` | `@effected\u002Fmcp-kit\u002Ftesting` | the MCP half of a packed-install proof |\n\n## Standards\n\n- **Name the layer, not the file.** \"Front end\", \"engine\", \"carrier\" are\n  roles a package plays, not folder names — a repo may fold a role into an\n  existing package (the carrier as a library) as long as the edges still\n  point one way.\n- **Keep every edge pointing down.** A pattern that needs a same-layer or\n  upward edge to work is the wrong shape for the problem, not a reason to\n  add an exception.\n- **Verify a pattern against a real tool before applying it**, the same\n  evidence discipline as any other platform claim — a pattern description\n  is a distillation, not a substitute for reading the case study it came\n  from.\n- **Prefer adding a package over introducing a back-edge.** Smaller,\n  focused packages composed acyclically have proven more reliable than a\n  shared package importing \"up\" for convenience.\n\n## Footguns\n\n- Bin-linking is direct-dependency-only in every package manager — see\n  [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md) for why hoisting\n  and hand-rolled hoist patterns don't fix it.\n- A carrier's front ends belong in `dependencies`, never\n  `peerDependencies` — see\n  [carrier-package.md](.\u002Freferences\u002Fcarrier-package.md).\n- A tool package that takes the kit at caret ranges changes under its own\n  version and can bind a kit peer across its closure; pin every kit\n  dependency of a tool package exactly — see\n  [carrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md).\n- An MCP `main.ts` that imports its server graph statically runs that graph\n  before its crash guards exist: Node prints the throw and exits `1` on its\n  own, but the server's own handler never runs — `McpStdio.launch` does not\n  remove this requirement, it sits around it — see\n  [carrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md) and\n  `effect-v4-mcp`'s `server-wiring.md#crash-guards`.\n- A package.json read for \"my own version\" reports the wrong package's\n  version once code moves to a shared engine — `CurrentDistribution` fixes\n  the identity-threading half of this, not the build-time-literal half —\n  see [carrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md).\n- A plugin loader that dispatches through `pnpm exec` \u002F `bunx` \u002F\n  `npm exec` resolves bins differently per package manager — see\n  [carrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md).\n- A manifest DAG test with no positive-control fixture can pass while\n  checking nothing — `WorkspaceLayering`'s own `edgeCount` guard is that\n  control; a hand-rolled `LAYER_RANKS` table has to add it itself — see\n  [carrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md).\n\n## Additional resources\n\n- [references\u002Fcarrier-package.md](.\u002Freferences\u002Fcarrier-package.md) — the\n  problem the carrier pattern solves, its roles and edge direction, the\n  carrier-as-library deviation, the dependencies-vs-peers rule, and the\n  release model. Load when: deciding whether a multi-bin tool needs this\n  shape at all, or reviewing a package's `dependencies` vs\n  `peerDependencies` split.\n- [references\u002Fcarrier-entry-contract.md](.\u002Freferences\u002Fcarrier-entry-contract.md)\n  — the four-file front-end contract (`bin.ts`\u002F`main.ts`\u002F`index.ts`\u002F`version.ts`),\n  the carrier's bin shims, who declares a bin (carrier-only, recommended;\n  or shared, at the cost of provenance), and the MCP crash-guard\n  requirement. Load\n  when: scaffolding a new front-end package or a carrier's bin shims.\n- [references\u002Fcarrier-version-threading.md](.\u002Freferences\u002Fcarrier-version-threading.md)\n  — build-time version literals, the `Distribution` `Context.Reference`,\n  `engine_version` as the comparable version, and the `--version` format.\n  Load when: a tool needs to report which meta-package it was installed\n  through, or two front ends disagree about \"the version.\"\n- [references\u002Fcarrier-plugin-loader.md](.\u002Freferences\u002Fcarrier-plugin-loader.md)\n  — the Claude Code \u002F Copilot plugin loader shape (`node_modules\u002F.bin`\n  first, install hint, major-pinned `npx -p` fallback through the carrier)\n  and the hook CLI\n  resolution order. Load when: writing or reviewing a plugin's\n  `mcpServers`\u002F`lspServers` loader script or a hook that shells out to a\n  project's own CLI.\n- [references\u002Fcarrier-verification.md](.\u002Freferences\u002Fcarrier-verification.md)\n  — the manifest DAG test with non-vacuity, source boundary tests, and the\n  packed-install e2e across package managers. Load when: adding the\n  repo-shape checks to a multi-package tool — uses the kit's checks, not\n  copied tests.\n- [references\u002Fcarrier-closure.md](.\u002Freferences\u002Fcarrier-closure.md) — a\n  tool owns its dependency closure: exact kit pins on every tool package,\n  why a library keeps carets and peers instead, what pinning does not seal,\n  and the breaking-floor rule for a library's own releases. Load when:\n  choosing `workspace:*` or `workspace:^` (or exact or caret) for a tool\n  package, a tool breaks beside a repository on a newer kit release, or a\n  library release moves a peer floor.\n- [references\u002Fcarrier-app-and-schemas.md](.\u002Freferences\u002Fcarrier-app-and-schemas.md)\n  — the OPTIONAL extension: where the app layer (platform + config\n  discovery) and a published config-file JSON Schema belong — core owns\n  shape\u002Fversion\u002Fhosted identity, the engine owns platform + discovery,\n  front ends only pass in process-derived inputs. Load when: the tool has\n  a user config file a person hand-edits, or publishes a JSON Schema for\n  it — cross-links `building-schemastore-schemas` for the generation and\n  drift-gate mechanics rather than re-teaching them here.\n- [references\u002Fcarrier-case-studies.md](.\u002Freferences\u002Fcarrier-case-studies.md)\n  — okfit, vitest-agent and systems: what each does best, what each is\n  missing, and the deviations each made and why. Load when: you want a\n  worked, citable example instead of the prescriptive rule alone.\n\n## Related skills\n\n- **`effect-v4-cli`** and **`effect-v4-mcp`** own each front end's own depth\n  — assembling `main.ts`, exit codes, protocol wiring, tool definitions and\n  testing. This skill teaches the shape a multi-front-end tool takes; the\n  two front-end skills teach what happens inside each front end. Knowledge\n  stays split rather than duplicated across all three.\n",{"name":5,"description":7,"when_to_use":24},"carrier package, meta-package, one package to install, bins missing from node_modules\u002F.bin, cli + mcp + lsp split, front end vs engine, keeping the package graph acyclic, plugin loader script, version threading, distribution, engine_version, manifest DAG test, packed-install e2e, tool closure, pin kit dependencies exactly, workspace:* vs workspace:^ for a tool, tool on an older kit release, two copies of a kit package, does not provide an export named, breaking peer floor","main","0b59ef50d270bac16abbb7729cf4326d16de63f9","plugin\u002Fskills\u002Fdesign-patterns",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 design-patterns",{"tool":38,"command":39},"bunx","bunx skills add spencerbeggs\u002Feffected --skill design-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add spencerbeggs\u002Feffected --skill design-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002FSKILL.md",true,[46,52,56,60,64,68,72,76],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcarrier-app-and-schemas.md","REFERENCE","参考文档",14815,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-app-and-schemas.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcarrier-case-studies.md",11039,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-case-studies.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcarrier-closure.md",5367,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-closure.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fcarrier-entry-contract.md",10472,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-entry-contract.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fcarrier-package.md",7835,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-package.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fcarrier-plugin-loader.md",9175,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-plugin-loader.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fcarrier-verification.md",26659,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-verification.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcarrier-version-threading.md",8026,"https:\u002F\u002Fgithub.com\u002Fspencerbeggs\u002Feffected\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fdesign-patterns\u002Freferences\u002Fcarrier-version-threading.md",[81,88,95,102,109,116],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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",[],[]]