1. Software Development

Structured four-phase debugging methodology for identifying root causes of software issues before implementing fixes, applicable to unexpected failures and performance regressions.

Enforces test-first development using the Red-Green-Refactor cycle for new features, bug fixes, and refactoring in production code.

Enforces standardized branch naming and creation protocols to maintain code organization and team collaboration in version control systems.

Manages GitHub repositories, issues, projects, and pull requests for software development workflows.

Provides structured guidelines for the planning phase in software development, emphasizing thorough preparation before coding or implementation.

Simplifies and improves code file content through refactoring to enhance understandability, maintainability, and debuggability.

Plans and guides restructuring of code folders to enhance readability, maintainability, and debugging efficiency in software projects.

Provides structured guidelines and checklists for creating pull requests in the Luxor project, ensuring adherence to development standards.

Analyzes and provides feedback on code changes in pull requests to maintain quality and standards.

Enforces component creation rules for jp-ui, including Base UI wrapper policies, render management, and layout/spacing guidelines in Storybook.

Provides Test-Driven Development (TDD) patterns and practices for software development workflows.

Automatically selects appropriate review criteria for code files based on file type and characteristics during code review initiation.

Creates a type-safe Zustand store for BoxLog with devtools integration and state persistence.

Analyzes codebases using parallel agent mapping to visualize structure, dependencies, and relationships.

Creates unified feature modules with stores, hooks, components, and types for BoxLog frontend development.

Plans and optimizes file locations within a project's folder structure for improved organization and maintainability.

Critically evaluates code review feedback for technical accuracy and clarity before implementation, ensuring rigorous verification over passive acceptance.

Orchestrates code implementation via independent subagents with two-stage review (spec compliance and code quality) for multiple non-coupled tasks in a single session.

Requires execution and confirmation of verification commands before claiming code completion, commit, or PR creation to ensure correctness.

Systematically debugs C#/.NET applications including gRPC services, EF Core queries, and async operations.

Enforces consistent coding standards by eliminating magic numbers, promoting constant usage, and ensuring type safety across the codebase during implementation and review.

Enables efficient execution of multiple independent tasks by dispatching them to parallel agents without shared state dependencies.

Enables efficient management of multiple Git branches in separate working directories for concurrent development tasks.

Automates responding to PR review comments by fixing issues, summarizing changes, and generating responses.