pynecore-strategylisted
Install: claude install-skill theonetrade/pynecore-skills
# PyneCore strategy development
PyneCore runs **Pyne code**: Python files whose docstring starts with `@pyne`, executed bar by
bar with series history, persistent state and a broker emulator. This skill is self-contained
and installed globally: it needs no per-project configuration files. Everything project-specific
(interpreter, CLI, workdir, data) is discovered at the start of a task.
## 1. Discover the environment first
Run the bundled probe (standard library only) from the project root and read its output:
```bash
python3 <skill>/scripts/pyne_env.py # add --json for machine-readable output
```
It reports the workdir (the folder with the `.pyne` marker or the `scripts/ data/ config/`
layout, or a `workdir/` child) and which of its folders exist, the scripts with their role and
`.toml`, the data files with symbol and timeframe, the configured plugins and symbol map, and
the interpreter that can import `pynecore` (the project's `.venv`/`venv`/`env` first, then
`$VIRTUAL_ENV`, then PATH) with its `pyne` command. Only the project folder is inspected.
Rules that follow from it:
- Call the CLI by its resolved path (`<venv>/bin/pyne`, or `uv run pyne` in a uv project) and
run Python tooling with the same interpreter. The agent shell does not have the venv active.
- Always set `PYNE_NO_LOGO=1` (and `NO_COLOR=1` when parsing output) on CLI calls.
- No project yet, or no PyneCore installed: `python3 <skill>/scripts/init_project.py <dir> --smoke`
builds the whol