agentsclimarketplace

Convex backend

Skill CloudAI-X/claude-workflow-v2/skills/convex-backend

Convex backend development guidelines. Use when writing Convex functions, schemas, queries, mutations, actions, or any backend code in a Convex project. Triggers on tasks involving Convex database operations, real-time subscriptions, file storage, or serverless functions.From its SKILL.md

Install
npx -y skills add CloudAI-X/claude-workflow-v2 --skill convex-backend

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

4.2 KB, 897 tokens by cl100k_base, as published. Nobody here has run it

Convex Backend Guidelines

When to Load

  • Trigger: Convex-specific development, writing Convex functions, schemas, queries, mutations, actions, or real-time subscriptions
  • Skip: Project does not use Convex as its backend

Comprehensive guide for building Convex backends with TypeScript. Covers function syntax, validators, schemas, queries, mutations, actions, scheduling, and file storage.

When to Apply

Reference these guidelines when:

  • Writing new Convex functions (queries, mutations, actions)
  • Defining database schemas and validators
  • Implementing real-time data fetching
  • Setting up cron jobs or scheduled functions
  • Working with file storage
  • Designing API structure

Rule Categories

CategoryImpactDescription
Function SyntaxCRITICALNew function syntax with args/returns/handler
ValidatorsCRITICALType-safe argument and return validation
Schema DesignHIGHTable definitions, indexes, system fields
Query PatternsHIGHEfficient data fetching with indexes
Mutation PatternsMEDIUMDatabase writes, patch vs replace
Action PatternsMEDIUMExternal API calls, Node.js runtime
SchedulingMEDIUMCrons and delayed function execution
File StorageLOWBlob storage and metadata

Quick Reference

Function Registration

// Public functions (exposed to clients)
import { query, mutation, action } from "./_generated/server";

// Internal functions (only callable from other Convex functions)
import {
  internalQuery,
  internalMutation,
  internalAction,
} from "./_generated/server";

Function Syntax (Always Use This)

export const myFunction = query({
  args: { name: v.string() },
  returns: v.string(),
  handler: async (ctx, args) => {
    return "Hello " + args.name;
  },
});

Common Validators

TypeValidatorExample
Stringv.string()"hello"
Numberv.number()3.14
Booleanv.boolean()true
IDv.id("tableName")doc._id
Arrayv.array(v.string())["a", "b"]
Objectv.object({...}){name: "x"}
Optionalv.optional(v.string())undefined
Unionv.union(v.string(), v.number())"x" or 1
Literalv.literal("status")"status"
Nullv.null()null

Function References

// Public functions
import { api } from "./_generated/api";
api.example.myQuery; // convex/example.ts → myQuery

// Internal functions
import { internal } from "./_generated/api";
internal.example.myInternalMutation;

Query with Index

// Schema
messages: defineTable({...}).index("by_channel", ["channelId"])

// Query
await ctx.db
  .query("messages")
  .withIndex("by_channel", (q) => q.eq("channelId", channelId))
  .order("desc")
  .take(10);

Key Rules

  1. Always include args and returns validators on all functions
  2. Use v.null() for void returns - never omit return validator
  3. Use withIndex() not filter() - define indexes in schema
  4. Use internalQuery/Mutation/Action for private functions
  5. Actions cannot access ctx.db - use runQuery/runMutation instead
  6. Include type annotations when calling functions in same file

Full Compiled Document

For the complete guide with all rules and detailed code examples, see AGENTS.md.

What ships with it: 1 file

20.7 KB alongside SKILL.md

Gives 0 of the 12 instructions most data backend skills give in 897 tokens

Counted across 258 of the 277 authors here whose files we hold, read 2026-09-06

  • Centralize error handling in one handlerin 38 of 258, across 20 files
  • Select only needed columns in queriesin 36 of 258, across 18 files
  • Check cache before querying the databasein 36 of 258, across 19 files
  • Wrap multi-step writes in transactionsin 36 of 258, across 18 files
  • Retry failed requests with exponential backoffin 36 of 258, across 18 files
  • Batch fetch related records to avoid N+1 queriesin 34 of 258, across 16 files
  • Use resource-based URLs for REST endpointsin 31 of 258, across 13 files
  • Separate business logic into a service layerin 29 of 258, across 17 files
  • Queue background jobs instead of blocking requestsin 29 of 258, across 14 files
  • Abstract data access behind repository interfacesin 25 of 258, across 13 files
  • Log structured JSON with request contextin 15 of 258, across 7 files
  • Use a shared store for rate limitingin 14 of 258, across 6 files

Said here and by no other author read

  • Write functions with args, returns, and handler
  • Include args and returns validators on all functions
  • Use v.null() for void return validators
  • Use withIndex() instead of filter() for queries
  • Define indexes in the schema
  • Use internalQuery, internalMutation, internalAction for private functions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.