Results for “backend”

Build backends with Appwrite — open-source Backend-as-a-Service. Use when a user asks to set up user authentication, manage a database without writing backend code, handle file storage and uploads, add realtime subscriptions, set up cloud functions, build a mobile or web app backend, replace Firebase with an open-source alternative, or self-host a BaaS platform. Covers auth, databases, storage, functions, realtime, and SDK integration for web, mobile, and server-side.

The English summary is being prepared. Showing the original description.

Trace uploaded files through extraction, conversion, parsing, and reconstruction of saved objects in a CTF sandbox, an isolated competition environment. Preserve original and derived files, distinguish visible validation from backend behavior, and document the smallest reproducible processing chain.

• Trace an uploaded file to its backend effect
• Investigate archive extraction and preview generation
• Compare visible validation with backend file handling

Build and review C#/.NET APIs and business backends using concrete implementation patterns. Cover asynchronous operations, service dependencies, database access, configuration, caching, and tests to structure application code and examine quality and performance issues.

• Designing a new .NET Web API
• Reviewing asynchronous C# code
• Improving database access and caching

Build Node.js APIs and backend services with Express/Fastify. The skill guides authentication, database integration, error handling, and operational practices such as logging and health checks, which report whether a service is working.

• Build a REST API with Express/Fastify
• Add authentication and database integration
• Organize middleware and error handling

Guide cmux backend changes with consistent rules for Effect, a TypeScript library for structured error handling. Covers Cloud VM state, database migrations, provider integrations, and authentication and payment checks so changes follow the intended architecture.

• Implementing API error handling
• Updating Cloud VM lifecycle logic
• Preparing database migrations

Build and operate websites, internal tools, APIs, and databases on Kortix Apps using its CLI or SDK. Covers deployment, sign-in, scaling, persistent storage that survives updates, snapshots, and restoring earlier application releases.

• Publish a static website or single-page app
• Build an internal CRM with team sign-in
• Create an API or database backend

Guide remote Windows app control using UI Automation, which identifies controls by names and roles. Covers text entry, buttons, window management, screenshot checks, and handling desktop session problems when the connected backend supports these features.

• Select and activate a Windows app button by name
• Enter text into a specific app field
• Minimize, restore, or maximize a window

Build reusable Convex backend components with their own database tables and a small API, the functions an app calls. It guides component structure, app integration, authentication boundaries, and checks for generated code and type errors.

• Adding a local component to an existing Convex app
• Extracting reusable backend logic
• Building an integration with its own tables

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.

The English summary is being prepared. Showing the original description.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

The English summary is being prepared. Showing the original description.

Analyzes the user's business problem and recommends the right backend integration approach — Web API, AI Web API (generative summaries / grounded search), Server Logic, Cloud Flows, or a combination — for a Power Pages site, then routes to the appropriate specialized skill. Use when the user wants to add backend integration, connect to data, add AI summaries, or needs help deciding which backend approach to use.

The English summary is being prepared. Showing the original description.

Fix "backend exists on a draft version but isn't reachable from the new Compute deploy" bugs after `fastly compute publish`. Use when: (1) You ran `fastly service backend create --autoclone` (or any dashboard/CLI change that creates a draft version) but did not activate that draft, (2) You then ran `fastly compute publish` which appeared successful but your backend / ACL / header / dictionary change is missing from the active version, (3) Compute code returns backend-not-found errors or misroutes requests, (4) You're surprised to see your draft version number "skipped over" in the version chain. Root cause: `fastly compute publish` clones from the currently-active version, not from the latest draft, so dashboard changes made in an un-activated draft get stranded.

The English summary is being prepared. Showing the original description.

World-class backend engineering - distributed systems, database architecture, API design, and the battle scars from scaling systems that handle millions of requestsUse when "backend, api, database, postgres, mysql, mongodb, redis, graphql, rest, authentication, authorization, caching, queue, background job, webhook, migration, transaction, n+1, rate limit, server, node.js, python, go, backend, api, database, architecture, performance, reliability, security" mentioned.

The English summary is being prepared. Showing the original description.

Multi-backend database security auditor. Audits Supabase, Firebase (Firestore/RTDB/Storage/Functions/Remote Config), MongoDB (self-hosted + Atlas), self-hosted PostgreSQL, and self-hosted MySQL for RLS/rules misconfigurations, exposed credentials, auth bypasses, MongoBleed (CVE-2025-14847), pgBouncer CVE-2025-12819, mysql_native_password drift, ghost auth, and storage exposures. Use this skill whenever the user mentions database security, RLS or rule audits, security review, penetration testing a vibe-coded app, checking if their DB is exposed, hardening a backend, fixing security rules, or auditing apps built with Lovable/Bolt/Replit/Cursor/Claude Code on any of these backends. Trigger on phrases like 'is my app secure', 'check my database', 'audit my Firebase', 'audit my MongoDB', 'audit my Postgres', 'audit my Supabase', 'is my DB exposed', or any cross-backend variant ('audit my full stack').

The English summary is being prepared. Showing the original description.

Comprehensive backend API development skill for building robust, scalable APIs. Use when creating new endpoints, services, or backend functionality. Keywords: API, backend, endpoint, service, REST, GraphQL, server, controller, route

The English summary is being prepared. Showing the original description.

Frappe backend guidance for Python and backend-adjacent JavaScript surfaces such as client interaction patterns, hooks, APIs, patches, scheduler logic, reports, and server-side review. Use when implementing or reviewing Frappe backend behavior.

The English summary is being prepared. Showing the original description.

pyfixest demeaner_backend="cupy64" (including its CPU fallback when cupy is absent) is NOT numerically identical to the default numba backend and does NOT drop fully-absorbed/collinear regressors the same way. Use when: (1) adding demeaner_backend="cupy64" to existing pf.feols/fepois calls changes the printed coefficient table, (2) a regression report suddenly gains rows with absurd estimates (e.g. coef 435.8, SE 7106) for controls absorbed by the fixed effects, (3) diffing outputs before/after a backend change, or (4) anything parses a pyfixest text report by line position.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Backend Python Specialist IA — Expert en développement backend Python (FastAPI, Django, SQLAlchemy, Celery, async, type safety)

The English summary is being prepared. Showing the original description.

Backend Rust Specialist IA — Expert en développement backend Rust (Actix, Axum, Tokio, zero-cost abstractions, WASM)

The English summary is being prepared. Showing the original description.

Backend Node.js Specialist IA — Expert en développement backend Node.js (Express, Fastify, NestJS, Prisma, real-time, WebSockets)

The English summary is being prepared. Showing the original description.

Use when the user wants a backend-only action plan — API endpoints, services, models, migrations, jobs and their tests — 'plano de backend para o endpoint X', 'plan the orders API'. Writes .planning/feat/features/{slug}/plan.md with the PWDEVIA method. Do NOT use for UI work (feat-frontend), full features spanning backend and UI (feat-feature), writing code (feat-exec) or quick 1–3 file fixes (feat-quick).

The English summary is being prepared. Showing the original description.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.

The English summary is being prepared. Showing the original description.

Build or review Java Spring Boot backends using examples for web APIs, separate application layers, and database access. Covers input validation, error handling, caching, background processing, and logging to guide maintainable implementations.

• Designing web APIs and separating application layers
• Reviewing database access and transactions
• Adding input validation and centralized error handling