{"id":77030,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.961Z","digest":"05ac7c409e9a0092efc49e0aa614e459b11180191df3d25c8557b2a27c8f497b","against":null,"payload":{"description":"Specify domain data, external integrations and API contracts for a proposed application.","included_files":[],"name":"design-data-apis","skill_md_contents":"---\nname: design-data-apis\ndescription: Specify domain data, external integrations and API contracts for a proposed application.\n---\n\n# Design Data Apis\n\n## When to use\nSpecify domain data, external integrations and API contracts for a proposed application.\n\n## Workflow\nDerive data ownership and mutations from concrete flows; identify cardinality, source of truth, tenancy, permission boundaries, lifecycle and retention. Define APIs with schemas, idempotency, versioning, rate limits, error and retry semantics; account for migrations and rollback. Preserve existing contracts where known. Don't invent accessible service endpoints, datasets, and code files.\n\nUse `../../references/data-api-contracts.md` and `../../templates/data-api-contract.md`. Output contract tables and critical invariants, not unrequested implementation code.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/data-api-contracts.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}