forze-deps-modules
Installation
SKILL.md
Forze dependency modules
Use when authoring or reviewing infrastructure wiring. For application bootstrap, see forze-wiring. For logical names and StrEnum route values, see forze-specs-infrastructure.
Container model
Deps has two registration modes:
| Mode | Shape | Use when |
|---|---|---|
Deps.plain({DepKey: value}) |
one provider per key | shared clients, secrets, idempotency defaults |
Deps.routed({DepKey: {route: value}}) |
one provider per key + route | specs resolved by spec.name |
Deps.routed_group({...}, routes={...}) |
same provider for many routes | one backend supports several logical resources |
Deps.merge(...) raises CoreError on duplicate plain keys, plain-vs-routed conflicts, or duplicate routed keys. Let it fail fast instead of silently overriding providers.
Module shape
Built-in modules are generic over K: str | StrEnum. Follow that pattern so callers can use StrEnum names.