ClaudeSuperPower
SubmitLog in

quickstart

Skill

Scaffold a brand-new Convex app from a one-sentence idea and build it live in front of the user — a running Next.js + shadcn app backed by `convex dev` + `next dev` with error watchers already armed. Use this to go from idea → running app in under a minute (it runs locally), then iterate, narrating

0Frontend

Install

git clone https://github.com/get-convex/convex-backend-skill.git ~/.claude/skills/quickstart

What is quickstart?

Scaffold a brand-new Convex app from a one-sentence idea and build it live in front of the user — a running Next.js + shadcn app backed by `convex dev` + `next dev` with error watchers already armed. Use this to go from idea → running app in under a minute (it runs locally), then iterate, narrating each step in chat.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~80 tokens of context used while enabled, before you invoke anything

Documentation

README · ~8 min read

Convex Quickstart — scaffold and build live

This skill takes a one-sentence app idea and stands up a running Convex app the user can watch build in real time. The scaffold is a Next.js + shadcn app with convex dev + next dev started and error watchers armed. The app runs locally at the URL the bootstrap prints.

Your job: scaffold it, open the browser, then build the user's idea live, narrating every step in chat.

Scope for this release. The scaffold ships with no login (no auth/passkeys), no in-app panel, and no publishing — the app runs locally at the printed URL. Only add auth if the user explicitly asks for it. Don't deploy, publish to a public URL, or wire a custom domain.

Degradation rule — when the scaffold can't run, write code, not ceremony

If the served scaffold/bootstrap can't run — a non-interactive/one-shot session, no network access, a sandboxed temp dir, or the user just wants code rather than a running app — don't wait on the scaffold. Write a standard Convex project directly:

  • ALL backend code goes under convex/ (schema.ts, queries, mutations, actions, http.ts, crons.ts, convex.config.ts) — NEVER at the project root. Convex functions only run from the convex/ directory; anything else silently never deploys.
  • Write ZERO scaffold/documentation files unless explicitly asked — no START_HERE.md, ARCHITECTURE.md, MANIFEST.txt, DEPLOYMENT_CHECKLIST.md, IMPLEMENTATION_SUMMARY.txt, or a wall of README files. "Build me a backend" is a request for code, not a design-doc package.

Data access + imports — read before writing any convex/*.ts

  • Never an unbounded .collect() on a table that can grow — use .withIndex(...) combined with .paginate(paginationOpts) or .take(n).

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Subagents

All subagents →

code-architect

Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences

32.8K stars

plugin-validator

Use this agent when the user asks to "validate my plugin", "check plugin structure", "verify plugin is correct", "validate plugin.json", "check plugin files", or mentions plugin validation. Also trigger proactively after user creates or modifies plugin components. Examples: <example> Context: User f

32.8K stars

scan-inventory

Restricted read-only repository cartographer dispatched by the Claude Security scan workflow to partition the tree into components and account for every top-level directory; not for direct invocation or vulnerability research.

32.8K stars