← Product & App ArchitectCONTENT HISTORY
WHAT CHANGED
Update to Product & App Architect
Snapshot Nov 3, 2026 · 00:12 UTC · version 0.2.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Product & App Architect and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"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"
}SHA-256 of public snapshot: 05ac7c409e9a0092efc49e0aa614e459b11180191df3d25c8557b2a27c8f497b