pranav8494

Use when defining or auditing SLOs/SLIs/error budgets, designing production observability (metrics, alerting, dashboards), reviewing production readiness, reducing operational toil, writing runbooks or postmortems, designing infrastructure as code, or planning chaos experiments. Distinct from devex, this skill covers production reliability and the outer loop (deploy → monitor → incident → postmort

Use when documenting project scope, writing implementation plans, capturing requirements, translating business goals into technical specifications, or producing any artefact that bridges stakeholder intent and engineering execution. Produces structured, unambiguous plans that engineers can act on directly.

Use when you are unsure which specialist to invoke, when a task spans multiple roles, when you want the system to plan before acting, or when you need parallel specialist agents dispatched to complete a complex task. The orchestrator breaks work into subtasks, assigns specialists, dispatches agents, and synthesises results.

Use when building UI components, designing layouts, writing CSS, working with React or other frontend frameworks, improving accessibility, optimizing web performance, or any task involving the visual and interactive layer of a web application.

Use when implementing any feature or bugfix in a Kotlin/Spring Boot service, covers layer conventions, idioms, testing, and observability

Use when designing SEO strategy, conducting keyword research, auditing technical SEO issues (crawlability, indexability, Core Web Vitals, structured data), planning content strategy for organic search, analysing search performance data, evaluating competitor positioning, building link acquisition plans, advising on site architecture for search, handling international SEO or hreflang, diagnosing ra