Initializes a new Convex project from scratch or adds Convex to an existing app. Use this skill when starting a new project with Convex, scaffolding with npm create convex@latest, adding Convex to an existing React, Next.js, Vue, Svelte, or other frontend, wiring up ConvexProvider, configuring environment variables for the deployment URL, or running npx convex dev for the first time, even if the user just says "set up Convex" or "add a backend."
npx skills add https://github.com/get-convex/convex-backend --skill convex-quickstart
Set up a working Convex project as fast as possible.
convex/ exists - just startbuilding
convex-setup-auth skill
npm create convex@latestconvex and wire up the providernpx convex dev to connect a deployment and start the dev loopUse the official scaffolding tool. It creates a complete project with the
frontend framework, Convex backend, and all config wired together.
| Template | Stack |
| -------------------------- | ----------------------------------------- |
| react-vite-shadcn | React + Vite + Tailwind + shadcn/ui |
| nextjs-shadcn | Next.js App Router + Tailwind + shadcn/ui |
| react-vite-clerk-shadcn | React + Vite + Clerk auth + shadcn/ui |
| nextjs-clerk | Next.js + Clerk auth |
| nextjs-convexauth-shadcn | Next.js + Convex Auth + shadcn/ui |
| nextjs-lucia-shadcn | Next.js + Lucia auth + shadcn/ui |
| bare | Convex backend only, no frontend |
If the user has not specified a preference, default to react-vite-shadcn for
simple apps or nextjs-shadcn for apps that need SSR or API routes.
You can also use any GitHub repo as a template:
npm create convex@latest my-app -- -t owner/repo
npm create convex@latest my-app -- -t owner/repo#branch
Always pass the project name and template flag to avoid interactive prompts:
npm create convex@latest my-app -- -t react-vite-shadcn
cd my-app
npm install
The scaffolding tool creates files but does not run npm install, so you must
run it yourself.
To scaffold in the current directory (if it is empty):
npm create convex@latest . -- -t react-vite-shadcn
npm install
npx convex dev is a long-running watcher process that syncs backend code to a
Convex deployment on every save. It also requires authentication on first run
(browser-based OAuth). Both of these make it unsuitable for an agent to run
directly.
Ask the user to run this themselves:
Tell the user to run npx convex dev in their terminal. On first run it will
prompt them to log in or develop anonymously. Once running, it will:
.env.localconvex/ directory with generated typesThe user should keep npx convex dev running in the background while you work
on code. The watcher will automatically pick up any files you create or edit in
convex/.
Exception - cloud or headless agents: Environments that cannot open a
browser for interactive login should use Agent Mode (see below) to run
anonymously without user interaction.
The user should also run the frontend dev server in a separate terminal:
npm run dev
Vite apps serve on http://localhost:5173, Next.js on http://localhost:3000.
After scaffolding, the project structure looks like:
my-app/
convex/ # Backend functions and schema
_generated/ # Auto-generated types (check this into git)
schema.ts # Database schema (if template includes one)
src/ # Frontend code (or app/ for Next.js)
package.json
.env.local # CONVEX_URL / VITE_CONVEX_URL / NEXT_PUBLIC_CONVEX_URL
The template already has:
ConvexProvider wired into the app rootProceed to adding schema, functions, and UI.
Use this when the user already has a frontend project and wants to add Convex as
the backend.
npm install convex
Ask the user to run npx convex dev in their terminal. This handles login,
creates the convex/ directory, writes the deployment URL to .env.local, and
starts the file watcher. See the notes in Path 1 about why the agent should not
run this directly.
The Convex client must wrap the app at the root. The setup varies by framework.
Create the ConvexReactClient at module scope, not inside a component:
// Bad: re-creates the client on every render
function App() {
const convex = new ConvexReactClient(
import.meta.env.VITE_CONVEX_URL as string,
);
return <ConvexProvider client={convex}>...</ConvexProvider>;
}
// Good: created once at module scope
const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string);
function App() {
return <ConvexProvider client={convex}>...</ConvexProvider>;
}
// src/main.tsx
import { StrictMode } from "react";
import { createRoot } from "react-dom/client";
import { ConvexProvider, ConvexReactClient } from "convex/react";
import App from "./App";
const convex = new ConvexReactClient(import.meta.env.VITE_CONVEX_URL as string);
createRoot(document.getElementById("root")!).render(
<StrictMode>
<ConvexProvider client={convex}>
<App />
</ConvexProvider>
</StrictMode>,
);
// app/ConvexClientProvider.tsx
"use client";
import { ConvexProvider, ConvexReactClient } from "convex/react";
import { ReactNode } from "react";
const convex = new ConvexReactClient(process.env.NEXT_PUBLIC_CONVEX_URL!);
export function ConvexClientProvider({ children }: { children: ReactNode }) {
return <ConvexProvider client={convex}>{children}</ConvexProvider>;
}
// app/layout.tsx
import { ConvexClientProvider } from "./ConvexClientProvider";
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html lang="en">
<body>
<ConvexClientProvider>{children}</ConvexClientProvider>
</body>
</html>
);
}
For Vue, Svelte, React Native, TanStack Start, Remix, and others, follow the
matching quickstart guide:
The env var name depends on the framework:
| Framework | Variable |
| ------------ | ------------------------ |
| Vite | VITE_CONVEX_URL |
| Next.js | NEXT_PUBLIC_CONVEX_URL |
| Remix | CONVEX_URL |
| React Native | EXPO_PUBLIC_CONVEX_URL |
npx convex dev writes the correct variable to .env.local automatically.
When running in a cloud or headless agent environment where interactive browser
login is not possible, set CONVEX_AGENT_MODE=anonymous to use a local
anonymous deployment.
Add CONVEX_AGENT_MODE=anonymous to .env.local, or set it inline:
CONVEX_AGENT_MODE=anonymous npx convex dev
This runs a local Convex backend on the VM without requiring authentication, and
avoids conflicting with the user's personal dev deployment.
After setup, confirm everything is working:
npx convex dev is running without errorsconvex/_generated/ directory exists and has api.ts and server.ts.env.local contains the deployment URLOnce the project is set up, create a schema and a query to verify the full loop
works.
convex/schema.ts:
import { defineSchema, defineTable } from "convex/server";
import { v } from "convex/values";
export default defineSchema({
tasks: defineTable({
text: v.string(),
completed: v.boolean(),
}),
});
convex/tasks.ts:
import { query, mutation } from "./_generated/server";
import { v } from "convex/values";
export const list = query({
args: {},
handler: async (ctx) => {
return await ctx.db.query("tasks").collect();
},
});
export const create = mutation({
args: { text: v.string() },
handler: async (ctx, args) => {
await ctx.db.insert("tasks", { text: args.text, completed: false });
},
});
Use in a React component (adjust the import path based on your file location
relative to convex/):
import { useQuery, useMutation } from "convex/react";
import { api } from "../convex/_generated/api";
function Tasks() {
const tasks = useQuery(api.tasks.list);
const create = useMutation(api.tasks.create);
return (
<div>
<button onClick={() => create({ text: "New task" })}>Add</button>
{tasks?.map((t) => (
<div key={t._id}>{t.text}</div>
))}
</div>
);
}
Always use npx convex dev during development. It runs against your personal
dev deployment and syncs code on save.
When ready to ship, deploy to production:
npx convex deploy
This pushes to the production deployment, which is separate from dev. Do not use
deploy during development.
convex-setup-auth skillconvex-create-component skillconvex-migration-helper skillnpm create convex@latest usingappropriate template
convex and wired up the providernpx convex dev running and connected to a deploymentconvex/_generated/ directory exists with types.env.local has the deployment URLGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take get-convex/convex-backend-.agents-convex-quickstart from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm, npx.
Without those the skill loads but fails at the first command.