메뉴
Use when adding or updating Python dependencies, writing standalone Python scripts, documenting local setup, or choosing Python execution commands in the J-stock repository where uv is the preferred workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when: generating worker-ready JSON manifests for J-stock evaluation, pos-evaluation, walk-forward-evaluate, or replay-evaluation batch execution. Resolve WebUI-equivalent defaults, split jobs by worker during generation, and stop before execution.
Use when: orchestrating an end-to-end J-stock batch evaluation workflow, or when the user explicitly names evaluation-batch-runner. Schedule evaluation-batch-generator, evaluation-batch-executor, and evaluation-result-summary in order, preserving the manifest approval boundary and allowing subagent delegation only during approved execution.
Use when: aggregating completed J-stock evaluation output directories into markdown summary reports under G:/My Drive/AI-Stock-Sync/summary without rerunning backtests, including global MDD-Win re-scoring via tools/score_evaluation_outputs.py when worker-local PRS is not comparable.
Use when generating training-window entry-signal-analysis datasets for a J-stock stock-pool experiment, especially scanning a broad/full universe with a fixed entry strategy before ticker-level pool selection.
Use when orchestrating a J-stock custom stock-pool experiment where a fixed entry condition is applied to a broad/full universe during a training window, good tickers are selected into one or more test universes, and those universes are evaluated out-of-sample against current and full-pool controls.
Use when generating approval-ready J-stock out-of-sample evaluation commands or batch manifests that compare trained selected stock pools against current production and broad/full universe controls.
| name | modern-uv-workflow |
| description | Use when adding or updating Python dependencies, writing standalone Python scripts, documenting local setup, or choosing Python execution commands in the J-stock repository where uv is the preferred workflow. |
Use uv as the default Python workflow for this repository while respecting existing project files and commands.
pyproject.toml, scripts, docs, or CI already define a command, follow that shape.uv run ... for local Python execution when no more specific project command exists.uv sync to recreate the project environment.uv add <package> and uv remove <package> for dependency changes when the user asks to change project dependencies.pip, python, or CI commands unless the task is specifically to modernize setup.pip, python -m, or another installer, explain the reason and keep the command scoped.