supabase-edge-functions
Guidelines for writing Supabase Edge Functions with TypeScript and Deno runtime. Use when creating or modifying edge functions in supabase/functions/.
Guidelines for writing Supabase Edge Functions with TypeScript and Deno runtime. Use when creating or modifying edge functions in supabase/functions/.
Performance benchmarking expertise for shell tools, covering benchmark design, statistical analysis (min/max/mean/median/stddev), performance targets (<100ms, >90% hit rate), workspace generation, and comprehensive reporting
TODO: [What it does]. Use when [specific triggers]. Example: "Analyzes Excel spreadsheets and generates charts. Use when working with Excel files, .xlsx, spreadsheet analysis, or data visualization." REQUIRED: Include "Use when..." with trigger keywords (file types, domains, tasks). Third person. Max 1024 chars.
Guide creation of AI Developer Workflows (ADWs) that combine deterministic orchestration code with non-deterministic agents. Use when building automated development pipelines, designing AFK agent systems, or implementing the PITER framework.
Design gateway scripts as entry points for agentic coding. Use when creating CLI entry points for agents, designing subprocess-based agent invocation, or building script interfaces for agentic workflows.
Guide creation of meta-prompt templates that encode engineering workflows into reusable, scalable units. Use when creating slash commands that generate plans, designing workflow templates, or encoding team best practices into agentic prompts.
Your approach to handling global error handling. Use this skill when working on files where global error handling comes into play.
Set up task-based multi-agent systems with shared task files. Use when setting up parallel agent execution, designing worktree isolation patterns, or implementing task file coordination.
Central authority for Claude Code sandboxing and isolation. Covers sandboxed bash tool, /sandbox command, filesystem isolation (blocked access, custom paths), network isolation (domain restrictions, proxy support), OS-level enforcement (bubblewrap on Linux, Seatbelt on macOS), sandbox configuration options, escape hatches (dangerouslyDisableSandbox, allowUnsandboxedCommands), and sandbox security limitations. Assists with configuring sandbox settings, understanding isolation mechanisms, and troubleshooting sandbox issues. Delegates 100% to docs-management skill for official documentation.
Use when data operation or statistical analysis tasks do not need full program implementation, and the agent should operate Insyra through CLI/REPL, .isr scripts, or DSL workflows, including environment workflows, reproducible command pipelines, and command selection guidance.
Parallel subagent execution for complex tasks. Use when a task has independent parallel workstreams.
Executes code snippets by saving them to a temporary file and running them via bash commands (e.g., node, python, go run) to test logic or compute results.
Orchestrate multiple worker agents to implement groomed tasks. Use when multiple ready tasks need implementation, when you want autonomous multi-task execution, or when coordinating batch development work. Keywords: coordinator, orchestrator, multi-task, parallel, workers, batch, autonomous.
Guide AI agents to generate complete PageObject pattern web scraper projects using Playwright and TypeScript with Docker deployment. Supports agent-browser site analysis for automated selector discovery. Keywords: scraper, playwright, pageobject, web scraping, docker, typescript, data extraction, automation.
Create an ExecPlan (execution plan) from a PRD, RFC, voice note, or brainstorming blurb, following the repo's PLANS.md. Use when the user asks for an exec plan, execution plan, or ExecPlan, or wants a PRD/RFC turned into a step-by-step plan.
Execute a pending execution plan from the .agent folder. Use when user asks to implement an execplan, execute the plan, run the pending plan, or mentions execplan-pending.md.
Comprehensive, measurement-driven performance optimization for latency, throughput, memory/GC, and tail behavior. Use when the user asks to optimize/speed up, reduce latency (p95/p99), increase throughput/QPS, lower CPU/memory/allocations/GC pauses, profile hot paths, or run a benchmarked perf pass (including JSONL/query-heavy code). Requires before/after measurement on a runnable workload (or an explicit `UNMEASURED` plan) plus a correctness gate. Zig-only CLI iteration where `bench_stats`/`perf_report` are proven before shipping.
Create and manage Codex app automations stored in the local SQLite database (~/.codex/sqlite/codex-dev.db). Use when you need to add, list, update, enable/disable, delete, or run-now automations; edit automation names, prompts, RRULE schedules, or cwd scopes; or inspect automation records while troubleshooting app automation behavior.
Compile and run one of the example programs. Use this when asked to run an example or demo.
Generates scheduled background jobs using Quartz.NET. Includes job definitions, triggers, cron scheduling, dependency injection, and persistent job store configuration.