Desenvolvimento

Minimal codex-native calibration loop. Use to detect leaks or major gaps across mirrored skills and agents with fixed checks.

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.

Analysis-only planning — classify and scope a task without writing code; outputs a structured plan to .plans/active/.

Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".

Use when implementing any feature or bugfix, before writing implementation code

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

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

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".

Use when a complex task needs parallel decomposition into independent subtasks, when multiple agents must work simultaneously without conflicts, or when recursive task delegation is required

Minimal codex-native analysis loop. Use for issue/PR/problem analysis before implementation with measurable gates.

Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".