convex-quickstart
Skill628 starsChanged 7 months agoMITView on GitHub
Initialize a new Convex project from scratch or add Convex to an existing app. Use when starting a new project with Convex, scaffolding a Convex app, or integrating Convex into an existing frontend.
- Reads credentials
- Installs packages
20 other projects use a version of this, 13 of them edited.
Adopted by
Most recently taken up by
- get-convex/agent-skillstheir own version, first seen Oct 29, 2026
- convex/agent-skillstheir own version, first seen Oct 17, 2026
- get-convex/workflowedited, first seen Oct 9, 2026
- moltbot/molthubtheir own version, first seen Oct 8, 2026
- get-convex/convex-helpersedited, first seen Oct 8, 2026
- clawdbot/clawdhubtheir own version, first seen Oct 8, 2026
Used with
Projects with it also use convex-acquire-domain, convex-check-updates and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
FabienGreardSkillconvex-acquire-domain
Find and buy a domain for the current Convex app through Convex, then bind it (labs; spend action).
Also in 4 projects that use this
FabienGreardSkillconvex-check-updates
Check the current app's pinned Convex components against recommended versions and upgrade them behind a build gate.
Also in 4 projects that use this
openclawSkillclawhub-ban-appeals
Review ClawHub account-ban appeals, distinguish bans from moderation holds or blocked releases, and prepare an evidence-backed moderation decision. Route validated scanner inaccuracies to clawhub-clawscan.
Also in 3 projects that use this
openclawSkillclawhub-clawscan
Investigate ClawScan health alerts, diagnose scanner or ClawHub integration failures, prepare operational repairs, and route validated verdict inaccuracies upstream. Account ban appeals use clawhub-ban-appeals.
Also in 3 projects that use this
- +5 more from openclaw
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 13
- raroque/boop-agent★ 1.3k39% same
- pingdotgg/lawn★ 69024% same
- get-convex/convex-helpers★ 49638% same
- get-convex/workflow★ 8638% same
- sholajegede/mastra-vs-langchain★ 1724% same
- vantageos-agency/vantage-peers★ 438% same
- Decentralized-Rights-Protocol/Dr-Blockchain★ 238% same
- fiinytid/nexusai.gg★ 224% same
- ReScienceLab/TrySkills★ 238% same
- sprioleau/flock★ 124% same
3 more not listed
Wrote their own version · 7
- openclaw/clawhub★ 9.6ksame name
- clawdbot/clawdhub★ 9.5ksame name
- moltbot/molthub★ 9.5ksame name
- convex/agent-skills★ 68same name
- get-convex/agent-skills★ 68same name
- FabienGreard/TouchGrassBar★ 5same name
- getsentry/friday★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- public/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/convex2.mdcCursor rule
- .cursor/rules/convex-doctor.mdcCursor rule
- .cursor/rules/convex-write-conflicts.mdcCursor rule
- .cursor/rules/dev2.mdcCursor rule
- .cursor/rules/gitruels.mdcCursor rule
- .cursor/rules/help.mdcCursor rule
- .cursor/rules/rulesforconvex.mdcCursor rule
- .cursor/rules/sec-check.mdcCursor rule
- .cursor/rules/task.mdcCursor rule
- .cursor/rules/workflow.mdcCursor rule
- .cursor/rules/write.mdcCursor rule
- public/llms.txtllms.txt
- convex-create-componentSkill
- convex-migration-helperSkill
- convex-performance-auditSkill
- convex-quickstartSkill
- convex-setup-authSkill
- convexSkill
- impeccableSkill
- convex-setup-authSkill
- devSkill
- function-creatorSkill
- gitrulesSkill
- helpSkill
- migration-helperSkill
- react-effect-decisionSkill
- real-time-backendSkill
- schema-builderSkill
- sec-checkSkill
- workflowSkill
- writeSkill
- convex-doctorSkill
- convex-return-validatorsSkill
- convex-self-hostingSkill
- create-prdSkill
- robel-authSkill
- update-project-docsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 2 are common, 2 are distinctive, and 7 are very specific to this project.
2
Common
Most of the 20 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
If new project, pick a template and scaffold with npm create convex@latest
- Very specific: line 25
If existing app, install convex and wire up the provider
- Very specific: line 26
Run npx convex dev to connect a deployment and start the dev loop
- Common: line 27
Verify the setup works
- Very specific: line 42
Default to react-vite-shadcn for simple apps or nextjs-shadcn for apps that need SSR or API routes.
- Common: line 46
Always pass the project name and template flag to avoid interactive prompts:
- Very specific: line 56
Ask the user to run npx convex dev in their terminal.
- Distinctive: line 57
Create a Convex project and dev deployment
- Very specific: line 58
Write the deployment URL to .env.local
- Very specific: line 59
Create the convex/ directory with generated types
- Distinctive: line 154
Use in a React component:
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Convex Quickstart
Set up a working Convex project as fast as possible.
When to Use
- Starting a brand new project with Convex
- Adding Convex to an existing React, Next.js, Vue, Svelte, or other app
- Scaffolding a Convex app for prototyping
When Not to Use
- The project already has Convex installed and
convex/exists: just start building - You only need to add auth to an existing Convex app: use the
convex-setup-authskill
Workflow
- Determine the starting point: new project or existing app
- If new project, pick a template and scaffold with
npm create convex@latest - If existing app, install
convexand wire up the provider - Run
npx convex devto connect a deployment and start the dev loop - Verify the setup works
Path 1: New Project (Recommended)
Pick a template
| 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 |
bare | Convex backend only, no frontend |
Default to react-vite-shadcn for simple apps or nextjs-shadcn for apps that need SSR or API routes.
Scaffold the project
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 installStart the dev loop
Ask 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:
- Create a Convex project and dev deployment
- Write the deployment URL to
.env.local - Create the
convex/directory with generated types - Watch for changes and sync continuously
Path 2: Add Convex to an Existing App
Install
npm install convexWire up the provider
React (Vite)
// 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>,
);Next.js (App Router)
// 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>;
}Environment variables
| Framework | Variable |
| Vite | VITE_CONVEX_URL |
| Next.js | NEXT_PUBLIC_CONVEX_URL |
| Remix | CONVEX_URL |
| React Native | EXPO_PUBLIC_CONVEX_URL |
Writing Your First Function
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:
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>
);
}Checklist
- Determined starting point: new project or existing app
- If new project: scaffolded with
npm create convex@latestusing appropriate template - If existing app: installed
convexand wired up the provider - User has
npx convex devrunning and connected to a deployment convex/_generated/directory exists with types.env.localhas the deployment URL- Verified a basic query/mutation round-trip works
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

