Guide for modern game anti-cheat architecture, Windows kernel monitoring, and detection tradeoffs. Use this skill when analyzing EAC, BattlEye, Vanguard, FACEIT AC, kernel callbacks, handle protection, manual-map detection, boot-start drivers, BYOVD, DMA threats, or behavioral telemetry in game security research.
Guide for PCIe DMA threat modeling, FPGA-based memory access, and defensive implications in game security. Use this skill when researching pcileech, BAR and TLP behavior, page-table walking, IOMMU or VT-d, device impersonation, firmware mimicry, or DMA detection and mitigation in game security research.
Guide for Windows kernel internals and security mechanisms used in game protection and low-level research. Use this skill when working with drivers, IRQL-sensitive callbacks, EPROCESS, ETHREAD, MMVAD internals, IOCTL paths, DSE, PatchGuard, HVCI, PiDDBCache, MmUnloadedDrivers, or kernel memory inspection.
A central entry point for a set of embedded-development skills. It guides users through installing all or selected skills and offers candidates when a vague request such as “build,” “flash,” or “debug” does not identify one skill.
A build helper for embedded projects made with Keil MDK, a development environment for microcontroller software. It reads the project files, runs the Keil command-line build, and finds the firmware output.
A Saleae Logic 2 tool for recording digital signals and decoding common device protocols. A logic analyzer observes electrical signal changes; I2C, SPI, UART, and CAN are communication formats used by electronic devices.
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Use when the user reports jank, dropped frames, janky scrolling, slow click or typing response, poor INP, slow LCP, layout shifts (CLS), unresponsive pages, or asks to debug rendering, animation, or interaction performance in a browser app.
Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.
Self-evolution system for AI coding assistants. Six integrated mechanisms: (1) Real-time logging of errors, corrections, and failures to errorlog.md, (2) Silent 3-gate checkpoint before every code change, (3) periodic error review that scans errorlog.md and updates a categorized tracker, (4) rule accumulation loop…
Full ownership of the VitePress documentation site — writing pages, maintaining structure, i18n translations (EN/RU), blog posts, config updates, and custom theme components. Use for any documentation task.
Implement frontend features, components, pages, and modules. Expert in React 19, strict TypeScript, semantic HTML, accessible markup, CSS layout, and maintainable code patterns. Use for any frontend implementation task.
Deep expertise in Yii 2 framework internals — modules, debug module architecture, component system, DI container, event system, request lifecycle, and extension points. Use when implementing or modifying the Yii 2 adapter, writing collectors, or debugging integration issues.
Automate browsers with Puppeteer CLI scripts and persistent sessions. Use for screenshots, performance analysis, network monitoring, web scraping, form automation, JavaScript debugging.
Debug and trace C/C++/Rust programs with the GNU Debugger (GDB) without blocking the agent. Use when you need to set tracepoints, inspect variables, or monitor a running process while staying responsive to the user.
Check the PHP runtime with server-info, its version, OS, and loaded extensions. Reach for it when a Mate tool itself fails or a capability is missing and you suspect the environment, a missing extension or an old PHP, rather than the app or its config. Not for diagnosing app behavior (profiler, log investigation) or…
Resolve which dependency versions are actually installed, from composer show and composer.lock, when diagnosing version-specific behavior such as a method, argument or class that does not exist in the release that is really running. For the PHP runtime itself (version, OS, loaded extensions) use the…
A fault-finding tool that uses an error stack or failed tests to narrow the problem to likely root-cause code. It uses test-failure patterns and the structure of the source code to navigate relevant areas.
A general bug-diagnosis toolkit for apps that use the included BugReport logging library. It collects error and network logs, traces crashes, monitors performance, and helps prepare structured reports.