القائمة
A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | planetscale-best-practices-matrix |
| description | A concise feature matrix for deciding which PlanetScale safety, observability, and automation recommendations apply by engine. |
Map database findings to recommended PlanetScale features. Use this to ensure the assessment does not miss major safety and operational surfaces.
Recommend for every production database:
sort=cpuTime on the Insights API)
when diagnosing CPU pressure.insights/tags, insights/tags/summaries) on both engines, plus
tag:key:value filtering and per-execution tag drill-down in the Vitess
dashboard.Recommend for operational events:
Recommend:
AGENTS.md.Recommend:
Recommend:
Recommend for production branches and staging branches that accept deploy requests.
Recommend for schema changes into protected branches.
Recommend documenting who may use "force cutover now" for deploy requests delayed by long-running transactions. It stops running transactions to finish schema cutover, so frequent use should trigger workload review before enabling aggressive cutover as the database default.
Recommend for production deploy requests in multi-admin organizations.
Recommend when cutover timing and human control matter.
Recommend documenting revert responsibilities and the application rollback relationship.
Recommend production, staging, and short-lived development branches with safe migrations on protected targets.
Recommend when query patterns or growth suggest shard-awareness problems. Do not reshard automatically.
Recommend for application servers instead of default role. If roles are managed
by Terraform and passwords should stay outside Terraform state, prefer
planetscale_postgres_redacted_branch_role plus a separate password reset and
secret-manager storage path.
Recommend for application roles after evaluation, especially to block accidental full-table update/delete mistakes.
Recommend for resource isolation of agents, exports, reports, workers, integrations, BI, and known expensive fingerprints.
Recommend verifying retention and restore drill coverage. If Terraform is the customer's source of truth, recommend managing backup policies there so backup posture changes are reviewed as infrastructure code.
Recommend where connection churn or serverless/edge behavior creates pressure, subject to transaction-pooling limitations.
Recommend for customers requiring private network posture or reduced public exposure. Treat changes as production-risking.
Recommend only when use case is clear and restart/activation impact is accepted.
Include auto_explain when automatic plan logging for slow queries would
materially improve diagnosis and the resulting log volume is acceptable.
If Terraform manages Postgres branch parameters or supported extensions, keep
that source of truth aligned with approved dashboard/API changes.
Recommend inspecting pscale branch connections top during active connection
pressure incidents to identify sessions, blockers, and idle-in-transaction
roots without relying on normal database connection capacity.
For each matrix item, mark:
End with:
“No changes have been applied.”
Collect read-only evidence about PlanetScale org, database, branches, webhooks, backups, roles, Insights, recommendations, and traffic configuration.
Review a PlanetScale Vitess database for safe migrations, deploy requests, schema recommendations, Insights, webhooks, and operational safety.
Review PlanetScale Postgres for Traffic Control, query tags, roles, pg_strict, backups/PITR, private connectivity, webhooks, branches, and safe agent operation.
Use PlanetScale Insights and SQLCommenter-style query tags to attribute database load, identify risky queries, and prepare safe Traffic Control or schema recommendations.
Configure safe agent behavior around PlanetScale MCP, Insights, schema recommendations, and repository work without autonomous production mutation.
Use the PlanetScale CLI (pscale) from automated agents with --format json, auth check, pscale sql, and per-command --force. Run before other PlanetScale skills when driving pscale directly. Use when the user asks to automate pscale, run CLI commands headless, or verify pscale auth from an agent.