design-patterns
Use when choosing or applying a proven architecture pattern for a project built on Effect v4 / 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. Also use when: carrier package, meta-package, one package to install, bins missing from node_modules/.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
Pinned to revision 500242f8d91c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/design-patterns/SKILL.md
- skills/design-patterns/references/carrier-app-and-schemas.md
- skills/design-patterns/references/carrier-case-studies.md
- skills/design-patterns/references/carrier-closure.md
- skills/design-patterns/references/carrier-entry-contract.md
- skills/design-patterns/references/carrier-package.md
- skills/design-patterns/references/carrier-plugin-loader.md
- skills/design-patterns/references/carrier-verification.md
- skills/design-patterns/references/carrier-version-threading.md
Every link opens the file at its source, pinned to the revision this page describes.