Menu
Use this skill when creating commits, writing commit messages, preparing PRs, or when asked about git workflow. Triggers on 'commit this', 'write a commit message', 'create a PR', 'prepare for review'.
Helps the user explore a career pivot from senior technical leadership into a healthier, values-aligned future role. Use this skill when the user is brainstorming future roles, career pivots, values, passions, burnout, anxiety, identity, purpose, work-life fit, executive roles, consulting, COO, CTO, VP Engineering, Head of Engineering, AI leadership, or founder-to-corporate transitions.
Visual guide to structuring your Claude Code development environment with tmux, git worktrees, and Agent Teams. Use when setting up parallel sessions, onboarding to Claude Code workflows, or when terminal tabs are getting chaotic. Triggers on 'set up my dev environment', 'tmux workflow', 'parallel sessions', 'worktree setup', 'agent teams setup', 'too many tabs'.
Use this skill when reviewing, auditing, or improving code quality. Triggers on requests like 'review this code', 'check code quality', 'clean this up', 'audit this file', or 'make this production-ready'.
Use this skill when preparing code for review, reviewing a PR, or doing an adversarial review pass. Triggers on 'review this PR', 'prepare this for review', 'adversarial review', 'fresh eyes on this'.
Build a concrete plan to manually find and personally close the first 10 customers for a new product, feature, or pricing tier. Includes the Sean Ellis "would be devastated" test. Triggers on 'find first 10', 'first 10 customers', 'who do I sell this to first', 'sean ellis test', 'manual customer acquisition plan'.
Use this skill when building UI components, designing layouts, or making frontend styling decisions. Triggers on 'build this UI', 'style this component', 'make this look good', 'improve the design', 'create a landing page'.
| name | git-conventions |
| description | Use this skill when creating commits, writing commit messages, preparing PRs, or when asked about git workflow. Triggers on 'commit this', 'write a commit message', 'create a PR', 'prepare for review'. |
Follow these conventions for all git operations.
Use Conventional Commits:
<type>(<scope>): <short description>
[optional body]
[optional footer]
feat — new featurefix — bug fixchore — maintenance, dependencies, configdocs — documentation onlyrefactor — code change that neither fixes a bug nor adds a featuretest — adding or updating testsperf — performance improvementci — CI/CD changesFixes #123 or Relates to #456feat(auth): add OAuth2 login with Google
Adds Google OAuth2 as a login option alongside existing email/password.
Uses the existing session management system.
Fixes #89
fix(api): handle null response from payment provider
The Stripe webhook occasionally sends a null amount field for
disputed charges. This was causing an unhandled exception.
<type>/<short-description>
Examples:
feat/user-dashboardfix/login-redirect-bugchore/update-dependencies## What
[Brief description of the change]
## Why
[Context and motivation]
## How
[Implementation approach, notable decisions]
## Testing
[How to verify this works]
## Screenshots (if UI change)
For CSS, visual, or layout changes deployed to a hosted environment:
verify-deploy.sh script (if one exists) after the deployment completesmain or master.env files