Specifies the correct Babel configuration for NativeWind to ensure proper processing and avoid conflicts.
Look up Babylon.js APIs, import paths, examples, loaders, Vite integration, and browser runtime behavior.
בדיקת CVR לפני פרסום כל שינוי ב-BabyMania. הפעל לפני פרסום sections, templates, product pages, homepage, navigation, landing pages, עדכוני sticky bar, trust badges, CTA, ניווט.
יוצר סקילים חדשים לקלוד קוד לפי סטנדרט BabyMania. הפעל כאשר המשתמש מבקש ליצור סקיל חדש, לתכנן אוטומציה של workflow חוזר, לסטנדרטיזציה של תהליך.
טוען מצב מינימלי של מערכת BabyMania לפי סוג משימה. הפעל תמיד בפתיחת סשן חדש, כאשר המשתמש אומר "מה המצב", "תבדוק מצב", "state", "מצב פרויקט", "מה קרה", "היכן אנחנו", "תסכם",…
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are…
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is…
Multi-agent coordination for parallel development. Use when asked to parallelize work, coordinate multiple agents, or manage tasks across a codebase.
Agentic instruction set for mission-critical back-end development, specializing in autonomous API engineering, distributed systems, and proactive server-side verification.
Build NestJS backend following Orchestrator AI patterns. Module/Service/Controller structure, A2A protocol compliance, transport types, error handling.
Tell the Assistant to leave the current cmux workspace alone — no Observer calls, no /cleanup or /merge-when-ready sends, no awaiting cards.
Protect an OpenClaw workspace with repeatable Synology NAS backups, integrity checks, and safer restores instead of ad hoc file copying.
Use GitHub Backup when an agent needs to mirror repositories, release assets, and gists into local storage on a schedule, instead of manually exporting GitHub content repo by repo.
Backblaze integration. Manage data, records, and automate workflows. Use when the user wants to interact with Backblaze data.
use for application service, transaction boundary, use case orchestration, domain event, outbox, idempotency, DTO mapping, and backend application-layer changes.
Ensure backend build readiness for Espresso Engineered. Use when backend code/config changes are made or when a feature/task is wrapping up to suggest running `npm run…
Load the minimal Cookmate backend context fast. Use only for backend tasks to avoid repeated discovery: Prisma schema, domain modules, repositories, route patterns, shared route…
Úsala cuando el usuario pida escribir la lógica de negocio de un servicio, escribir queries o modelos de MySQL, encriptar contraseñas o manejar tokens JWT.
You are a senior backend engineer operating production-grade services under strict architectural and reliability constraints.
Backend Developer Agent. 코드 개발, 디버깅, 기능 구현을 담당합니다. 개발, 코딩, 디버그(debug), 버그 수정, 기능 구현 관련 요청 시 사용됩니다.
Senior Backend Developer with 10+ years Java and 5+ years Spring Boot experience. Use when implementing Spring Boot features, writing Java code, creating REST APIs, working with…
Guidelines for backend development in C++ and Elixir/Phoenix, covering modern language features, best practices, and production-ready patterns.
use for aggregate boundary, entity, value object, invariant, state transition, domain service, domain event, policy object, primitive obsession, and domain model design.
Scaffolds backend features including new domain entities, new properties on existing entities, and new business operations.
Post-change backend integration sanity check. Run after frontend changes to verify API contracts, auth patterns, subscription hooks, and data flow integrity.
Backend Implementation Workflow Agent. Backend만 구현이 필요한 경우 사용합니다. API 추가, 서비스 로직 구현, DB 스키마 변경 등을 오케스트레이션합니다.
Use when designing a backend feature or API endpoint for reconGG — defining data models, request/response contracts, validation, error handling, and how it maps to API-SPEC.md.
Coordinates backend development tasks (APIs, services, databases). Use when implementing REST APIs, business logic, data models, or service integrations.
Authentication middleware for Express.js and Node.js applications. Use when building Express APIs that need JWT authentication, OAuth, or custom auth strategies.
Runs backend quality checks including formatting, linting, and tests. Use before commits, to verify code quality, or when the user says "check backend", "run backend tests",…
Use when implementing backend APIs, data persistence, or external integrations. Enforces TodoWrite with 25+ items.
Make the backend survive its dependencies: timeout every outbound call, retry idempotent-only with exponential backoff + jitter, add circuit breakers and bulkheads, define a…
Use when the task involves server-side API routes, middleware, business logic, authentication, database queries, or infrastructure configuration.
Backend engineer focused on simplicity, bug elimination, and clean code. Use when user mentions "simplify backend", "fix backend bugs", "clean up code", or "make backend perfect".
Generates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.
Generate backend tests (unit, integration, mocks). Auto-invoke when user says "write test for", "add test", "test this", or "create test".
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 hand — from…
Automatically runs required Go checks after any backend code changes. Ensures go vet, gofmt, and go test pass before commits.
Backendless integration. Manage data, records, and automate workflows. Use when the user wants to interact with Backendless data.
Automate Backendless tasks via Rube MCP (Composio). Always search tools first for current schemas. — from general/automation
Backfill missing GitHub streak dates using the streakify.sh script. Use this when the user asks to backfill dates, fix missing streak days, or catch up on streak commits.
Playbook สำหรับ backfill historical data และ reconcile inconsistencies ระหว่าง data sources
How to backfill a newly-added repo or team — the enumerate-then-drain loop, the single-event contract, and resume-safe todo discipline.
Use when the user says "/backfill-feature", "backfill the ADR", "this feature has no ADR", "I need to document what's already there before I change it", or wants to capture an…
Walks every daily journal entry in a date range (default this year) and appends a "Body track" section BELOW the original verbatim content.
Правило работы — все долгие команды запускать в фоне (run_in_background), не блокировать диалог
Design layered backgrounds that make PNG assets blend naturally. Use when hero assets float awkwardly on gradients, multiple images don't blend, or need seamless…
Summarizes raw background check data into structured executive reports with risk categorization (GREEN/YELLOW/RED).
Orchestrates multiple AI agents (Claude, Codex, Gemini) for parallel implementation in the background.
Orchestrates robust background job implementation: design job → TDD implementation → configure retry/discard strategies → test failure scenarios → production monitoring.
Implement background job processing systems with task queues, workers, scheduling, and retry mechanisms.
Use when designing a background-job system, choosing between BullMQ / Sidekiq / RQ / Temporal / SQS, deciding queue-vs-workflow, sizing concurrency vs rate limits, building…
Background job processing with BullMQ, Inngest, Trigger.dev, Upstash QStash. Use when implementing async tasks, scheduled jobs, event-driven workflows, retries, or dead letter…
Designs background job processing systems with queue integration (BullMQ/Celery), job definitions, retry policies, exponential backoff, idempotent execution, and monitoring hooks.
Run marketplace diff and reconciliation in the background while surfacing per-source progress to the UI without blocking startup.
Orchestrates multiple AI agents (Claude, Codex, Gemini) for parallel planning in the background with auto-save. Agents continue running even when session hits context limits.
To remove a finished background process from the manager list, clear a stopped process after it exits so it no longer appears in listings.
To read logs from a managed background process, fetch recent output (head or tail) for a process so you can inspect its stdout/stderr.
To check if the Background Process Manager is running, get the server status and confirm it is available.
To see all managed background jobs, list processes so you can find their IDs, states, and names.