Index of every page on this site: llms.txt
← All skills

Backend

Server code, business logic, request handling

51 skills ·1.3m stars

  • /backend-patterns

    Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.

    307k GitHub stars

  • /backend-code-review

    Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend code outside `api/`.

    162k GitHub stars

  • /backend-code-review

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `src/backend/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.

    157k GitHub stars

  • /performance-optimization

    Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

    119k GitHub stars

  • /dotnet-backend-patterns

    Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.

    43k GitHub stars

  • /nodejs-backend-patterns

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

    43k GitHub stars

  • Guides PostHog engineers through dashboard widget platform work — ship a new widget_type (WIDGET_REGISTRY, catalog, run_widgets, WidgetCard) or update a shipped type (config, query, layout, RBAC, tile filter bar, list footer, titleHref, throttles). Use for WidgetSpec, widget_specs/, widget-configs.zod.ts, hogli build:openapi, error_tracking_list, session_replay_list, widgetFilters, formatWidgetListCountFooter, widget_query_throttle, or WidgetCard composition. New types need widget-intake confirmation first. Not for MCP batch-add of existing types or adding tiles to a dashboard.

    41k GitHub stars

  • /sending-notifications

    How to send real-time in-app notifications from PostHog backend code. Use when integrating notifications into a new feature, wiring up a notification source (alerts, comments, approvals, pipelines, issues), or choosing the right target type and priority for a notification.

    41k GitHub stars

  • /setup-web-tests

    Set up Python test environment in Claude Code for web where flox is unavailable. Use when you need to run backend tests and `uv sync` fails due to Python version mismatch.

    41k GitHub stars

  • /backend-architect

    Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems.

    34k GitHub stars

  • /backend-dev-guidelines

    Comprehensive backend development guide for Node.js/Express/TypeScript microservices. Use when creating routes, controllers, services, repositories, middleware, or working with Express APIs, Prisma database access, Sentry error tracking, Zod validation, unifiedConfig, dependency injection, or async patterns. Covers layered architecture (routes → controllers → services → repositories), BaseController pattern, error handling, performance monitoring, testing strategies, and migration from legacy patterns.

    34k GitHub stars

  • /backend-to-frontend-handoff-docs

    Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.

    34k GitHub stars

  • /cc-skill-backend-patterns

    Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

    34k GitHub stars

  • /dotnet-backend

    Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.

    34k GitHub stars

  • /frontend-to-backend-requirements

    Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.

    34k GitHub stars

  • /nodejs-backend-patterns

    Comprehensive guidance for building scalable, maintainable, and production-ready Node.js backend applications with modern frameworks, architectural patterns, and best practices.

    34k GitHub stars

  • /senior-backend

    Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.

    34k GitHub stars

  • /opik-backend

    Java backend patterns for Opik. Use when working in apps/opik-backend, designing APIs, database operations, or services.

    23k GitHub stars

  • /replica-backend

    Builds the backend of an app clone: auth, database migrations and access rules, payments with Stripe, email, background jobs and third-party integrations through official APIs only, plus a security checklist. Use when the user says "add login", "set up auth", "wire up the database", "add payments", "connect Stripe", "add Google Calendar", "send emails", "backend for my clone", or when /replica-build is running on fake data.

    10k GitHub stars

  • /backend-patterns

    Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

    6.7k GitHub stars

  • /azure-cloud-migrate

    Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

    3.2k GitHub stars

  • /diagnose-backend-bug

    Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do not use for frontend-only defects or generic logging reviews.

    2.5k GitHub stars

  • /backend-development

    Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

    1.2k GitHub stars

  • /kotlin-backend-jpa-entity-mapping

    Model Kotlin persistence code correctly for Spring Data JPA and Hibernate. Covers entity design, identity and equality, uniqueness constraints, relationships, fetch plans, and common ORM (Object-Relational Mapping) traps specific to Kotlin. Use when creating or reviewing JPA (Java Persistence API) entities, diagnosing N+1 or LazyInitializationException, placing indexes and uniqueness rules, or preventing Kotlin-specific bugs such as data class entities and broken equals/hashCode.

    1.1k GitHub stars

  • /convex-best-practices

    Retired. Points to the skill that replaced convex-best-practices in builder-skills 3.0. Use when /convex-best-practices is invoked by name or the user asks where convex-best-practices went.

    404 GitHub stars

  • /typescript-backend-project-setup

    Sets up NX monorepo for TypeScript backend projects optimized for AI-assisted development. Delegates to NX commands where possible, patches configs as last resort. Triggers on: 'set up typescript backend project', 'create backend project', 'initialize typescript backend', 'create monorepo', or when working in an empty project folder.

    366 GitHub stars

  • /create-a-backend

    Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Daemons, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.

    340 GitHub stars

  • /fastapi-python

    Expert in FastAPI Python development with best practices for APIs and async operations

    311 GitHub stars

  • /neon

    Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, a no-signup database, or pairing Neon with Upstash for cache, Redis, rate limiting, queues, or background jobs.

    117 GitHub stars

  • /clerk-backend-api

    Clerk Backend REST API explorer and executor. Browse tags, inspect endpoint schemas, and execute authenticated requests. Use when listing users, managing organizations, or calling any Clerk API endpoint.

    95 GitHub stars

  • /python-architecture-review

    Comprehensive design architecture review for Python backend applications. Use this skill when users ask you to review, analyze, or provide feedback on backend architecture designs, system design documents, or Python application architecture. Covers scalability, security, performance, database design, API design, microservices patterns, deployment architecture, and best practices.

    93 GitHub stars

  • Defensive backend security review for source code, API servers, auth flows, database access, dependency configuration, secrets handling, file uploads, webhooks, background jobs, and deployment settings. Use when Codex is asked to audit, review, deep research, harden, or find vulnerabilities in a user's own backend or authorized codebase, and to report findings before making fixes.

    70 GitHub stars

  • /convex-quickstart

    Get a barebones Convex + web template running from a one-sentence idea.

    69 GitHub stars

  • /backend-latency-profiler-helper

    Identifies API latency hotspots and bottlenecks with profiling tools, slow endpoint detection, suspected causes, and fix roadmap. Use for "latency profiling", "performance bottlenecks", "slow APIs", or "backend performance".

    64 GitHub stars

  • /clean-ddd-hexagonal

    Design or review backend domain and dependency boundaries using DDD, Clean Architecture, and ports/adapters. Use for aggregate modeling, bounded contexts, use-case isolation, or architecture refactoring; not routine CRUD changes.

    61 GitHub stars

  • /wix-app

    Build and review Wix CLI app extensions — dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, context providers, function libraries, lightbox (popup) behavior, page onLoad contexts, backend APIs, backend events, service plugins, data collections, and App Market readiness. Use when building ANY feature or extension for a Wix CLI app or preparing a Wix app for App Market review. Triggers on: add, build, create, implement, help me, dashboard, widget, plugin, backend, API, event, collection, embedded script, service plugin, Editor React component, context provider, function library, onLoad, on page load, checkout, shipping, tax, discount, SPI, CMS, schema, tracking, popup, lightbox, admin panel, menu item, modal, validate, test, verify, register extension, App Market, app review, submission readiness.

    40 GitHub stars

  • /getting-started

    Set up Encore.ts from scratch. Install the CLI, log in, create an app, check that it runs, and connect Encore's MCP servers, with a pointer to the skill for each step. Ends where building starts. Not for architecture or feature questions.

    30 GitHub stars

  • /go-getting-started

    Set up Encore Go from scratch. Install the CLI, log in, create an app, check that it runs, and connect Encore's MCP servers, with a pointer to the skill for each step. Ends where building starts. Not for architecture or feature questions.

    30 GitHub stars

  • /migrate

    Migrate an existing backend application to Encore. Supports any source framework, targets Encore.ts or Encore Go. Drives a structured DISCOVER → PLAN → MIGRATE workflow with `migration-plan.md` tracking.

    30 GitHub stars

  • /backend-engineer

    Professional backend engineering for production-grade APIs, services, workers, databases, authentication, authorization, integrations, queues, observability, testing, reliability, and security. Use when the agent needs to build, improve, review, debug, or harden backend systems in Node.js, Python, Go, Java, .NET, Ruby, PHP, SQL, NoSQL, REST, GraphQL, WebSockets, event-driven systems, or similar backend stacks. Triggers on requests to build APIs, services, workers, webhook handlers, auth systems, database layers, background jobs, queues, cron tasks, billing flows, or server-side features. Also triggers on requests to fix slow queries, race conditions, deadlocks, failing tests, deployment issues, or to review backend code for security, correctness, and reliability.

    10 GitHub stars

  • /backend-performance-review

    Reviews backend codebases for performance bottlenecks using an evidence-first, workload-driven methodology. Use when investigating latency, throughput, slow endpoints, database or query performance, N+1 queries, connection pool exhaustion, event-loop blocking, lock contention, memory or CPU pressure, queue lag, or timeout and retry storms — and when asked to audit, review, or improve the performance or scalability of a backend service, API, worker, or data layer. Trigger phrases include "performance review", "why is this slow", "audit performance", "find bottlenecks", "will this scale", "review this service for performance", "perf review of this PR". Works on any language, framework, runtime, or datastore.

    8 GitHub stars

  • /python-backend-expert

    Python backend implementation patterns for FastAPI applications with SQLAlchemy 2.0, Pydantic v2, and async patterns. Use during the implementation phase when creating or modifying FastAPI endpoints, Pydantic models, SQLAlchemy models, service layers, or repository classes. Covers async session management, dependency injection via Depends(), layered error handling, and Alembic migrations. Does NOT cover testing (use pytest-patterns), deployment (use deployment-pipeline), or FastAPI framework mechanics like middleware and WebSockets (use fastapi-patterns).

    8 GitHub stars

  • /backend

    Governs backend architecture, API endpoints, REST, GraphQL, database schemas, SQL, ORM, Prisma, Drizzle, migrations, transactions, concurrency, idempotency, and error handling standards.

    6 GitHub stars

  • /backend-numerics

    Use for Chelis IR, backend, and autodiff work where numerical correctness matters. Focuses on evaluator-vs-backend agreement, compile-run harnesses, tolerances, and finite-difference checks.

    5 GitHub stars

  • Provisions, configures, and deploys any backend, database, or third-party service (e.g. Supabase, Firebase, Stripe, Postgres, Auth0, AWS, MongoDB Atlas, Vercel, Resend) through the command line — from first credential to a live, deployed backend — without the agent ever seeing or handling the raw API key/token. Use whenever the user asks to "set up", "connect", "integrate", "configure", "provision", "deploy", or "hook up" a backend/service/API, even without naming the service, or phrases like "add a database" or "get this live." Authenticates via the provider's official CLI/OAuth login where possible; otherwise the user enters credentials directly in their own terminal into `.env`, never through chat. Checks the user's plan/subscription tier and fetches current official docs when exact CLI steps aren't already known. Use instead of guessing at setup/deploy steps from memory, and never as a substitute for asking the user for missing credentials.

    4 GitHub stars

  • /init-backend

    Initialize a production-oriented backend project using Node.js with TypeScript, Python with FastAPI and uv, or Go. Use when the user asks to initialize, scaffold, bootstrap, or set up a backend.

    1 GitHub star

  • /backend-architecture

    Enforces professional Node.js/Express backend architecture — API design, database modeling, security, auth, and production-readiness standards. TRIGGER when: user builds or modifies any backend route, API endpoint, database schema, auth system, middleware, or server configuration. Also trigger when user asks about JWT, CORS, MongoDB, SQL, environment variables, deployment security, or backend file structure. TRIGGER also when: user's backend is crashing, leaking errors, or has security gaps they want to fix. DO NOT TRIGGER when: user is working on frontend components, CSS, React state, or any client-side UI task with no backend involvement.

  • /backend-best-practices

    Use when finding architectural bugs in a backend repo

  • Bootstraps complete backend with Apso, including API setup, database configuration, and testing. Triggers when user needs to create backend, setup API, or initialize server.

  • /encapsulation-backend-config

    Published skill from SDLC Skills Hub (SRS Architect themed). Extracted and structured for agent use.

  • /fastapi-backend

    Mtrini Workspace — open-source AI development environment by Compiwer AI. Your AI. Your code. Your workspace.