// Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work.
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.
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.
| name | gitrules |
| description | Critical Git safety rules to prevent destructive operations. Use whenever performing git operations, reverting changes, or managing commits. Prevents accidental loss of work. |
NEVER USE git checkout TO REVERT CHANGES.
MANDATORY GIT SAFETY RULES:
git checkout -- <file> without first examining what you're about to destroygit diff <file> to see exactly what changes will be lostgit checkout destroys ALL changes: this can eliminate hours of valuable progressWhy this matters: Using git checkout blindly can destroy sophisticated implementations, complex prompts, provider-specific logic, and other valuable work that took significant time to develop.
NEVER run these commands without explicit user approval:
git reset --hard: Destroys uncommitted changes permanentlygit checkout -- .: Discards all working directory changesgit clean -fd: Deletes untracked files permanentlygit stash drop: Deletes stashed changesALWAYS before any git operation:
git status first to check for uncommitted changesgit stash to preserve changes if neededIf user asks to "revert" something:
This rule exists because careless git operations destroyed 2 days of work.