847건 · 관련도순
Autonomous coding agent. Delegate any task that involves understanding, writing, or running code — from a GitHub issue, a bug report, or a user request. It explores, implements, and verifies on its own.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose active BIRD daemon incidents across config, runtime, environment, sockets, logs, source, and tooling. Use when BIRD fails to start or reload, crashes, loses sessions/routes, behaves differently after lint passes, or when birdcc and bird -p disagree. Collect read-only evidence first, protect routing secrets, and route isolated config edits to bird-agent or pure implementation research to bird-source-explorer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, discover, lint, format, and validate BIRD 2/3 routing-daemon projects with the @birdcc toolchain. Use for bird.conf, bird2.conf, bird3.conf, bird6.conf, .bird/.bird2/.bird3 files, bird.config.json, birdcc.config.json, include graphs, BIRD filters and protocols, birdcc init/lint/fmt/lsp, or bird -p checks. Treat BIRD 1 as legacy and verify it with the actual BIRD 1 binary. Route editor and CLI installation to birdcc-installer, GitHub Actions to birdcc-cicd, runtime incidents to bird-troubleshooting, and implementation archaeology to bird-source-explorer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws — mANDATORY parallel execution patterns (30x speedup), CloudWatch statistics syntax, Cost Explorer aggregation, output token limits, and common pitfalls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Billing — analyze, break down, and report AWS costs and bills. Covers cost breakdown by service, account, or usage type; monthly/daily billing trends; cost anomaly detection; RI/SP utilization; cost forecasting; credit/discount analysis; and multi-account cost comparison. Uses anti-hallucination rules, mandatory currency/credit detection workflow, and reusable Cost Explorer functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Cost Optimization — aWS native cost optimization using Compute Optimizer, Trusted Advisor cost checks, Savings Plan analysis, Cost Explorer, and resource rightsizing. Covers EC2 rightsizing, idle resource detection, Savings Plan and Reserved Instance recommendations, and cost anomaly detection. Use when optimizing AWS infrastructure costs with native AWS tools.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a throwaway prototype to answer a design question, as UI variations or a state-model walkthrough. Use when the user types /prototype, wants to sanity-check whether a state model or logic feels right, wants to explore what a UI should look like, or as the prototype step of the web design flow with brainstorm or grill before the final plan goes to plan-canvas (annotate the running prototype with the plan-canvas annotation tool).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Searches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware payment tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence gathering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Signals scout that watches a PostHog project's most-viewed dashboards and insights for recent anomalies — sudden bursts, drops, flat-lines, and trend breaks at the daily or hourly level. It discovers what the team actually looks at (view counts, dashboard access), curates a durable watchlist in the scratchpad, and balances re-checking known high-value insights (exploit) against discovering new ones (explore) across runs, since no single run can cover a busy project. Anomalies are scored by robust deviation from each insight's own seasonality-matched baseline; it emits a finding only when a move clears the confidence bar, otherwise it updates the baseline memory and closes out empty. Self-contained peer in the signals-scout-* fleet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore PostHog's Inbox — the surface where signal reports surface as actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by ID or title, or wants to see which signal sources are configured. Covers listing, filtering, and drilling into reports, plus pointers to the deeper `signals` skill when raw signals or semantic search are needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explore and diagnose a PostHog endpoint's execution logs — error messages, failed runs, cache misses, slow runs, or unexpected row counts during endpoint invocations. Use when the user says "my endpoint is failing", "show me the logs for endpoint X", "what error did endpoint Y produce", "why did endpoint Z return no rows", "is this endpoint hitting cache", or "check the last N runs". Focused on a single named endpoint's runtime log entries, not project-wide auditing or query performance profiling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Launch multiple explore subagents in parallel to investigate architecture, data models, auth, APIs, and deployment. Synthesize into an onboarding document.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.