メニュー
DSL plugin implementation skills for Edgion — builtin development, path/uri variable reference, redis/http builtin guides. Use when adding or modifying a `req.*`, `http.*`, or `redis.*` builtin, or wiring DslRuntime fields for a new namespace.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Conventions shared by the in-repo binaries (edgion-controller, edgion-gateway, edgion-cli) — project overview, command line / directory / config-path conventions, Core layering conventions, resource system.
KubernetesCenter implementation — K8s Reflector watching, leader election, HA mode, ResourceController lifecycle, status writeback.
ConfigCenter subsystem — ConfCenter trait abstraction, FileSystemCenter and KubernetesCenter implementations, unified Workqueue + ResourceProcessor pipeline.
edgion-controller control plane architecture — overall design, startup/shutdown, Admin API, ConfigCenter, Workqueue, ResourceProcessor, Requeue, CacheServer, ACME service.
Route matching overview — multi-stage pipeline (Listener→Domain→Path→DeepMatch), per-listener isolation, registration flow, atomic swap.
TLS subsystem overview — TLS Store, SNI matching, certificate management, BoringSSL/OpenSSL backend selection.
| name | dsl-coding |
| description | DSL plugin implementation skills for Edgion — builtin development, path/uri variable reference, redis/http builtin guides. Use when adding or modifying a `req.*`, `http.*`, or `redis.*` builtin, or wiring DslRuntime fields for a new namespace. |
Implementation-level guides for the EdgionDSL plugin: how to use the existing builtins from script-author and gateway-developer viewpoints, and how to add a new function inside an existing namespace. Engine-internal architecture (VM, bytecode, panic isolation, DslRuntime lifecycle) lives in
../../01-architecture/02-gateway/dsl-engine.md; user-facing syntax and the full function catalogue live underdocs/en/user-guide/http-route/filters/edgion-plugins/dsl/.
| File | Topic |
|---|---|
| builtins-path.md | req.path / req.uri / req.query and related path/uri/query variables: views, behavior, rewrite interaction, allocation cost |
| builtin-error-semantics.md | Error-handling contract for DSL builtins — which functions return nil / "" / false silently vs raise RuntimeError::ApiError; lock-in tests and "adding a new builtin" decision flow |
| http-call.md | http.call() builtin: async outbound HTTP, Value::Map return shape, SSRF guard, config fields, test patterns |
| redis-builtin.md | redis.* builtins: async LinkSys Redis interaction, named alias lookup, Map { ok, value, error } return shape, "Adding new redis.* functions" 5-step recipe |
../../01-architecture/02-gateway/dsl-engine.md: data flow, source layout, async/sync bridging, panic isolation../../01-architecture/02-gateway/dsl-engine-security-model.md: where each VmLimits cap is enforced, ReDoS posture, SSRF guard rationale — read before adding a new builtin that produces strings/lists/maps or calls out to external services../../01-architecture/02-gateway/05-plugin-system.md: where DslPlugin sits among other gateway pluginsbuiltins-path.md) → ../../01-architecture/02-gateway/uri-normalization/SKILL.md../../04-review/dsl-value-str/sso-migration-not-worth-it.md: why Value::Str(Arc<str>) stays, why Value::Map is Boxeddocs/en/user-guide/http-route/filters/edgion-plugins/dsl/api-reference.mdbuiltins-path.mdhttp-call.mdredis.* function (or wiring a new redis.* op end-to-end) → redis-builtin.mddsl-engine.md first