convex

Apply Convex backend patterns for queries, mutations, actions, schemas, and HTTP endpoints.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/cfardev/kanban-hub --skill convex-cfardev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convex
Source: https://github.com/cfardev/kanban-hub/tree/main/.agents/skills/convex
Command: npx skills add https://github.com/cfardev/kanban-hub --skill convex-cfardev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps teams apply consistent Convex backend patterns for queries, mutations, actions, schemas, and HTTP endpoints, enabling robust, scalable development.

Core Features & Use Cases

  • Standardized patterns for public and internal Convex functions (queries, mutations, actions) and their validations
  • Clear guidance on schema design, indexes, and HTTP routes to build secure APIs
  • Real-world scenarios covering access control, data integrity, and maintainability of Convex-backed apps

Quick Start

Use this guide to begin aligning your Convex backend with established patterns and conventions.

Frequently Asked Questions about convex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure queries and mutations in a Convex backend?

Design Convex schemas and indexes by following established conventions for data integrity, utilizing clear guidance on schema structure and HTTP routes to build secure, maintainable APIs.

What is the best way to handle validation for Convex actions and HTTP endpoints?

Handle validation for Convex actions and HTTP endpoints by enforcing consistent validators across public and internal functions, ensuring robust data integrity and secure API access control.

Can I use Convex backend patterns for real-world projects requiring access control?

Yes, you can apply Convex backend patterns to real-world projects to manage access control, secure data integrity, and maintain scalable architecture across queries, mutations, actions, and HTTP endpoints.

When should I separate public and internal functions in a Convex backend?

Separate public and internal Convex functions when you need to enforce strict code structure, secure API boundaries, and apply consistent validation across different real-world scenarios and HTTP routes.