backend▌

Scalable backend architecture patterns for Node.js, Express, and Next.js applications. \n \n Covers RESTful API design, repository pattern for data abstraction, service layer separation, and middleware pipelines for request processing \n Includes database optimization techniques: query selection, N+1 prevention, transactions, and Redis caching strategies \n Provides authentication and authorization patterns: JWT validation, role-based access control, and rate limiting implementations \n Features

Comprehensive AI agent skill for all Google Workspace document operations — Docs, Sheets, Slides, Drive, Gmail, Calendar, Chat, Forms, Admin SDK, and Apps Script — via official REST APIs.

Complete reference for writing, validating, and interpreting OpenAPI Specification 2.0 (Swagger) documents. \n \n Covers all core schema elements: Swagger Object root, Info/Contact/License metadata, Paths, Operations, Parameters (path, query, header, body, formData), Responses, and Schemas with composition and polymorphism support \n Includes security definitions for Basic auth, API Key, and OAuth2 flows (implicit, password, application, accessCode) with scope and requirement objects \n Provides

Expert guidance for Django Celery task design, configuration, error handling, and production monitoring. \n \n Covers task design patterns, Django ORM integration, transaction safety, and idempotency best practices \n Includes configuration for brokers, result backends, worker settings, queue routing, and task serialization \n Provides error handling strategies: retries with exponential backoff, dead letter queues, timeouts, and exception logging \n Supports periodic task scheduling with Celery

Apache Maven configuration, dependency management, and multi-module project setup for Java builds. \n \n Covers POM structure, lifecycle phases (validate through deploy), and plugin configuration with practical examples \n Supports single-module, multi-module, and library project types with BOM-based dependency management \n Includes troubleshooting guidance for common issues like dependency conflicts, version mismatches, and build memory problems \n Provides Maven commands for dependency analys

Production-ready patterns for authenticating, transforming, and reliably integrating third-party APIs. \n \n Covers authentication methods including API keys, OAuth 2.0, and JWT with secure credential management \n Provides structured error handling, exponential backoff retry logic, and client-side rate limiting with configurable windows \n Includes webhook verification via HMAC signatures, request/response transformation, and pagination handling patterns \n Demonstrates REST client patterns, ti

Expert guidance for designing Zapier and Make automations that scale without complexity. \n \n Distinguishes when workflows belong in Zapier (simple, fast, maximum integrations) versus Make (complex branching, data transformation, budget optimization) \n Covers three core patterns: basic trigger-action, multi-step sequential chains, and conditional branching with different actions based on conditions \n Identifies critical anti-patterns including typing in dropdown fields, missing error handling

For production apps requiring reliable, unlimited RPC access.

Programmatic orchestration of Pulumi infrastructure operations across multiple stacks and applications. \n \n Supports both local source (existing Pulumi projects) and inline source (embedded programs) architectures, enabling flexible deployment patterns from simple to complex multi-stack scenarios \n Handles multi-stack orchestration with dependency sequencing, parallel independent deployments, and cross-stack output passing for coordinated infrastructure provisioning \n Provides programmatic c

Unit test external REST API integrations with WireMock HTTP mocking and request verification. \n \n Stub HTTP responses with configurable status codes, headers, and JSON bodies; verify request details including headers, query parameters, and request bodies \n Test error scenarios (4xx/5xx responses, timeouts, malformed responses) without calling real APIs or hitting rate limits \n Use dynamic port allocation to avoid conflicts in parallel test execution; automatic cleanup between tests via JUnit