convex-performance-audit

Diagnose Convex performance bottlenecks from deployment insights, code audits, and runtime metrics.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/RestartDK/project-europe --skill convex-performance-audit-restartdk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/RestartDK/project-europe/tree/main/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/RestartDK/project-europe --skill convex-performance-audit-restartdk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnose and fix Convex performance problems across hot-path reads, write contention, subscription cost, and function budgets, helping teams ship faster with reliable latency.

Core Features & Use Cases

  • Gather signals from deployment insights, code audits, and runtime metrics to identify the relevant performance problem class.
  • Map symptoms to the most relevant reference file (hot-path-rules.md, occ-conflicts.md, subscription-cost.md, function-budget.md) and apply the recommended fix order.
  • Provide guidance for end-to-end improvements, from quick wins to migration-safe backfills, so teams can scale performance fixes safely.

Quick Start

Run a Convex performance audit by gathering signals, identifying the problem class, consulting the corresponding reference, and applying the recommended fixes.

Frequently Asked Questions about convex-performance-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose slow Convex pages and high bytes read?▼

To diagnose slow Convex pages, gather signals from deployment insights, code audits, and runtime metrics to identify the problem class, then map symptoms to hot-path rules for targeted read optimization and staged fixes.

What causes OCC conflicts in Convex and how do I fix write contention?▼

OCC conflicts in Convex stem from write contention. Analyze runtime metrics to identify conflicting writes, then consult occ-conflicts guidance to apply a safe, staged fix order that reduces contention.

How do I reduce excessive Convex subscription costs?▼

Reduce excessive Convex subscription costs by auditing code and runtime metrics to identify the problem class, then applying the recommended fix order from subscription-cost references to optimize data fetching.

What's the best way to handle near-limit Convex function budgets?▼

Handle near-limit Convex function budgets by collecting runtime metrics to confirm the bottleneck, consulting function-budget references, and applying a migration-safe staged fix order to optimize resource usage.

Can I scale Convex performance fixes safely without breaking production?▼

You can scale Convex performance fixes safely by following a structured workflow that prescribes a staged fix order, progressing from quick wins to migration-safe backfills across all identified performance bottlenecks.