Explorar skills

This skill should be used when starting work on any project that uses tdder. It establishes interaction style, commit conventions, documentation discipline, and skill-trust principles. Invoke automatically alongside other tdder skills.

Use this agent when you need to safely modify legacy code that lacks tests. It applies Michael Feathers' dependency-breaking techniques from \"Working Effectively with Legacy Code\" to identify seams, plan characterization tests, and recommend safe transformation paths.

Coordinate multiple agents on complex game development features using battle-tested spawn recipes. Triggers on: "multi-agent coordination", "team orchestration", "feature handoff", "cross-domain collaboration", or when a task spans multiple specialist domains (combat system, narrative feature, UI overhaul, performance pass, launch prep). Do NOT invoke for single-domain tasks -- route directly to t

This skill should be used when the user asks to "add a feature using TDD", "fix a bug with TDD", "do TDD", "red-green-refactor", "write a failing test first", "use test-driven development", "start TDD", "test first approach", "TDD loop", "TDD cycle", or mentions TDD workflow, baby steps, guessing game, or red-green-refactor cycles. Not applicable for pure refactoring without new tests.

This skill should be used when implementing features using Acceptance Test Driven Development. It guides through the RED/GREEN/REFACTOR cycle with explicit permission gates between phases.

Orchestrator role in the Unfolding Specs process. Launches the PO, forwards unsolicited Sensei guidance, handles genuine commissioner issues, and resumes the workflow through the platform-specific live task mechanism.

Use this agent when you need to evaluate test quality using Dave Farley's 8 properties of good tests. It produces a weighted Test Quality Score (1-10 per property) with letter grades and prioritized improvement recommendations.

Always load this skill when working on a Quarkus project, when the quarkus-maven-plugin is present in pom.xml, or when project setup has already chosen Quarkus before the pom.xml exists yet. It provides Quarkus-specific patterns and gotchas that complement the java and maven skills.

This skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub issues and pull requests. Always-on security rules plus optional workflow conventions.

This skill should be used when running end-to-end browser tests on pages affected by a PR. Uses agent-browser CLI to map changed files to routes and capture screenshots.

This skill should be used to attempt an automated single-file fix for a GitHub issue. Creates a branch, fixes, tests, opens a PR, and labels for auto-merge or human review.

Invoke when the user asks about testing strategy, bug tracking, playtest methodology, regression testing, release certification, QA automation, or bug triage. Triggers on: "testing", "bug", "QA", "regression", "certification", "playtest methodology", "test plan", "release gate". Do NOT invoke for usability testing (use game-ux-designer) or balance validation (use game-balance-check). Part of the A