composer-dependency-managementComposer dependency management patterns for PHP projects — version constraints, autoloading, private packages, WPackagist for WordPress, Bedrock-style WordPress, and retrofitting Composer onto legacy CI3 projects. Use when managing dependencies, configuring autoloading, or setting up Composer for Wo
database-patternsDatabase query and optimization patterns for Eloquent (Laravel/Sage), WordPress ($wpdb, WP_Query, meta queries), and CodeIgniter 3 Query Builder. Use when writing database queries, optimizing N+1 problems, creating migrations, or deciding between post meta and custom tables.
laravel-api-patternsLaravel API development patterns — API Resources, Sanctum token authentication, rate limiting, route groups, exception handling, webhook receivers, and cursor pagination. Use when building Laravel APIs.
laravel-architectureLaravel and Sage/Roots architecture decisions with tradeoffs. Use when planning a Laravel application's structure, designing Eloquent models and relationships, designing queues, jobs, events, or broadcasting, choosing a design or enterprise pattern such as repositories, CQRS, multi-tenancy, or event
laravel-patternsLaravel implementation patterns — service providers, middleware, Form Requests, API Resources, Eloquent models, jobs with retry logic, events and listeners, and action classes. Use when writing Laravel application code.
legacy-ci3-maintenanceSafe maintenance patterns for CodeIgniter 3 legacy applications — MVC conventions, avoiding regressions, incremental improvements, and security patching. Intentionally lean for codebases in maintenance mode. Use when working in CI3 code, patching CI3 security issues, or making safe changes to legacy
php-architectureFramework-agnostic PHP architecture and quality decisions. Use when setting type or static-analysis policy, choosing an architecture or design pattern for plain PHP or Symfony code, tuning PHP runtime performance (OPcache, preloading, JIT), choosing an async or long-running runtime such as ReactPHP,
php-security-hardeningPHP security patterns organized by framework — universal PHP, WordPress (nonces, capabilities, escaping), Laravel (Form Requests, guards, Sanctum), and CI3 legacy hardening. Use when implementing authentication, authorization, input validation, output escaping, or any security-sensitive code.
php-testing-patternsPHP testing patterns with PHPUnit, Pest, WordPress test framework (WP_UnitTestCase), Laravel test helpers, Sage testing, and CI3 legacy testing. Use when writing tests, setting up test infrastructure, or choosing a testing strategy.
sage-patternsSage/Roots theme patterns — Acorn service providers, Bud asset configuration, Blade components in WordPress, view composers, and common Sage gotchas with solutions. Use when working with Sage themes or the Roots ecosystem.
woocommerce-patternsWooCommerce development patterns — checkout field customization, cart/order hooks, custom product types, payment gateway skeleton, and HPOS compatibility. Use when extending WooCommerce functionality.
wordpress-architectureWordPress architecture decisions with tradeoffs. Use when choosing a caching, CDN, or Core Web Vitals strategy, deciding on multisite, planning WooCommerce architecture or scaling, evaluating headless WordPress, choosing hosting or a deployment pipeline, planning a site migration or version upgrade,
wordpress-plugin-patternsWordPress plugin development patterns — OOP architecture with PSR-4 autoloading, hook registration, activation/deactivation lifecycle, Gutenberg blocks, AJAX handlers, WP-CLI commands, custom post types, WP_Query, and transients. Use when building WordPress plugins or working with core WordPress API
wordpress-theme-patternsWordPress theme development patterns for classic themes (template hierarchy, functions.php organization, child themes), block/FSE themes (theme.json, block templates, template parts), and hybrid approaches. Use when building or modifying WordPress themes.
wordpress-troubleshootingDiagnostic procedure for a broken WordPress site. Use when a site shows a white screen, a 500, 403, or 404, or a database connection error, runs out of memory, breaks after a plugin or theme change, misses scheduled cron events, or has failing or slow admin-ajax requests.
wp-rest-api-patternsWordPress REST API patterns — registering custom endpoints, permission callbacks, schema validation, response formatting, extending existing endpoints, and webhook handling. Use when building or consuming WP REST API endpoints.