一键导入
env-contract
Rules for environment-driven configuration — template-backed, typed, documented, never hard-coded.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Rules for environment-driven configuration — template-backed, typed, documented, never hard-coded.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads.
Bound repository context reads and semantic-search output without weakening source, test, or evidence verification.
Choose staged contract tests that catch partial AI-generated fixes across models, data, risk, execution ownership, and CLI/Windows parity.
Keep concise user docs and machine-readable model evidence synchronized with real behavior without losing provenance or caveats.
Apply four anti-error coding principles plus this repository's stricter financial-evidence, safety, and single-session rules.
Research the existing implementation, tests, primary technical sources, and financial rationale before adding trading code or dependencies.
| name | env-contract |
| description | Rules for environment-driven configuration — template-backed, typed, documented, never hard-coded. |
| origin | adapted from ZMB-UZH/omero-docker-extended env-contract-reviewer |
Use this skill whenever you add, rename, or remove an environment variable, or change how config is loaded.
.env.example at the repo root. That file is the canonical tracked contract..strip()) before use. An empty string means "unset"..env, deploy.env, etc.) are never created, edited, or read by the repo's tooling. They are developer-local, and git ignores them.ARG and .env.example and docker-compose.yml. Pick one source of truth (usually .env.example).eval, source, or shell-interpolate an env file. Parse it as data..env.example with a one-line comment describing purpose and default.os.getenv("NAME", "").strip()), with an explicit default in the caller.| Name | Purpose | Trust boundary |
|---|---|---|
BINANCE_BASE_URL | Override both spot and futures base hosts (proxy/testing). | Trusted for the current session only. |
BINANCE_SPOT_BASE_URL | Override spot base host. | Trusted for the current session only. |
BINANCE_FUTURES_BASE_URL | Override futures base host. | Trusted for the current session only. |
Adding a new entry to this table is part of the change, not a follow-up.
runtime.json) is user-owned; env overrides are session-scoped.