What problem does it solve? Working with @prisma/composer requires understanding non-obvious concepts—typed service declarations, provision wiring, secret binding channels, replay-only migrations, and converge-based deploys—that cannot be discovered from the CLI's help output or inferred from code alone. ## Core Features & Use Cases - Conceptual grounding: Explains declarations (services, resources, modules), typed ports, contracts and RPC, the two input channels (deps vs input), and the build/deploy model. - Operational guidance: Covers local development with dev, testing via mockService and bootstrapService, database migration loops, stage management, and destroy semantics. - Failure diagnosis: Documents known failure modes such as effect version conflicts, 401s on unwired RPC calls, MIGRATION_PATH_NOT_FOUND, and scale-to-zero connection resets. - Use Case: When deploying a Prisma Cloud app whose deploy fails with a connection contract refusal, consult this Skill to understand why the producer's outputs must satisfy the declared connection params and how to fix the correct end. ## Quick Start Explain how to wire a Postgres database dependency into a Prisma Composer service and read it at runtime.