Explorar skills

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

연구 논문(PDF/arXiv URL)을 분석하여 실행 가능한 코드로 변환합니다. 논문 복제, 알고리즘 구현, 연구 재현 요청 시 자동으로 활성화됩니다. "이 논문 구현해줘", "paper2code", "논문 코드로 변환" 등의 요청에 반응합니다.

Use when designing or architecting Rust applications, creating comprehensive project documentation, planning async/await patterns, defining domain models with ownership strategies, structuring multi-crate workspaces, or preparing handoff documentation for Director/Implementor AI collaboration

Apply this opinionated workflow when modernizing legacy systems: strangler fig pattern, branch by abstraction, characterization tests, incremental monolith decomposition, framework upgrades, feature-flagged migration with rollback.

This skill should be used to promote or demote a user's flag-targeting role across Supabase users.role and the Flagsmith identity trait.

Use this agent when you need a formal quality report with severity-scored findings and a prioritized refactoring roadmap. Use pattern-recognition-specialist for quick pattern checks; use this agent when you need a formal report to plan refactoring work.

This skill should be used when working on Java projects with JUnit tests that have layered preconditions, expensive shared setup (servers, databases, provisioned users), or complex scenario trees. Trigger phrases include "nested fixture", "fixture pattern", "scenario tree", "layered test setup", or when the user is writing integration tests with multiple levels of dependent setup/teardown. Complem

Invoke when the user asks about creative vision, game pillars, core fantasy, design direction, art style decisions, scope arbitration, or creative conflicts. Triggers on: "vision", "pillars", "creative direction", "core fantasy", "tone", "aesthetic", "creative conflict". Do NOT invoke for mechanics design (use game-designer) or technical architecture (use game-technical-director). Part of the Alte

This skill should be used when triaging legacy local todo files in todos/. For GitHub issues, use ticket-triage agent.

Participates in brainstorm and planning phases to assess technical implications, flag architecture concerns, and identify engineering risks for proposed features. Use individual engineering agents (review, research, design) for focused tasks; use this agent for cross-cutting technical assessment during feature exploration.

Orchestrates the legal domain -- assesses legal document posture, recommends actions, and delegates to legal specialist agents. Use individual legal agents for focused tasks; use this agent for cross-cutting legal strategy and multi-agent coordination.