716건 · 관련도순
Orchestrates multi-step tasks autonomously using a 3-tier agent hierarchy (Director/Manager/Worker). Use when user says "run this end-to-end", "handle everything", "execute all tasks", or needs parallel task execution with queuing, course correction, and session resume. Provides FIFO task queue, escalation policy, git worktree isolation, and context persistence across agent sessions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pick one open GitHub issue off this repository's queue, implement the fix, and open a pull request for it. One issue and one PR per run. Use when the user asks to burn down the issue backlog, or when the issue-burndown workflow invokes it. It never merges, never closes an issue, never edits .github/workflows/, and never acts on an issue from outside the organisation unless a maintainer has opted it in.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register completed local agent work with Neondeck so Neon can watch PRs, show notes, and queue bounded review assistance when allowed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Single-mainline governance for deployless repositories. Use after a deployless audit when a repo needs trunk-based branch rules, branch protection, contribution guidance, review gates, merge queue policy, AI PR intake rules, or agent-ready mainline practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AI PR intake and multi-agent governance for deployless repositories. Use when a repo has high-volume bot or agent PRs, parallel agent work, noisy low-context PRs, merge-queue pressure, CI exhaustion, duplicate fixes, ownership confusion, or review bottlenecks that threaten a single-mainline delivery model.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run AltoRank through its hosted MCP server: readiness audits, Search Console, keyword research, and SEO drafts into a review queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implements and reviews mobile API integration across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for HTTP clients, pagination, request cancellation, concurrent token refresh, resumable uploads and WebSocket lifecycle. Durable offline mutation queues belong to mobile-offline-sync.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adds a per-form settings panel to the JetFormBuilder Gutenberg form editor sidebar — registers REST-exposed post meta on the form CPT, enqueues a block-editor JS bundle, and registers a panel via the JFB-specific 'jet.fb.register.plugins' filter using @wordpress/components (TextControl, SelectControl, ToggleControl) and JFB's useMetaState hook for two-way binding to post meta. Use when a companion plugin needs settings that vary per form (e.g. upload folder, file size limit, integration target) instead of (or in addition to) site-wide defaults from the global Settings page. Triggers on mentions of "JFB form sidebar", "JFB form settings panel", "form-level settings", "useMetaState", "jet.fb.register.plugins", "jet-form-builder/editor-assets/before", or scaffolding a JFB companion plugin that needs per-form config.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claim one live GitHub queue item, implement it end to end, run fail-closed gates and independent verification, then open a draft PR. Use for one ready-to-implement issue or the implementation routine.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Classify GitHub issues into the factory's live label queue and write an auditable snapshot. Use for backlog triage or a scheduled triage run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn a ready-to-spec queue item into an approved plan through explicit human gates. Use when an item needs scope decided before code exists, when planning a feature, or before starting a migration. Runs interactively - not for unattended routines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scheduled health sweep that closes the factory loop - reads CI failures, recent commits, dependency and security advisories, and live queue labels, then files issues and writes an immutable run record. Use for the nightly or weekly monitor routine.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drain acc's deliberation queue — open/waiting brain_frames checkpointed by headless runs — via acc_act(runtime="continue").
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Memory management and FreeRTOS context for the Megahub ESP32 project. Use when dealing with heap allocation, stack size, task creation, inter-task communication, semaphores, queues, or any ESP32 memory constraints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build messaging applications using Azure Service Bus SDK for JavaScript (@azure/service-bus). Use when implementing queues, topics/subscriptions, message sessions, dead-letter handling, or enterpri...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Service Bus SDK for Python messaging. Use for queues, topics, subscriptions, and enterprise messaging patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Celery — celery worker management, task monitoring, queue routing, Flower dashboard analysis, and task result tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Buildkite — buildkite CI/CD pipeline and agent management. Covers build pipeline status, agent pool health, artifact management, build annotations, and cluster queue monitoring. Use when checking build status, investigating failures, managing agents, or reviewing pipeline configurations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Lambda Deep — deep AWS Lambda analysis covering function inventory, cold start profiling, memory optimization, concurrency patterns, layer dependency auditing, dead letter queue health, event source mappings, and cost estimation. Goes beyond basic metrics to identify optimization opportunities.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Eventbridge — aWS EventBridge event bus management, rule analysis, target health monitoring, and schema registry exploration. Covers event pattern matching, rule invocation metrics, dead-letter queue analysis, cross-account event routing, and event replay.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); debugging and troubleshooting errors or unexpected behavior on Supabase projects (HTTP errors, Postgres errors, RLS surprises, permission denied, schema cache issues, timeouts, Edge Function crashes, Realtime drops, Storage failures) and reading or querying logs (Logs Explorer, ClickHouse).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.