Developer Tools & Repos Agent Skills for Microsoft Copilot

Build wallet-connected applications with the Phantom Connect SDK for Solana.

Evidence-based phase completion enforcement for /dev:feature.

Validate readiness to advance between development phases.

Phoenix context design — creating/splitting contexts, Scope (1.8+), Ecto.Multi, PubSub, routers, plugs, controllers.

Build Phoenix perpetual futures integrations on Solana with the Rise SDK.

Reference — PHPickerViewController, PHPickerConfiguration, PhotosPicker, PhotosPickerItem, Transferable, PHPhotoLibrary, PHAsset…

When to activate: PHP concurrency, ReactPHP, Swoole coroutines, PHP Fibers, async PHP, queued jobs, Laravel queues, Symfony Messenger…

Guides CodeIgniter 4 application architecture — Controllers, Models (Query Builder, not an ORM), Entities, the Validation library, Filters…

When to activate: idiomatic PHP, PHP 8.3, readonly properties, enums, match expression, attributes, named arguments, nullsafe operator…

When to activate: PHP performance, OPcache, APCu, Redis caching, Xdebug profiling, Blackfire, autoloader optimization, composer…

Use when working with physics bodies, collision shapes, raycasting, areas, rigid bodies, ragdolls, soft bodies, Jolt physics, and physics…

Maps Pi packages, extensions, and skills to this repository's Nix ownership.

Discover what exists in a Pikku project — functions, tags, middleware, permissions, HTTP routes, channels, schedulers, queues, and more.

Zero-install localhost tunnels over SSH via Pinggy.

Pinia state management for Vue 3 including store creation, actions, getters, plugins, and DevTools integration.

Pipedrive integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`.

Generates consistent pixel art animation sprite sheets and Aseprite-compatible metadata for seamless game engine integration.

Bootstrap browser-based games with PixiJS 8 and a modern retro/vector aesthetic (Geometry Wars, Asteroids, Tempest, Tron).

Dispatched after a task lands at `in_review` to produce a structured CTO-grade verdict on the work and its PR.

Use when deciding which layer a piece of code belongs in (domain, application, or infrastructure), when business rules are mixed with…

Use when renaming routes, packages, modules, APIs, configuration keys, or persisted contracts while existing consumers may remain.