Strengthen lab AGENTS env-development guardrails#876
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| - Document required environment variables in README and validate missing keys early with `vf.ensure_keys(...)`. | ||
| - NEVER initialize environment source code manually; ALWAYS create new environments with `prime env init`. | ||
| - Use the Prime CLI for all environment lifecycle operations (`prime env init` → `prime env install` → `prime eval run` → `prime env push`) rather than ad-hoc scripts. | ||
| - NEVER begin environment development before `prime lab setup` has been run; if work starts outside that structure, recommend adjusting course into a proper lab workspace before continuing. |
There was a problem hiding this comment.
Missing skill update for new lab setup prerequisite
Low Severity
The PR introduces a new requirement that prime lab setup must be run before beginning environment development, but skills/create-environments/SKILL.md does not reflect this prerequisite. The skill file starts with prime env init my-env as the first step without mentioning the lab setup requirement. This creates an inconsistency between the agent guidance files and the create-environments skill, potentially causing agents to skip the now-mandatory workspace setup. Per the Skills Updates rule: "If workflow-relevant changes are detected without matching skill updates, request that the author update the impacted skills before merge."


Motivation
prime lab setupbefore starting env work and by encouraging a dedicatedenvironments/<env_name>/layout.Description
assets/agents/end_user_best_practices.mdto add strict instructions: never initialize env source manually, always useprime env init, prefer the Prime CLI for lifecycle operations, requireprime lab setupbefore env development, and keep environments self-contained underenvironments/<env_name>/.scripts/sync.py, which updatedassets/lab/AGENTS.mdto reflect the source changes.Testing
uv run pre-commit installwhich completed successfully.uv run python scripts/sync.pyto regenerate compiled AGENTS files which completed and updatedassets/lab/AGENTS.md.uv run pre-commit run --all-files(includesruffchecks and the sync validation) and it passed.Codex Task
Note
Low Risk
Documentation-only updates that tighten recommended workflows for lab environment development; no runtime or API behavior changes.
Overview
Strengthens lab end-user guidance to explicitly enforce the Prime CLI as the canonical environment workflow: never manually initialize env source, require
prime lab setupbefore env work, and standardize on a self-containedenvironments/<env_name>/layout with documented best-practice patterns.Regenerates the compiled lab
assets/lab/AGENTS.mdso it reflects the updated source guidance inassets/agents/end_user_best_practices.md.Written by Cursor Bugbot for commit 093d114. This will update automatically on new commits. Configure here.