engineer-sdklisted
Install: claude install-skill Veritas-Quaesitor/vq-sdk-engineering-skill
# Engineer SDK
## Outcome
Enable a clearly defined capability through the path of least resistance, pain, risk, and effort for the SDK consumer, while keeping the implementation maintainable, testable, secure, configurable, and operationally supportable.
An SDK is a product-facing integration layer that packages the reusable knowledge, protocol details, lifecycle handling, validation, transport behavior, models, errors, and safe defaults required for another party to enable a capability reliably. The consumer may be a customer, client, merchant, partner, application team, developer, or another SDK. Internal modularity is valuable, but it is not the product; the product is the consumer experience and the reliable capability it enables.
## Non-negotiable rules
1. **Consumer first.** Write the intended install/start/use example before selecting architecture. Measure complexity from the consumer's point of view, never by repository file count.
2. **Agnosticism.** Assume no language, framework, runtime, source shape, delivery format, package registry, hosting provider, or distribution visibility. Do not assume npm, Maven, NuGet, PyPI, crates.io, a CDN, IIFE, ESM, CommonJS, GitHub, or generated clients. Discover what consumers actually use.
3. **Version neutrality.** Modernization does not inherently mean `v2`, semantic versioning, or a major release. Use *current contract*, *target contract*, *existing implementation*, *modernized implementation*, *compatibility layer*, and *