Downstream Exports

How our content reaches hosts that are not Claude Code: the host adapters, what each host expects a package to look like, how the compiler renders harnesses from templates, how a neutral policy gets a host implementation, when a fingerprinted semantic override is the right answer, and the content that deliberately keeps host-as-subject vocabulary. TRIGGER WHEN: changing an adapter layout, capability binding, coordination strategy, harness template, policy implementation or override, or diagnosing why one host's package came out differently from another's. DO NOT TRIGGER WHEN: pulling content IN from an external repo (use `external-repo-intake` or `upstream-sync`), or editing plugin behaviour, which lives in the kernel under `plugins/` and is host-neutral by rule.

acaprino Updated 10 repo stars

File contents

acaprino/daodan commit 3aca6d8c9a

Frequently asked questions

npx get-skill add acaprino/downstream-exports-2