Developer Tools & Repos Agent Skills for Zed

Invoke when the user wants to start a new game project, set up project scaffolding, onboard into an existing codebase, or initialize…

Invoke when the user works with Unity or asks about C#, MonoBehaviour, DOTS/ECS, Shader Graph, Addressables, UI Toolkit, URP/HDRP, or…

CLI tools for Svelte 5 documentation lookup and code analysis.

Analyze a kernel Oops from the printk buffer in a PearPC memory dump

Use when reviewing code quality - measures decision logic complexity, identifies refactoring candidates, sets quality gates for CI/CD.

Analyzes codebases to understand structure, tech stack, patterns, and conventions.

Use this skill when the user wants to: - Control Android devices, emulators, or simulators - Perform mobile testing, QA automation, or UI…

Enforces Android Automotive OS (AAOS) best practices and architectural patterns for high-quality embedded vehicle applications.

Use when diagnosing an Android app problem (crash, misbehavior, UI anomaly) — reproduces the symptom on a device, gathers an evidence…

Use to find stuck coroutines, leaked jobs, and suspended awaits with no resumer — the concurrency bugs that don't crash but cause hangs…

Use when implementing the data layer in Android or KMP — the Repository pattern's layered error-propagation model (repository as the error…

Use when the user asks for an Android app, Compose UI, Material 3, Material You, Material 3 Expressive, Pixel-style app, foldable/adaptive…

Create production-quality Android app features.

Control and inspect a local Android emulator app through ADB, screenshots, Pillow-based image analysis, and optional desktop coordinate…

Android and Kotlin development patterns — Compose, architecture, coroutines,

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 surface invisible main-thread I/O, leaked closeables, leaked activities, and other policy violations that don't crash but cause…

Global Angular best practices: component lifecycle, clean code, lazy loading with permissions, and *ngFor trackBy performance.

Convert AngularJS controllers into Angular components during modernization.