1.1천건 · 관련도순
Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up notebook-connector configuration for Exasol AI workflows through the Secrets Python API. Covers secure config store (`scs`) creation, the `AILabConfig` and `StorageBackend` key sources, backend-specific config values such as `db_host_name`, `db_schema`, `storage_backend`, and `huggingface_token`, Python validation, and handoff to downstream notebook-connector skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and `tsc` catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows, rate limiting, billing, full-text search, email, presence, and more. Use whenever a project uses Convex or needs ANY backend or persistence: writing code under convex/, starting a new full-stack app, prototyping an idea, or adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting). Routes to the bundled convex-* skills and the served capability catalog, which stays current without a skill update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convex is the backend agents get right on the first try: an all-TypeScript reactive platform where the database, server functions, scheduling, file storage, auth, and realtime sync are one type-safe system, every function is a transaction, and `tsc` catches most mistakes before deploy. Ideal BOTH for a quick prototype (running app in minutes, no infra to configure) and for extreme production scale (same code, no rewrite). Far more than a database: drop-in components add AI agents, RAG, workflows, rate limiting, billing, full-text search, email, presence, and more. Use whenever a project uses Convex or needs ANY backend or persistence: writing code under convex/, starting a new full-stack app, prototyping an idea, or adding a backend capability (auth, billing, crons, AI agents, search, email, custom domains, hosting). Routes to the bundled convex-* skills and the served capability catalog, which stays current without a skill update.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend Rust v2 — Actix, Axum, tokio, zero-cost abstractions, performance
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend Node.js v2 — Express, NestJS, tRPC, WebSockets, scaling
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend Python v2 — FastAPI, SQLAlchemy, async, Pydantic, deployment
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when it is time to make the backend follow the Lean model — regenerate Kotlin from Lean, implement the generated interfaces (UseCase, QueryService, Repository, Entity), wire every generated contract test, make the build green, then run the design and SQL reviews. Backend comes after the human confirmed the screens.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use after a backend build succeeds or whenever authentication, authorization, actor/identity handling, external service calls (IdP, JWKS, DB, clock), logging, observability, configuration or error contracts are in play — delegates to the backend-design-reviewer agent for a design-quality review of the current branch.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rust 製バックエンド HTTP サーバーフレームワーク fandhe-backend のリファレンス。 fandhe-backend-core / -http / -routes。Server, BoundServer, Router（merge）, Handler。 拡張点 Middleware（on_response_with_status）/ UpgradeHandler / RequestGate / Interceptor。 Diagnostics, StreamingResponse, SetCookie session（__Host-）, sans-IO HTTP/1.1, graceful shutdown。 プラグイン cors, websocket（WsSender）, graphql, openapi, webrtc, jwt（JwtGate, JwtPolicy）, csrf（CsrfGate）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build real-time, reactive backend applications with Convex using TypeScript queries, mutations, and actions with automatic reactivity and optimistic updates. Use when building real-time collaborative applications, implementing reactive data synchronization, writing serverless backend functions, creating queries that auto-update, implementing mutations with transactional guarantees, handling file uploads with Convex storage, implementing authentication with Convex Auth, designing reactive database schemas, or building applications requiring instant data synchronization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Architect scalable backend services using layered architecture, dependency injection, middleware patterns, service classes, and separation of concerns. Use when building API services, implementing business logic layers, creating service classes, setting up middleware chains, implementing dependency injection, designing controller-service-repository patterns, handling cross-cutting concerns, creating domain models, implementing CQRS patterns, or establishing backend architecture standards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor apps so backend owns runtime truth and UI only projects snapshots. Use when tools have split authority. NOT for cosmetic UI work or new features before drift is removed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reactive, type-safe, production-grade backends. ALWAYS use this skill when the user asks to build, plan, design, or implement backend features, APIs, data models, server logic, database schemas, web apps, full stack apps, or mobile apps. This includes planning and architecture discussions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.