// Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope.
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.
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.
Set up Convex authentication with proper user management, identity mapping, and access control patterns. Use when implementing auth flows, setting up OAuth providers, or adding role-based access control.
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.
Create Convex queries, mutations, and actions with proper validation, authentication, and error handling. Use when implementing new API endpoints.
Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.
| name | help |
| description | Reflection-first problem solving methodology for Convex development. Use before implementing any solution to ensure proper root cause analysis, 98% code confidence, and minimal change scope. |
Deep reflection and problem-solving methodology for full-stack Convex development.
Before implementing any solution, follow this process:
Never assume. If anything is unclear, ask questions and clarify.
Direct mutation pattern:
Best practices:
ctx.db.get())Promise.all() for parallel independent operations to avoid write conflictsFunctions:
Core concepts:
Authentication:
git log --date=short to check commit historyFor pop-ups, alerts, modals, warnings, notifications, and confirmations:
https://raw.githubusercontent.com/vercel-labs/web-interface-guidelines/refs/heads/main/AGENTS.md
IMPORTANT: Do NOT create documentation files unless explicitly instructed.
Banned unless requested:
You may include a brief summary in responses, but don't create separate documentation files.
Formatting rules:
98% confidence rule:
Don't write any code until you're very confident (98% or more) in what needs to be done.
If unclear, ask for more information.
Before writing code:
When uncertain: