convex-performance-audit

Diagnose Convex performance bottlenecks in hot-path reads, write contention, and subscription costs.

Updated Apr 3, 2026

Search Tags:#performance #audit #convex #refactor-guidance #hot-path #occ-conflicts #subscription-cost

Ready to run

npx skills add https://github.com/ScriptKitKat/TamaGoosie --skill convex-performance-audit-scriptkitkat

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convex-performance-audit
Source: https://github.com/ScriptKitKat/TamaGoosie/tree/main/.agents/skills/convex-performance-audit
Command: npx skills add https://github.com/ScriptKitKat/TamaGoosie --skill convex-performance-audit-scriptkitkat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Diagnoses Convex performance bottlenecks in hot-path reads, write contention, and subscription-related costs.

Core Features & Use Cases

Guided signals-driven auditing: gather health signals from insights, dashboards, or code audits and map them to the most impactful problem class.
Reference-guided fixes: apply targeted optimizations using the references for hot-path rules, OCC conflicts, subscription costs, and function budgets.
End-to-end validation workflow: audit one concrete user flow, inspect sibling functions, implement fixes, and verify no regressions.

Quick Start

Start by triggering the audit from the strongest signal and follow the guided steps to surface a concrete, high-impact optimization.

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 reads and high mutation retries in my Convex app?▼

To diagnose slow reads and high mutation retries in Convex, gather health signals from insights or dashboards and map them to problem classes like hot-path reads or write contention. This guides targeted fixes for your specific bottlenecks.

What causes excessive reactive updates and subscription costs in Convex?▼

Excessive reactive updates and subscription costs in Convex are caused by inefficient query designs that trigger unnecessary reactivity. Auditing subscription-related costs maps these signals to targeted optimizations using function budgets and subscription cost references.

How do I fix write contention and OCC conflicts in Convex?▼

Fix write contention and OCC conflicts in Convex by applying targeted optimizations from OCC conflict references. The audit maps contention signals to problem classes and guides you through implementing fixes while inspecting sibling functions for safety.

What is the best way to audit a Convex app for performance bottlenecks?▼

The best way to audit Convex performance bottlenecks is a signals-driven approach: trigger the audit from the strongest signal, map it to a problem class, implement fixes using reference guides, and validate one concrete user flow for regressions.

Can I use this audit approach for a Convex app with hot-path read issues?▼

Yes, you can use this audit approach for Convex apps with hot-path read issues. The audit specifically diagnoses hot-path reads using reference-guided fixes and validates changes by inspecting sibling functions to ensure no regressions occur.

Why does my Convex app have high mutation retries and how do I resolve them?▼

High mutation retries in Convex indicate write contention or OCC conflicts. Resolve them by mapping these signals to problem classes during an audit and applying targeted fixes from the OCC conflict references to reduce contention.