What problem does it solve? Dispatcher and Apache HTTPD configurations in AEM as a Cloud Service often suffer from low cache hit ratios, redirect chains, and tail-latency hotspots, and tuning them without cloud-specific guardrails risks breaking validator contracts or managed defaults. ## Core Features & Use Cases - Baseline-to-After Verification: Captures metrics and cache evidence before changes, then compares post-change results using the core-7 MCP tools (validate, lint, sdk, trace_request, inspect_cache, monitor_metrics, tail_logs). - Cloud Guardrails Enforcement: Preserves immutable includes, reserved probe paths, and CDN-vs-Dispatcher ownership boundaries required by AEMaaCS validators. - Scenario Playbooks: Provides eight tuning playbooks covering cache hit ratio, invalidation blast radius, redirect latency, static assets, query-parameter fragmentation, tail latency, persisted queries, and cache operations. - Use Case: When a site's cache hit ratio drops below 70%, use this Skill to identify top MISS URLs, apply targeted cache-rule changes, validate them against cloud contracts, and prove the improvement with before/after metrics. ## Quick Start Ask the assistant to analyze the dispatcher configuration for low cache hit ratio and propose verified performance optimizations for the cloud deployment.
