dxkit-extensionslisted
Install: claude install-skill vyuh-labs/dxkit
# dxkit-extensions
An **extension** is a script the repo already owns — any language — that dxkit
orchestrates: it runs at refresh time, emits one JSON document, and dxkit
validates it and routes it through the same machines native output gets.
Before writing one, climb the ladder from the bottom — most needs stop early:
1. **Config** — a `.dxkit/policy.json` key. No code.
2. **Declared artifact** — you already have a Postman collection, Pact file,
`.http` requests, HAR capture, or OpenAPI document? Declare it:
```jsonc
// .dxkit/policy.json
{
"flow": {
"sources": [
{ "kind": "postman", "path": "collections/checkout.postman_collection.json" },
{ "kind": "pact", "path": "pacts/web-api.json" },
{ "kind": "har", "path": "fixtures/session.har" },
],
},
}
```
Zero code; the artifacts join the flow map and gate like extracted calls.
3. **External extension** (this skill's core) — a committed manifest points at
your existing script.
4. **TypeScript plugin** — only for what the rungs above can't express: a
bespoke HTTP-client wrapper flow can't see (`httpFlowDialect`), a custom
artifact format for `flow.sources` (`contractReader`), base-URL logic
beyond `stripUrlPrefixes` (`urlNormalizer`), or an assertion over the
gathered flow model (`integrationVerifier`). Scaffold with
`vyuh-dxkit extensions init <name> --plugin`; the dxkit-author-extension
skill writes one from a prose description.