'backend' 검색 결과

Backend-neutral image generation: create new raster images and looping GIF/WebP animations through the local one-file image-use CLI (formerly chatgpt-imagegen), using the user's ChatGPT subscription by default, the Codex backend as fallback, or an optional Gemini subscription — no API key or daemon. Triggers: image generation, generate an image, draw a picture, 画图, 画一张, 生成图片, 生图, 配图. Use for photos, illustrations, icons, hero banners, mockups, sprites, concept art, animation loops, and figures for documents, proposals, blog posts, or READMEs; save outputs in the workspace. Auto mode uses the logged-in ChatGPT browser via chrome-use. Gemini users can pass --backend gemini or agy. Proactively propose useful figures while authoring long-form content. Do not use for editing existing images, SVG/vector work, code-native graphics, established icon systems, explicit high-quality or transparent API output, or end-user image-generation services.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backendless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Backendless data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code in WooCommerce projects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when users want to practice or simulate Java, C++, Go, Golang, mixed-stack, or general backend technical interviews, including resume-based and job-description-based interview preparation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assists with building real-time reactive backends using Convex. Use when creating databases with automatic client sync, reactive queries, file storage, scheduled functions, or full-text and vector search. Trigger words: convex, reactive backend, real-time database, useQuery, useMutation, convex functions, convex schema.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill for any Python backend work in this project: building FastAPI endpoints, writing service functions, defining Pydantic/SQLModel schemas, running Alembic migrations, or debugging 422 errors. Essential for authentication and authorization patterns — setting up get_current_user, is_superuser checks, admin-only guards, role-based access, and dependency injection chains like Depends(). Also covers middleware, background tasks, async SQLAlchemy sessions, ORM relationship loading, and request/response design. Activate whenever the question involves Python API code, FastAPI patterns, or backend architecture in this codebase. Not for frontend, Docker, CI/CD, or infrastructure.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for the Kimix HTTP serve system — FastAPI backend + TypeScript/Vite frontend. Use when adding new backend endpoints, modifying the session manager, changing the frontend API client, or understanding how data flows from backend to UI. Covers dummy_app.py, dummy_session_manager.py, sse_cli.py, and src/app/.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

How to determine which backlog backend a project is configured to use, and what to do with the answer. Use when about to call a backend-specific tool, choosing between a GitHub-only and a Beads-native operation, or reporting which store a result came from.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Add a new tool to the backend OpenAI function calling system. Use when user mentions "new tool", "add tool", "backend function", "agent capability", or wants to extend what the AI agent can do.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Appwrite is an open-source backend platform for web, mobile, and AI apps. This skill helps agents use Appwrite's real services—Auth, Databases, Storage, Functions, Messaging, Realtime, and Sites—instead of inventing a generic backend workflow.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Amplication is an open source developer platform for generating production-ready backend services and scaffolding from a visual workflow. This skill fits agents that need to help with service generation, codebase setup, schema-driven backend work, or self-hosted Amplication environments.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Policy for the cross-model council: when to hand off to an installed sibling plugin's own slash command (`/codex:*`) versus dispatching our `delegation-runner` (backend: codex|agy|…), which backend to pick, what permission posture to use, and the fan-out/cost discipline that applies regardless of backend — plus the council layer built on that substrate: which play to run, how a cast gets picked from the project roster, budget guardrails, and where project policy/commission config lives. Consult before delegating out to a peer agentic CLI, before choosing between a sibling plugin's command and our runner, before choosing a permission posture, before fanning out more than one external delegation concurrently, or before running a council play (`/…:council-run`).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Backend conventions and patterns. Use when working on API routes, dependency injection, or hexagonal architecture in the backend.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide for testing code built on Simba 5 (leader election and distributed locks). Use when writing or reviewing tests for LeadershipListener callbacks, runWhileLeader / schedule work, partition groups, locks, @SimbaScheduled / @SimbaPartitioned beans, fencing-token resources (FencingSpec), LeaseBackend implementations (LeaseBackendSpec), or deterministic failover tests with InMemoryLeaseBackend and VirtualScheduler.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Agent skill for dev-backend-api - invoke with $agent-dev-backend-api

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Delegate implementation to Codex or to a sandboxed Claude Code (`claude -p`), have a model from the other vendor review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex or a sandboxed Claude to write code, mentions handing off / delegating implementation to one of those backends, asks for a cross-vendor review of delegated code, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing or reviewing TypeScript backend tests — Jest unit tests for services/controllers (mocked Prisma) or Supertest integration tests against a real isolated PostgreSQL test database. Triggers on edits to `*.service.test.ts`, `*.controller.test.ts`, `*.integration.test.ts`, service/controller/API test files (`.ts`, not `.tsx`) under `**/__tests__/`, or mentions of "backend test", "service test", "API test", "database test".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DraftForge test infrastructure for writing backend unit tests, Playwright E2E tests, and managing test data population. This skill should be used when writing new tests, adding test fixtures, creating populate functions for new features, adding Playwright E2E specs, using login/auth fixtures, creating test users/orgs/leagues/tournaments, or understanding the test data architecture. Covers backend Django tests via Docker, Playwright config (projects, workers, sharding), test auth endpoints that expose backend login to frontend, and feature-isolated test data patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.