跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
开发与测试

distribution

Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use `tools` or `translate`. Do NOT use for recording what got installed on a project — use `framework`.

ai-driven-dev · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ai-driven-dev/framework --skill distribution

技能说明


name: distribution description: > Owns where plugin and marketplace content comes from and how it is fetched, under src/contexts/distribution/ — marketplace registration, catalog parsing, and the ports/adapters that reach git and HTTP. Use when adding a new marketplace source kind, a catalog parser for a foreign format, or a fetch/cache/trust-store adapter. Do NOT use for what a tool does with fetched content — use tools or translate. Do NOT use for recording what got installed on a project — use framework.

Distribution

distribution is a leaf: it depends on kernel only, and knows no tool and no manifest. It answers exactly one question — where does content come from, and how is it fetched — for whoever asks. framework is the only context that reaches it (framework → distribution); a plugin's own content and how it gets translated are someone else's job once it has arrived here.

What goes in

ConceptLocation
A marketplace registration (name, source, scope, staleness)domain/marketplace.ts, domain/marketplace-source-mode.ts
A cached catalog fetchdomain/ports/marketplace-cache.ts
The plugin catalog shapedomain/catalog.ts (the Claude-shaped parser lives here too)
A reader for a non-Claude catalog shapedomain/catalog-parsers/
A port this context's callers holddomain/ports/ — registry, cache, trust-store, catalog-repository, fetcher, raw-catalog-fetcher
Add / list / refresh / register / resolve / fetch a marketplace sourceapplication/
The concrete adapter behind one of the six portsinfrastructure/

How

  • This context is a leaf by construction: it must never gain an edge to tools, translate, or framework — tests/architecture/context-graph.arch.test.ts enforces the chain (framework → distribution, plus everything to kernel) and fails the build the moment a new edge appears. If a change seems to need one, the orchestration belongs to the caller (framework), not here — see BASELINE in tests/architecture/helpers.ts for the one documented exception, distribution->framework, and the comment there that explains it (marketplace add --overwrite removing before adding), which is framework work that has not yet been moved out.
  • A port here follows the port/adapter rule in .claude/rules/00-architecture/: interface only, ≤5 methods, no null in the return type unless "not found" is genuinely a normal domain state (documented per-port, not assumed).
  • An adapter owns every technical constant for its integration (API base URLs, cache TTLs, error-pattern regexes for classifying a third-party failure) — none of that belongs in a port, a use-case, or a domain model. try/catch inside an adapter exists only to translate a raw error into a typed one from kernel/errors.ts.
  • A new foreign catalog shape gets its own parser in domain/catalog-parsers/, producing the same PluginCatalog/PluginCatalogEntry shape the Claude parser produces — callers above this context never branch on which format a catalog came from.
  • Follow the use-case rule in .claude/rules/00-architecture/ for the application layer's shape.

Public surface

Nothing outside contexts/distribution/ may import a module this context has not declared public — tests/architecture/context-boundary.arch.test.ts holds the list (PUBLIC_MODULES.distribution). Measured at extraction, ten modules were reached from outside and not one was an adapter: the adapters are wired by the composition root (runtime/wiring/distribution.ts) alone, and stay internal for that reason. A module that exposes its own plumbing to a caller outside the composition root is not a leaf context anymore — keep new adapters unreachable from outside.

How it's tested

  • tests/contexts/distribution/ mirrors src/contexts/distribution/ — domain models and application use-cases are unit-tier; adapters against a real temp filesystem or a mocked network boundary are integration-tier. See the test skill for tier conventions.
  • A new catalog parser needs a fixture of the real foreign format and a test asserting the parsed PluginCatalog matches what the Claude-shaped parser would produce for an equivalent catalog.