Review database workspaces, projects, production databases, backup evidence, usage signals, and connections with the original records and related browser context beside them. This lets the team distinguish an observation from a decision.
Strawberry works from the Prisma Management API workspace in your tab. It can prepare a review, handover, or exception queue without treating a live write as automatic.
01
Start with the records that can change the next decision.
A Prisma database workspace can hide the production connection, backup status, or usage signal that needs an owner to investigate before it becomes an incident. Read the selected Prisma Management API views together with their visible history, then turn the exceptions into a short evidence-backed queue.
02
Put the context next to the record before proposing a change.
The decisive Prisma detail may be in a production database view, backup record, connection setting, or the incident note that explains why a usage signal changed. Put those records together before proposing a database action, so the reviewer can assess the production consequence rather than merely read a status field.
03
Make every handover specific enough to act on.
A Prisma handover should preserve the affected project or database, connection or backup evidence, responsible owner, and the decision needed before a production change. That keeps the next engineer from reconstructing a database risk from scattered project and connection screens.
04
Review production readiness when the team can still act on them.
A weekly Prisma review is valuable when it reaches the database owner before backup, connection, or usage anomalies become production incidents. Capture the exact Prisma Management API checks in a skill, then let a Friday at 14:00 routine assemble the evidence before the operating deadline arrives.
Yes. It can use the Prisma Management API browser context you provide to inspect the live workspace and prepare a review alongside related tabs or files.
It can prepare a Prisma review in the browser, while database configuration, connection, backup, and production-access changes remain for your approval.
Yes. Capture the Prisma Management API-specific checks in a skill and schedule a routine at the cadence that matches the team’s real operating deadline.
No. ### What should I verify before changing Prisma Management API? Before changing Prisma, check the live database or project, backup and connection evidence, anticipated production effect, and the authorisation for that exact action.
Prisma Management API Strawberry