What problem does it solve?
Working on the ClawHub repository's Convex backend requires knowing repository-specific rules that generic Convex guidance does not cover, such as which deployment to target, where migrations belong, and how to read and write migrated skill stat fields without breaking compatibility.
Core Features & Use Cases
- Runtime Targeting and Validation: Names the correct deployment (local, dev, prod) before running Convex commands, pushes functions before
convex run, and handles the 401 MissingAccessToken case by dropping --env-file.
- Migration Boundaries: Routes production data changes to
@convex-dev/migrations, component backfills to convex/migrations.ts, and custom repairs to convex/maintenance.ts, keeping one-off runs out of deploy workflows.
- Skill Stat Contract: Enforces dual-shape reads and writes for migrated stats (
statsDownloads, statsStars, statsInstallsCurrent, statsInstallsAllTime) via readCanonicalStat() and applySkillStatDeltas().
- Use Case: When adding a new stat field to the
skills table, follow the dual-write shape, add a cursor-based backfill, and route the production apply through the migration companion skills.
Quick Start
Ask the agent to make a Convex change in the ClawHub repository, such as updating a query or adding a migration, and it will apply the ClawHub-specific conventions automatically.
