sasler

Inspect, triage, implement, test, and reply to unresolved BrainRot pull request review comments while preserving exact model ownership for game files. Use for human, Copilot, or automated PR feedback and requested changes.

Prepare and publish a compliant BrainRot pull request by checking scope, metadata, documentation, tests, commit conventions, branch safety, push state, and PR content. Use when the user asks to commit, push, publish, open, or create a pull request for completed work.

Create, improve, or fix BrainRot game implementations while enforcing exact AI model ownership, standalone-file architecture, quality requirements, desktop-first gameplay, metadata maintenance, and documentation updates. Use for any change under public/games or any new game/version request.

Build, substantially revise, or visually review BrainRot Three.js games. Use for any game implementation that imports Three.js or creates a THREE.WebGLRenderer, including art direction, authored 3D forms, local GLB/image assets, rendering budgets, test hooks, diagnostics, and active-play visual verification.

Validate BrainRot repository changes with process-safe, change-scoped local checks while leaving the complete lint, build, and Playwright gate to required pull request CI. Use after implementation, before committing or opening a PR, or when diagnosing test and build failures.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

Prepare a BrainRot repository work session on a new task branch created from the latest remote main branch. Use when starting a new task, initializing a fresh coding session, or when the user asks to create a branch before implementation.

Create clean, reviewable commits for TroubleScout by staging logically, writing emoji-prefixed messages, and following repo safety rules (no secrets, no force-push, no bypassing hooks).

Create and update TroubleScout GitHub issues with clear repro steps, environment details (Windows/PowerShell/.NET), and actionable acceptance criteria.

Keep TroubleScout’s GitHub Copilot SDK integration current by verifying the installed Copilot CLI + GitHub.Copilot.SDK versions, updating when needed, and following the official usage guidance.

Validate APIs and patterns for TroubleScout by checking official Microsoft references and code samples (.NET SDK/C#/.NET 10, and PowerShell automation via the Microsoft.PowerShell.SDK .NET package) before implementing.

Use official Microsoft documentation to answer questions for TroubleScout (.NET SDK/C#/.NET 10, PowerShell 7.x, Windows Server, WinRM, publishing and security guidance).

Automates the full PR lifecycle after a task is complete. Creates a branch, commits, pushes, opens a PR, waits for GitHub Copilot code review, triages feedback, dispatches model-matched sub-agents to fix valid issues, and replies to review comments.

Standard workflow for implementing any feature, bug fix, or change in CafeMaestro. Enforces TDD, multi-model code review, version bumping, changelog updates, PR creation, and GitHub Copilot auto-review follow-up. Use this skill whenever asked to implement, fix, or change functionality.