backend▌

TypeScript patterns for type-first development, making illegal states unrepresentable, and exhaustive handling. \n \n Use discriminated unions, branded types, and const assertions to encode business rules in the type system and prevent invalid states at compile time \n Validate at system boundaries with Zod schemas as single source of truth; infer TypeScript types automatically to keep types and validation in sync \n Enforce exhaustive handling with never checks in switch statements and default

Production-ready FastAPI project structure with async patterns, dependency injection, and layered architecture. \n \n Provides recommended directory layout separating API routes, models, schemas, services, and repositories for maintainable codebases \n Includes base repository pattern for generic CRUD operations and service layer for business logic encapsulation \n Demonstrates async/await patterns throughout, from database sessions to route handlers, with proper lifespan management and middlewa

API routes in Expo Router for server-side logic, secrets, and third-party integrations on EAS Hosting. \n \n Create routes with +api.ts suffix in the app directory; export named functions for HTTP methods (GET, POST, PUT, DELETE) \n Handle query parameters, headers, JSON bodies, and dynamic route segments; add CORS headers for web clients \n Access server-side secrets via process.env ; set variables locally in .env or via eas env:create for production \n Deploy to EAS Hosting (Cloudflare Workers

Comprehensive pre-deployment verification pipeline for Django projects covering migrations, linting, tests, security, and configuration. \n \n Runs 12 sequential phases: environment validation, code quality checks (mypy, ruff, black, isort), migration safety, test coverage analysis, security scanning (pip-audit, bandit, gitleaks), and Django-specific configuration verification \n Includes coverage targets by component (models 90%+, views 80%+, overall 80%+) and pre-deployment checklist covering

sentry-node-sdk

Cargo-based fuzzing for Rust projects using libFuzzer with integrated sanitizer support. \n \n Requires nightly Rust toolchain and works best with library crate structure; automatically enables AddressSanitizer by default for memory error detection \n Provides cargo fuzz init scaffolding, harness templates, and corpus/artifact management; supports structure-aware fuzzing via the arbitrary crate for type-driven input generation \n Includes coverage analysis integration, dictionary support for for

Table-driven tests, subtests, benchmarks, fuzzing, and golden files for Go TDD workflows. \n \n Covers the RED-GREEN-REFACTOR cycle with step-by-step examples for writing tests before implementation \n Includes table-driven test patterns for comprehensive coverage, error cases, and parallel execution with t.Run() \n Provides benchmarking techniques for performance analysis, memory allocation tracking, and comparative benchmarks across input sizes \n Supports fuzzing with seed corpus and property

$21

Deterministic resource management with context managers, cleanup patterns, and streaming state accumulation. \n \n Covers class-based and decorator-based context managers for sync and async resources, with unconditional cleanup guarantees even on exceptions \n Includes patterns for database connections, file handles, connection pools, and dynamic resource management via ExitStack \n Provides streaming response patterns with efficient state accumulation, metrics tracking, and time-to-first-byte m

Convert existing projects into serverless Apify Actors with language-specific SDK integration. \n \n Supports JavaScript/TypeScript (with Actor.init() / Actor.exit() ), Python (async context manager), and any language via CLI wrapper \n Provides structured workflow: apify init to scaffold, apply SDK wrapping, configure input/output schemas, test locally with apify run , then deploy with apify push \n Includes input and output schema validation, Docker containerization, and optional pay-per-event