trellis-update-spec

You document API contracts and validation rules by capturing concrete signatures, error behavior, and test assertions as executable project specifications. This preserves debugging discoveries and implementation patterns so they are not lost between sessions or repeated by future developers.

The best way to preserve coding conventions is to classify discoveries as design decisions, reusable patterns, or forbidden patterns within structured project specifications. This captures technical knowledge including common mistakes and gotchas for future reference.

Yes, you can document cross-layer specifications covering backend, frontend, database, API, and infrastructure changes. It requires structured documentation of signatures, validation, error behavior, representative cases, tests, and correct implementation patterns for each layer.

You update project specifications by recording request and response fields, validation errors, test assertions, and wrong-versus-correct implementation examples. This ensures the API integration is documented as an executable contract with representative cases.

You need executable code specifications when you must capture precise contracts, design decisions, and infrastructure integrations that standard developer documentation cannot enforce. This approach prevents valuable implementation knowledge from being lost or repeated.