メニュー
Detect existing project environment and determine appropriate tools. Use when setting up a dev environment, installing dependencies, or running commands in any layer (Python, Node, Docker, etc.).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | environments |
| description | Detect existing project environment and determine appropriate tools. Use when setting up a dev environment, installing dependencies, or running commands in any layer (Python, Node, Docker, etc.). |
This skill detects what tools and runtimes a project uses, then routes to the appropriate spec file for working with those tools.
Before applying any setup, inspect the project to determine what's already in use:
| Signal | Inferred tool |
|---|---|
venv/, .python-version, requirements.txt | Python + uv virtualenv |
pyproject.toml + poetry.lock | Python + Poetry |
pyproject.toml + uv.lock | Python + uv (pyproject-based) |
package.json + package-lock.json | Node + npm |
package.json + yarn.lock | Node + Yarn |
package.json + pnpm-lock.yaml | Node + pnpm |
volta key in package.json | Node version managed by Volta |
.nvmrc or .node-version | Node version pinned |
docker-compose.yml or compose.yaml | Docker services defined |
Dockerfile present | App may be fully containerized |
Rule: Always detect before scaffolding. Treat existing artifacts as the source of truth.
These are the available spec files. Read only the ones relevant to the current stack:
| Environment | Spec file | When to read |
|---|---|---|
| Python (uv + virtualenv) | python-uv.md | Python backend — installing packages, running commands, scaffolding |
| Node (npm) | node-npm.md | Node/Vue frontend — installing packages, running scripts |
| Docker | docker.md | Service dependencies or full app containerization |
If the project uses a Python or Node tool not covered by a spec file (e.g. Poetry, Yarn, Volta), use the detected tool's own conventions and do not force the defaults from the spec files.
Each layer of the stack is always an independent environment — never mix Python package management with Node or vice versa. Each layer has its own .env file. See individual spec files for details.
create tasks as files in local project directory
orchestration skill for tasks, takes a task folder as input and runs one sub-agent for each individual task file. Should NOT execute or make any changes on its own, only sub-agents may do that.
coding best-practices and architecture skill
Plan and structure a new application from a vague prompt or PRD. Use when starting a greenfield project, building an app from scratch, or when the user provides a project idea or PRD that needs to be broken down into a structured development plan.
Break down a greenfield project blueprint into executable task-creator-ready research documents. Use after greenfield-init has produced a project blueprint, or when a project plan needs to be decomposed into buildable chunks with validation gates.
One-shot greenfield build orchestration. Takes a project blueprint and executes the full build pipeline using subagents for each phase, including intermediate verification gates. Use when you want to run an entire greenfield project build in one session without manual intervention between phases.
