Desenvolvimento

Use when legacy prompts or older framework flows reference `elite-developer` and you need the modern runtime to resolve that capability cleanly.

Migrate from Cypress or Selenium to Playwright. Use when user mentions \"cypress\", \"selenium\", \"migrate tests\", \"convert tests\", \"switch to playwright\", \"move from cypress\", or \"replace selenium\".

Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Esta skill revisa a autenticação e autorização de aplicações ASP.NET Core, incluindo esquemas, validação JWT, segurança de cookies/sessões, autorização baseada em políticas, confiança de claims, isolamento multi-tenant, caminhos de escalonamento de privilégios e cobertura de testes negativos.

Use when legacy prompts or older framework flows reference `code-reviewer` and you need the modern runtime to resolve that capability cleanly.

Fix failing or flaky Playwright tests. Use when user says \"fix test\", \"flaky test\", \"test failing\", \"debug test\", \"test broken\", \"test passes sometimes\", or \"intermittent failure\".

Coordinate a full Galyarder Framework release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.

Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.

Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.

Dead code cleanup and consolidation specialist. Removes unused code, duplicates, and refactors for maintainability.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes