Menu
Git conventions for this project. Use when: creating branches, writing commit messages, opening PRs, or running the pre-push checklist.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task.
Understand and customize authentication in this project. Use when: adding auth to routes, swapping auth providers (Clerk, Auth0, custom SSO), debugging auth issues, or understanding the UserInfo contract and get_current_user dependency.
Manage database schema changes with Alembic. Use when: creating migrations, adding tables or columns, checking migration status, rolling back, or seeding the database.
Build, push, and deploy to AWS using Docker, ECR, and Terraform. Use when: deploying to dev/staging/prod, checking deploy status, rolling back, or running the deploy checklist.
Monitor and auto-fix the development environment. Use when: debugging backend/frontend errors, watching log streams, diagnosing startup failures, or running make dev.
Discover, evaluate, and create project-specific skills. Use when: the user needs a capability not covered by built-in skills, wants to find patterns for a specific tool or service, or asks about extending the skills directory. Also use when asking 'how do I add a new skill.'
| name | git-workflow |
| description | Git conventions for this project. Use when: creating branches, writing commit messages, opening PRs, or running the pre-push checklist. |
Use prefixed branch names:
feature/short-description — new functionalityfix/short-description — bug fixeschore/short-description — tooling, dependencies, configrefactor/short-description — code restructuringLowercase, hyphens, under 50 characters.
Follow Conventional Commits:
<type>: <short summary under 72 chars>
Types: feat, fix, chore, docs, test, refactor, style
gh pr create \
--title "feat: add projects endpoint" \
--body "## Summary
- What changed and why (1-3 bullets)
## Test plan
- How the changes were verified"
Before pushing, run the full verification suite:
make verify # lint + typecheck + test for both backend and frontend
This runs the same checks as CI, so if it passes locally, CI will pass too.