Documenting Contracts

by riekelt85e53729dd95No license28 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Use when documenting an HTTP API, message payloads, queue contracts, DTOs, file formats, or webhooks - or when writing the api-reference of a legacy campaign, or when callers keep asking what a field means or which errors an endpoint returns. Encodes the four detail levels, the DTO-first catalog, wire types with source anchors, the generated-spec one-home rule, and omitted-versus-null semantics. Use whenever a machine interface needs documenting for its callers, even if nobody says "API docs".

  1. 85e53729dd95Currentcommit 85e5372Published Oct 8, 2026

Source and attribution

Source:riekelt/technical-writerinplugins/technical-writer/skills/documenting-contractsat commit85e5372

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal