1. Software Development

Systematically traces errors backward through the call stack to identify root causes of bugs, invalid data, or incorrect behavior in software execution.

Maintains IdeaVim test suite quality by reviewing disabled tests, documenting Neovim annotations, and enhancing test readability for periodic upkeep.

Creates database migration files for Prisma, Sequelize, and other ORMs following project conventions.

Provides Python code patterns for implementing observability through logging, metrics, and tracing using OpenTelemetry and structlog.

Enables developers to explore unfamiliar codebases by answering questions about implementation locations, functionality, and component behavior.

Dispatches competing architectural and implementation reviewers to ensure thorough codebase analysis before technical decisions or code changes.

Enforces TypeScript strict mode, type safety, and best practices including strict flags and no-any rules for improved code quality in project setup and reviews.

Provides state management patterns for React applications using TanStack Query and Zustand.

Automates software release creation by analyzing changes, bumping versions, updating changelogs, and managing Git commits and tags.

Provides utilities for Angular form management, including Signal Forms (experimental) and Reactive Forms, with validation and state handling.

Provides core Angular patterns including standalone components, signals, and zoneless setup for efficient frontend development.

Guides Angular project structure, scope rules, file naming conventions, and style guides for effective frontend code organization.

Optimizes Angular app performance with NgOptimizedImage, @defer, lazy loading, and SSR techniques.

Manages Git worktrees for parallel development, handling creation, dependency setup, validation, and PR registry updates.

Delegates coding tasks to Codex CLI for prototyping, debugging, and code review with algorithm implementation support.

Creates targeted test cases to replicate and debug complex software issues through iterative problem-solving.

Enables development and debugging of frontend features for web applications, enhancing user interface and interaction logic.

Enforces a development workflow where tests are written before implementation code, ensuring tests validate behavior by requiring initial failure.

A four-phase debugging framework (root cause investigation, pattern analysis, hypothesis testing, implementation) ensuring thorough problem understanding before proposing fixes.

Creates isolated Git workspaces to develop multiple branches concurrently without switching contexts in a single repository.

Systematically traces errors backward through the call stack to identify the root cause of bugs, invalid data, or incorrect behavior in software execution.

Finalizes a feature branch with passing tests and prepares for pull request creation.

Prevents common testing anti-patterns including mocking without dependency understanding, testing mock behavior, and polluting production code with test-only methods.

Guides users through creating a new custom skill, covering requirement gathering, directory structure setup, and SKILL.md documentation.