convex

Deploy Convex backends in sync with Vite-based frontends.

2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/marcojsmith/AgriBid --skill convex-marcojsmith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex
Source: https://github.com/marcojsmith/AgriBid/tree/main/.agent/skills/convex
Command: npx skills add https://github.com/marcojsmith/AgriBid --skill convex-marcojsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers to build and deploy Convex backends in sync with a Vite-based frontend, ensuring consistent environments and smoother CI/CD.

Core Features & Use Cases

  • End-to-end Convex development: guidance on backend design, functions, and integration with Vercel.
  • Deployment best practices: codegen, TypeScript path aliases, and environment variable management for production-ready builds.
  • Use Case: Aligns a Convex API with a Vercel deployment to avoid drift between backend and frontend during updates.

Quick Start

Set up your Convex project with a synced backend/frontend deployment pipeline and run the codegen step before deploying.

Frequently Asked Questions about convex

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

FAQPage Schema
How do I deploy a Convex backend in sync with a Vercel frontend?

Deploying a Convex backend with Vercel requires coordinating CI pipelines, environment variables, and codegen workflows to prevent drift between frontend and backend updates.

What is the best way to run Convex codegen before a Vite deployment?

Running Convex codegen before deployment generates typed API references, ensuring your Vite frontend stays synchronized with backend schema changes during CI/CD.

How do I configure TypeScript path aliases for a Convex and Vercel project?

Configuring TypeScript path aliases aligns module resolution between your Vite frontend and Convex backend, ensuring consistent imports across local development and Vercel deployments.

Can I manage Convex environment variables consistently across Vercel CI/CD stages?

Yes, managing Convex environment variables consistently across Vercel CI/CD stages prevents configuration drift and ensures backend functions execute with correct credentials.

Why does my Convex API drift from my Vite frontend during updates?

Convex API drift occurs when frontend and backend deployments are not aligned, which is resolved by syncing codegen steps and environment configurations within your Vercel pipeline.