Files
redsen-lean-harness/.github/instructions/context7.instructions.md
T
mozempkandCopilot 383129f571 feat: scaffold redsen-lean-harness v0.1.0
Recovered from crashed session (Node OOM). Repo contains full P0-P6
scaffold: plugin.json/marketplace.json, AGENTS.md, ADRs 0001-0006,
lh CLI (init/index/graph/lane/run/memory/host/report/doctor), 10
.github/agents, 12 CLI skills, instructions, context7 mcp.json, and
unit/e2e test suite.

Fixed: run.mjs read --in-tokens/--out-tokens but tests and CLI docs
use --input-tokens/--output-tokens, so telemetry totals were always 0.
Now accepts both forms.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-09-09 22:44:15 +02:00

970 B

applyTo, description
applyTo description
** Mandatory Context7 usage for external library, framework, SDK, API, CLI, and cloud-service work.

Context7 Rules

  1. Use Context7 before using any external library, framework, SDK, API, CLI, or cloud service.
  2. Call resolve-library-id first.
  3. Call query-docs with the resolved id second.
  4. Base implementation on the returned docs.
  5. Cite the library id or doc source in notes when it affects decisions.
  6. Read the API key only from the CONTEXT7_API_KEY environment variable.
  7. Never write the API key to any file.
  8. Never put the API key in .github/mcp.json.
  9. Never paste the API key into prompts, logs, memory, or telemetry.
  10. If CONTEXT7_API_KEY is missing, stop library work.
  11. Tell the user exactly:
export CONTEXT7_API_KEY='<your-context7-api-key>'
  1. Resume library work only after the environment variable exists.
  2. Continue non-library work when it does not depend on external docs.