Android and Kotlin development patterns — Compose, architecture, coroutines,
Use to extract concrete numbers and slice-level evidence from a `.perfetto-trace` captured by `android-perfetto-capture`.
Use to capture Perfetto system traces from a connected Android device — the input for any timing, threading, jank, or "is this on the main…
Use when you need empirical proof a code path actually executed — branch entries, callback fires, coroutine continuations, suspect early…
Use INSTEAD of git bisect when investigating a regression between two refs (releases, branches, "it worked yesterday") — especially when…
Use BEFORE fixing any non-trivial bug. Write a test that fails because of the bug, watch it fail, then fix the bug until the test passes…
Use to flip framework-level diagnostics without code changes — verbose framework logging (`log.tag.<Tag> VERBOSE`), view-bounds overlay…
Use to prove (or disprove) that a state actually changed between two points — "did the dialog dismiss?", "did this navigation actually…
Use to surface invisible main-thread I/O, leaked closeables, leaked activities, and other policy violations that don't crash but cause…
Use to answer questions logging can't — "did this run, on what thread, for how long, in what overlap with frame boundaries?" Wrap suspect…
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
Build, compose, or style any Spiderly Angular admin-panel UI — pages, cards, panels, dashboards, buttons, tables, dialogs, empty/loading…
Global Angular best practices: component lifecycle, clean code, lazy loading with permissions, and *ngFor trackBy performance.
Convert AngularJS controllers into Angular components during modernization.
Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration.
Write intentional, minimal, context-aware code that avoids generic AI-generated patterns.
Generates high-quality, predictable, and efficient .agent/skills/ directories based on user requirements.
API design and developer experience for TypeScript libraries.
Use when working on the backend API (packages/api).
Compare API specifications to detect breaking changes.
API class validation rules for Scopy plugins.