القائمة
Deep analysis mode. Use when facing a complex bug, design decision, or problem that needs careful step-by-step reasoning before acting.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run performance benchmarks on AWS EC2 (bare-metal or regular instances) with a reproducible launch → tune → measure → terminate workflow. Use for ANY AWS benchmarking — CPU/memory/IO/database/application, NUMA-related or not: choosing + launching an instance, one-time key-pair/security-group setup, OS kernel tuning (hugepages, governor, THP, NUMA balancing), EBS provisioning, A/B methodology, collecting results, and (critically) terminating the instance when done so it stops costing money. Triggers on: "benchmark on AWS/EC2", "bare-metal EC2", "launch an instance to test", "A/B benchmark", "clock sweep / NUMA benchmark", "pgbench/HammerDB on EC2". For the PostgreSQL-buffer-manager clock-sweep specifics, this pairs with the pg-numa-benchmark skill (which uses this one for the AWS substrate).
Run PostgreSQL clock sweep benchmarks on bare-metal EC2 instances. Covers AWS setup, instance launch (r8i.metal-96xl / m6i.metal), OS tuning, PG build (stock + patched), pgbench A/B testing, HammerDB TPC-C, and result collection. Use when benchmarking PostgreSQL buffer manager changes on NUMA hardware. The generic AWS benchmarking substrate (launch/tune/A-B/terminate) is in the aws-benchmark skill; this layers the PostgreSQL specifics on top.
Hard-won lessons for working on the Nix-managed AI agent configs in modules/home-manager/ai/ (the Bedrock-backed agents pi, claude, maki, hermes, codex, plus kiro-cli, and the LiteLLM proxy). Use this skill ONLY when editing files under modules/home-manager/ai/ or debugging agent auth/telemetry/model routing. Covers: telemetry-off enforcement, thinking-effort ceilings, the two Bedrock auth paths (bearer vs SigV4), model-reachability verification, patching pipx/venv tools, and the CI expectations for this repo. Triggers on: editing modules/home-manager/ai, "LiteLLM proxy", "Bedrock auth", "agent telemetry", "thinking effort", "kiro-cli config".
Date-based release tagging conventions for this maintainer's personal repos (nix-config and other single-author repos). Use this skill ONLY when actually cutting a release or creating/pushing a git tag — the commit→push→tag→push-tag flow, the vYYYY.MM.DD[.N] format, and the deliberate maintainer exceptions to the "never push to main / never force-push" rules. Triggers on: "tag a release", "cut a release", "ship this", "create a tag", "vYYYY.MM.DD".
How to run coordinated sub-agent teams (worker → reviewer → re-reviewer) and the Bedrock model-dispatch rules for sub-agents. Use this skill ONLY when spawning/dispatching sub-agents (e.g. Pi's Agent tool, parallel task fan-out) or debugging a sub-agent that dies instantly. Triggers on: "sub-agent", "subagent", "dispatch agents", "parallel agents", "Agent tool", "sub-agent finished in <2s / 0 tool uses".
Research the PostgreSQL community via the agora MCP server (https://pg.ddx.io/mcp/). Use when investigating PostgreSQL internals or extension development, reviewing or writing patches, understanding historical design decisions, finding related prior art, or tracing a feature through 76k+ pgsql-hackers messages and the upstream/master git history.
| name | think-hard |
| description | Deep analysis mode. Use when facing a complex bug, design decision, or problem that needs careful step-by-step reasoning before acting. |
Stop and think deeply before doing anything.
Process:
Do NOT jump to a fix. The goal is understanding, not speed.
