Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

env-contract

Estrellas1

Forks0

Actualizado24 de abril de 2026 a las 14:49

Rules for environment-driven configuration — template-backed, typed, documented, never hard-coded.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

strmt7

strmt7/simple_ai_trading

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

Más de este repositorio

mismo repositorio

cocoindex-code-search

strmt7/simple_ai_trading

Use the pinned external CocoIndex Code MCP workflow for broad repository routing, then prove exact candidates with rg and direct file reads.

2026-07-151

context-budget

strmt7/simple_ai_trading

Bound repository context reads and semantic-search output without weakening source, test, or evidence verification.

2026-07-151

ai-regression-testing

strmt7/simple_ai_trading

Choose staged contract tests that catch partial AI-generated fixes across models, data, risk, execution ownership, and CLI/Windows parity.

2026-07-111

docs-knowledge-maintainer

strmt7/simple_ai_trading

Keep concise user docs and machine-readable model evidence synchronized with real behavior without losing provenance or caveats.

2026-07-111

karpathy-guidelines

strmt7/simple_ai_trading

Apply four anti-error coding principles plus this repository's stricter financial-evidence, safety, and single-session rules.

2026-07-111

search-first

strmt7/simple_ai_trading

Research the existing implementation, tests, primary technical sources, and financial rationale before adding trading code or dependencies.

2026-07-111

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

Env Contract

Use this skill whenever you add, rename, or remove an environment variable, or change how config is loaded.

Rules

All environment variables read by the trading CLI are listed in .env.example at the repo root. That file is the canonical tracked contract.
Variables are trimmed (.strip()) before use. An empty string means "unset".
Non-example env files (.env, deploy.env, etc.) are never created, edited, or read by the repo's tooling. They are developer-local, and git ignores them.
Never duplicate a default in both Dockerfile ARG and .env.example and docker-compose.yml. Pick one source of truth (usually .env.example).
Never eval, source, or shell-interpolate an env file. Parse it as data.

Required change pattern

Add the variable to .env.example with a one-line comment describing purpose and default.
Load it via the existing helper (e.g. os.getenv("NAME", "").strip()), with an explicit default in the caller.
Update the README "Host overrides" or "Environment" section with the new variable.
If the variable affects behavior, add a test that sets it and asserts the observable effect.

Currently tracked variables

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.

Don't

Don't read secrets from env at import time. Lazy-read inside the function that needs them, so tests can patch cleanly.
Don't let an env override silently promote to the persisted config. Persisted config (runtime.json) is user-owned; env overrides are session-scoped.