.cursor

Planning and orchestration patterns for turning messy context into an incremental, verifiable execution plan. Use when you need a step-by-step strategy before coding or delegating to subagents.

Instrumenta frontends Vite 3 + TypeScript com OpenTelemetry para Grafana, Tempo e Mimir (traces, Web Vitals, page views, cliques, erros). Use ao adicionar telemetria em novas páginas, configurar RUM ou revisar código de instrumentação existente.

Perform QA Playwright code review by applying the perspectives of maintain, add-fixture, and add-flow agents; produce a consolidated improvement summary focused on maintenance, quality, and standardization. Use when the user asks for a code review, review of specs/test-data, or improvement summary.

Manages correlation-id in .NET applications using AsyncLocal for async context isolation. Use when implementing correlation-id tracking, HTTP request/response correlation, logging integration, or when working with distributed tracing in .NET applications.

Instruments .NET applications with OpenTelemetry spans following best practices. Use when adding distributed tracing, instrumenting HTTP requests, SOAP calls, database operations, or when implementing observability with OpenTelemetry in .NET Framework 4.8 or .NET 8 applications.

Manages correlation-id in Node.js/TypeScript applications using AsyncLocalStorage for async context isolation. Use when implementing correlation-id tracking, HTTP request/response correlation, logging integration, or when working with distributed tracing in Node.js applications.

Instruments Node.js/TypeScript applications with OpenTelemetry spans following best practices. Use when adding distributed tracing, instrumenting HTTP requests, database operations, or when implementing observability with OpenTelemetry in Node.js applications.

Guides frontend markup and structure for easy Playwright testing: semantic HTML, accessible roles and labels, stable selectors (data-testid). Use when writing or reviewing UI components, forms, or pages that will be tested by QA.

Add or extend a Playwright fixture in fixtures/index.ts (e.g. inputs loader, authenticated request). Use when the user asks to add a fixture, inject test-data per flow, or authenticated API context.

Add a new test flow to the QA Playwright project: create tests and test-data folders for the flow, add inputs and optional builder, write specs from fixtures. Use when the user asks to add a flow, new flow, or test suite for a feature.

Add a new Playwright test (API or UI) following project conventions: import from fixtures, use test-data when applicable, Arrange-Act-Assert. Use when the user asks to add a test, create a test, or add a test for a flow.

Add or extend test data for a QA Playwright flow: create or edit inputs.json and optional builder.ts in test-data, use lib/data-factory for generated data. Use when the user asks to add inputs, test data, or a builder for a flow.

Enforce QA Playwright project conventions when editing tests or project files: import from fixtures only, use test-data for inputs, follow directory structure. Use when editing specs, refactoring, or when the user asks to align code with project standards.

Code quality principles including SOLID, clean code, design patterns, and code smells. Use when refactoring code, reviewing code quality, or when implementing design patterns in any language.

Conventional Commits specification, format, validation rules, and semantic-release integration. Use when creating commits, suggesting commit messages, validating commit format, or when working with semantic-release.

Idempotency concepts, patterns for APIs REST, database operations, and implementation strategies. Use when implementing idempotent operations, handling retries, or when ensuring operations can be safely repeated in any language.

Safely update Jira cards by reading card information, identifying changes, and adding structured comments using the official Atlassian MCP. Use when updating Jira cards with progress, changes, or status updates.

Performance optimization patterns including caching, async operations, profiling, and performance best practices. Use when optimizing code performance, implementing caching strategies, or when working with async/await patterns in any language.

Security best practices, OWASP Top 10, input validation, and secure coding patterns. Use when implementing authentication, authorization, input validation, or when addressing security vulnerabilities in any language.

Testing patterns, frameworks, and best practices for unit, integration, and end-to-end tests. Use when writing tests, implementing TDD/BDD, or when working with test frameworks in any language.