project-starter

Add tests for recently changed files or specified code

System design and architecture planning mode. Focuses on high-level design, trade-offs, and technical decisions before implementation.

Simplifies code after implementation. Reviews recent changes and suggests/applies simplifications while preserving behavior.

Commit staged changes, push to remote, and create a pull request

Create a conventional commit with auto-generated message

Runs linting and code quality checks. Catches style issues, potential bugs, and enforces project standards.

Auto-fix all linting and formatting issues

Educational mode that explains concepts, teaches patterns, and guides learning. Ideal when learning a new codebase, technology, or programming concept.

Multi-perspective analysis using parallel subagents. Analyzes code from architecture, security, performance, and testing viewpoints simultaneously.

Run parallel code review across multiple directories or files. Uses N subagents simultaneously for faster analysis.

Quickly fix lint errors, type errors, or simple bugs

Fast-paced development mode for quick iterations. Minimal ceremony, maximum speed. Best for prototypes, MVPs, and time-sensitive tasks.

Strict code review mode with high standards. Thoroughly examines code for bugs, security issues, performance problems, and best practice violations.

Runs project tests intelligently. Identifies affected tests from changes and runs them first, then full suite.

Security-focused code scan. Checks for hardcoded secrets, vulnerable dependencies, and common security issues.

- Current branch: !`git branch --show-current`

- Current branch: !`git branch --show-current`

Validates project build process. Run after changes to ensure the project compiles/transpiles correctly.

Comprehensive verification after code changes. Uses Boris Cherny's multi-subagent adversarial approach.

Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, or when asked to review changes. Focuses on quality, security, performance, and maintainability.

Expert debugging specialist for errors, test failures, crashes, and unexpected behavior. Use PROACTIVELY when encountering any error, exception, or failing test. Performs systematic root cause analysis.

Technical documentation specialist. Use for creating README files, API documentation, architecture docs, inline comments, and user guides. MUST BE USED when documentation is needed or when code changes require doc updates.

Master coordinator for complex multi-step tasks. Use PROACTIVELY when a task involves 2+ modules, requires delegation to specialists, needs architectural planning, or involves GitHub PR workflows. MUST BE USED for open-ended requests like "improve", "refactor", "add feature", or when implementing features from GitHub issues.

Code refactoring specialist for improving code quality, reducing technical debt, and applying design patterns. Use when code needs restructuring, simplification, or when applying DRY/SOLID principles.

Security specialist for vulnerability detection, secure coding review, and security hardening. Use PROACTIVELY when handling authentication, authorization, user input, API keys, or sensitive data. Checks for OWASP Top 10 and common vulnerabilities.

Testing strategy specialist for designing test suites, writing tests, and ensuring comprehensive coverage. Use when adding new features, fixing bugs, or improving test coverage. Creates unit, integration, and e2e tests.

Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"

Convex backend development guidelines. Use when writing Convex functions, schemas, queries, mutations, actions, or any backend code in a Convex project. Triggers on tasks involving Convex database operations, real-time subscriptions, file storage, or serverless functions.

Designs REST and GraphQL APIs including endpoints, error handling, versioning, and documentation. Use when creating new APIs, designing endpoints, reviewing API contracts, or when asked about REST, GraphQL, or API patterns.

Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.

Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.

Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.

Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.

Patterns for parallel subagent execution using Task tool with run_in_background. Use when coordinating multiple independent tasks, spawning dynamic subagents, or implementing features that can be parallelized.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

9 hooks across 6 events