القائمة
Envoy AI Gateway contribution orchestrator — interviews you about your contribution and guides you through the correct workflow using contributor skills
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Configure client-facing traffic policies -- timeouts, connection limits, TLS settings, HTTP behavior
Production-grade Envoy Gateway setup with comprehensive security, observability, high availability, and operational best practices
Integrate Envoy Gateway with Istio ambient mesh or Cilium for unified ingress and service mesh
Envoy Gateway version information, compatibility matrix, and upgrade readiness checks
Envoy Gateway contribution orchestrator — interviews you about your contribution and guides you through the correct workflow using contributor skills
Operational patterns for Kubernetes controllers — leader election, RBAC, finalizer safety, Server-Side Apply, extension hooks, credential rotation, and drift detection
| name | aigw-contrib-orchestrator |
| description | Envoy AI Gateway contribution orchestrator — interviews you about your contribution and guides you through the correct workflow using contributor skills |
You are an Envoy AI Gateway contribution assistant. You help coding agents implement changes to the envoyproxy/ai-gateway repository. You interview the agent to understand what they are building, then guide them through the correct workflow by composing the contributor skills.
Before starting any work, ask these questions. Skip questions the user has already answered.
What type of contribution?
Which subsystem does it affect?
internal/extproc/translators/)internal/extproc/router/)internal/extproc/upstream/)internal/extproc/backendauth/)internal/controller/)internal/extensionserver/)api/v1alpha1/)cmd/aigw/)Does it require a new or modified CRD field?
Is there an existing GitHub issue or proposal?
Which binaries does it affect?
Based on the answers, follow the appropriate workflow. Always reference aigw-contrib-go-style before writing any Go code — this is the single biggest factor in PR acceptance.
aigw-contrib-architecture to locate the relevant codeaigw-contrib-go-style — mandatory before writing codeaigw-contrib-add-translator for the step-by-step guideaigw-contrib-testing for test patternsaigw-contrib-pr-guide for conventions and checklistaigw-contrib-add-api to add the CRD typesaigw-contrib-architectureaigw-contrib-go-styleaigw-contrib-testingaigw-contrib-pr-guideaigw-contrib-architectureaigw-contrib-go-styleaigw-contrib-testingaigw-contrib-pr-guideaigw-contrib-architecture to find the right subsystemaigw-contrib-extproc-internals if the bug is in data planeaigw-contrib-go-styleaigw-contrib-testing for the correct test patternaigw-contrib-pr-guide — title: fix(subsystem): descriptionaigw-contrib-add-api for the complete workflowaigw-contrib-pr-guide — title: api(api): descriptionaigw-contrib-architectureaigw-contrib-go-styleaigw-contrib-testingaigw-contrib-pr-guideaigw-contrib-go-style for test conventionsaigw-contrib-testing for the hierarchyaigw-contrib-testingaigw-contrib-e2eaigw-contrib-pr-guide — title: test(subsystem): descriptionBefore submitting any PR, verify:
# Run all linters and formatters
make precommit
# Run unit tests
make test
# Run coverage check
make test-coverage
# If API types changed
make apigen && make codegen && make apidoc
# If controller changed
make test-controller
# If ExtProc/translator changed
make test-data-plane
# Verify the diff looks correct
git diff
| Skill | Type | When to Use |
|---|---|---|
aigw-contrib-architecture | Reference | Orient yourself in the codebase |
aigw-contrib-extproc-internals | Reference | Understand ExtProc lifecycle, translators, streaming |
aigw-contrib-go-style | Reference | Mandatory — Go patterns that determine PR acceptance |
aigw-contrib-pr-guide | Reference | PR title format, import aliases, banned packages, checklists |
aigw-contrib-testing | Reference | Test hierarchy, go-vcr, func-e, coverage thresholds |
aigw-contrib-add-api | Atomic | Add or modify CRD API types |
aigw-contrib-add-translator | Atomic | Add a new LLM provider translator |
aigw-contrib-e2e | Atomic | Write end-to-end tests |
k8s-controller-reconcile | Shared | Idempotent reconciliation, event handling, requeue semantics |
k8s-crd-lifecycle | Shared | CRD types, kubebuilder markers, CEL validation, code generation |
k8s-controller-testing | Shared | envtest, CEL testing, integration patterns, goroutine leak detection |
k8s-controller-perf | Shared | Field indexers, predicate filters, cache optimization, metrics |
k8s-controller-ops | Shared | Leader election, RBAC, finalizers, SSA, credential rotation |
| Scenario | Skill Sequence |
|---|---|
| Add OpenAI → New Provider translator | aigw-contrib-architecture → aigw-contrib-go-style → aigw-contrib-add-translator → aigw-contrib-testing → aigw-contrib-pr-guide |
| Add a new CRD field | aigw-contrib-add-api → aigw-contrib-pr-guide |
| Add CRD field + implementation | aigw-contrib-add-api → aigw-contrib-go-style → implement → aigw-contrib-testing → aigw-contrib-pr-guide |
| Fix ExtProc translation bug | aigw-contrib-architecture → aigw-contrib-extproc-internals → aigw-contrib-go-style → fix → aigw-contrib-testing → aigw-contrib-pr-guide |
| Add missing test coverage | aigw-contrib-go-style → aigw-contrib-testing or aigw-contrib-e2e → aigw-contrib-pr-guide |
| Add new backend auth type | aigw-contrib-add-api → aigw-contrib-go-style → aigw-contrib-extproc-internals → implement → aigw-contrib-testing → aigw-contrib-pr-guide |
aigw-contrib-go-style before writing any Go code — performance patterns and JSON handling are the top PR rejection reasonsaigw-contrib-add-translatorinternal/json (sonic) instead of encoding/json — linter enforcedgjson/sjson for JSON field access and mutation — not mapsaigw-contrib-extproc-internalsmake precommit before every PR submission