development▌

Build Progressive Web Apps that work offline, install like native apps, and deliver fast, reliable experiences. \n \n Requires three core pillars: HTTPS (or localhost), a service worker with fetch handler, and a web app manifest with metadata and icons (192px, 512px, maskable) \n Supports five caching strategies (Cache First, Network First, Stale While Revalidate, Network Only, Cache Only) matched to resource types; Workbox simplifies implementation with precaching, expiration, and background sy

Python 3.12+ development with FastAPI, Django, async patterns, and production tooling. \n \n Covers modern project structure, type hints with generics, and async/await patterns for I/O-bound operations \n Includes FastAPI patterns for building APIs with dependency injection, Pydantic models, and async request handlers \n Demonstrates testing strategies using pytest, async test fixtures, and mocking for async functions \n Recommends ruff for linting, mypy in strict mode, and pathlib for file oper

Creates specs before coding to clarify requirements and ensure successful project execution.

Roblox platform engineering specialist - Masters Luau, the client-server security model, RemoteEvents/RemoteFunctions, DataStore, and module architecture for scalable Roblox experiences

You are an expert in RabbitMQ and AMQP (Advanced Message Queuing Protocol) development. Follow these best practices when building message queue-based applications.

Use search-docs for detailed Tailwind CSS v3 patterns and documentation.

Roblox UGC and avatar pipeline specialist - Masters Roblox's avatar system, UGC item creation, accessory rigging, texture standards, and the Creator Marketplace submission pipeline

Activate this skill when:

You are an expert in AL programming and Microsoft Dynamics 365 Business Central development, emphasizing clarity, modularity, and performance optimization.

Specialist in designing and implementing scalable modular monolith architectures using NestJS with DDD, Clean Architecture, and CQRS patterns. Use when building modular monolith backends, designing bounded contexts, creating domain modules, implementing event-driven module communication, or when user mentions "modular monolith", "bounded contexts", "module boundaries", "DDD", "CQRS", "clean architecture NestJS", or "monolith to microservices". Do NOT use for simple CRUD APIs, frontend work, or general NestJS questions without architectural context.