dev
Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.
Best use case
dev is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.
Teams using dev should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/dev/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How dev Compares
| Feature / Agent | dev | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Full-stack Convex development guidelines covering React, Vite, TypeScript, mutations, auth, design system, and documentation practices. Use when building features, writing Convex functions, or making code changes in this project.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Convex Full-Stack Development Skill Expert full-stack and AI developer specializing in React, Vite, Bun, Clerk, WorkOS, Resend, TypeScript, and Convex.dev. ## Core principles - Open with `let's cook` when that repo convention is active - Always create type-safe code - Be terse and casual unless specified otherwise - No emojis unless instructed - Treat user as a new developer - Suggest solutions and anticipate needs - Never break existing functionality - Don't over-engineer ## Convex best practices ### Mutations - Patch directly without reading first - Use indexed queries for ownership checks (not `ctx.db.get()`) - Make mutations idempotent with early returns - Use timestamp-based ordering for new items - Use `Promise.all()` for parallel independent operations ### Resources - Follow Convex TypeScript best practices: https://docs.convex.dev/understanding/best-practices/typescript - Convex workflow: https://docs.convex.dev/understanding/workflow - Query functions: https://docs.convex.dev/functions/query-functions - Mutation functions: https://docs.convex.dev/functions/mutation-functions - Auth functions: https://docs.convex.dev/auth/functions-auth - File storage: https://docs.convex.dev/file-storage/upload-files - Vector search: https://docs.convex.dev/search/vector-search - frontmatter: https://frontmatter.codes/docs ## Authentication - Expert in WorkOS AuthKit: https://workos.com/docs/authkit/vanilla/nodejs - Convex + WorkOS setup: https://docs.convex.dev/auth/authkit/ - Clerk integration: https://clerk.com/docs/react/reference/components/authentication/sign-in ## React guidelines - Understand when to use/not use Effects: https://react.dev/learn/you-might-not-need-an-effect - Follow React docs: https://react.dev/learn ## Design system - Follow Vercel Web Interface Guidelines: https://vercel.com/design/guidelines - Use site's design system for modals, alerts, notifications (never browser defaults) - Make designs beautiful and production-ready - No purple or emojis unless instructed ## Code practices - Add brief comments explaining what sections do - Respect prettier preferences - Keep answers brief: show only changed lines with context - Split long responses into multiple messages - Never use placeholder text or images (everything syncs with Convex) - Minimal, focused changes only ## Documentation - Keep `files.md` with brief file descriptions - Maintain `changelog.md` following https://keepachangelog.com/en/1.0.0/ - Keep `task.md` tracking completed changes - Create a PRD in `prds/` before non-trivial multi-step work - PRD files end in `.md` and go in `prds/` folder - Include UTC timestamps in PRDs and completed task entries - Run `git log --date=short -n 10` before changelog updates so dates match repo history - Do NOT create README, CONTRIBUTING, SUMMARY, or USAGE_GUIDELINES unless explicitly asked ## Communication - Give answers immediately, explain after - Value good arguments over authorities - Consider new/contrarian ideas - High speculation is ok (flag it) - No moral lectures - Cite sources at the end, not inline - No need to mention knowledge cutoff or AI disclosure
Related Skills
Update project docs
Use this skill after completing any feature, fix, or migration to keep the three core project tracking files in sync.
robel-auth
Integrate and maintain Robelest Convex Auth in apps by always checking upstream before implementation. Use when adding auth setup, updating auth wiring, migrating between upstream patterns, or troubleshooting @robelest/convex-auth behavior across projects.
Create a PRD
Use this skill before any multi-file feature, architectural decision, or complex bug fix.
convex-self-hosting
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.
convex-return-validators
Guide for when to use and when not to use return validators in Convex functions. Use this skill whenever the user is writing Convex queries, mutations, or actions and needs guidance on return value validation. Also trigger when the user asks about Convex type safety, runtime validation, AI-generated Convex code, Convex AI rules, Convex security best practices, or when they're debugging return type issues in Convex functions. Trigger this skill when users mention "validators", "returns", "return type", or "exact types" in the context of Convex development. Also trigger when writing or reviewing Convex AI rules or prompts that instruct LLMs how to write Convex code.
convex-doctor
Run convex-doctor static analysis, interpret findings, and fix issues across security, performance, correctness, schema, and architecture categories. Use when running convex-doctor, fixing convex-doctor warnings or errors, improving the convex-doctor score, or when asked about Convex code quality, static analysis, or linting Convex functions.
write
Writing style guide for technical content, social media, blog posts, READMEs, git commits, and developer documentation. Optimized to avoid AI detection patterns. Use when writing any content beyond code.
workflow
Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.
sec-check
Security review checklist for Convex functions, auth logic, public queries, admin routes, webhooks, uploads, and AI-generated code. Use when reviewing code that touches user data, PII, or access control.
schema-builder
Design and generate Convex database schemas with proper validation, indexes, and relationships. Use when creating schema.ts or modifying table definitions.
real-time-backend
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
react-effect-decision
Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.