pynecore-idelisted
Install: claude install-skill theonetrade/pynecore-skills
# PyneIDE project workflow
PyneIDE initializes a project with a workdir, a managed Python environment and editor
settings, and runs Pyne scripts on a chart with a bar-by-bar debugger. An agent usually has no
UI tools, so this skill tells you how to reach the IDE's environment from a shell, which
commands to name when the user works in the editor, what the IDE writes into the project, and
how to report evidence honestly. Nothing outside the project folder is consulted.
## 1. The project structure PyneIDE requires
PyneIDE works on a PyneCore workdir and expects this layout (the project folder itself when it
holds the `.pyne` marker, otherwise a `workdir/` child):
```
.pyne # marker: workdir_version = "1.0"
scripts/ scripts/lib/
data/ # <name>.ohlcv + <name>.toml pairs
config/ # .gitignore (*), api.toml, plugins/<plugin>.toml, symbol_map.toml
output/ output/logs/
cache/
```
```bash
python3 <skill>/scripts/ide_env.py # verify the structure, list scripts/data/config
python3 <skill>/scripts/ide_env.py --create # add whatever is missing, never overwrite
python3 <skill>/scripts/ide_env.py --json
```
Exit code 1 means a required folder or the marker is missing; `--create` makes the folder a
valid workdir for both the IDE and the CLI. A missing `data/<name>.toml` next to an `.ohlcv`
file or an unconverted CSV is reported too. The script reads only the project folder.
## 2. The environment and how to reach it
| Setup