install-windows
Set up a Windows PC to run the project. Sets PowerShell execution policy, installs Node.js if needed, and runs npm install.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Set up a Windows PC to run the project. Sets PowerShell execution policy, installs Node.js if needed, and runs npm install.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Set up a Mac to run the project. Installs Node.js if needed and runs npm install.
Begin the guided building experience. Helps the user brainstorm an idea and start building their first app.
Run health checks and fix problems. Checks if the dev server is running, runs lint and build checks, verifies file integrity, and automatically fixes any issues found.
Context-aware help for when someone is stuck, confused, or needs guidance. Reads the conversation and project state to give specific, relevant help.
Deploy the app to the internet and get a shareable link. Triggers on "$deploy", "deploy my app", "push this live", "put it on the internet", or any deployment request. Handles build verification, deployment to Vercel, and guides the user through sharing their creation.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
| name | install-windows |
| description | Set up a Windows PC to run the project. Sets PowerShell execution policy, installs Node.js if needed, and runs npm install. |
do not narrate technical steps. the user doesn't need to know what you're checking or installing behind the scenes. keep all checks, downloads, and installs silent unless you need the user to do something.
only talk to the user at these moments:
$start to begin building"never mention node_modules, node -v, version numbers, npm, winget, PowerShell, PATH, or any technical terms in messages to the user.
silently run this as the very first step — don't mention it to the user:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
silently check if node_modules/ exists in the project root. if it does, tell the user:
you're already set up! type
$startto begin building.
stop here. don't continue.
tell the user:
setting things up — give me a sec.
silently run node -v to check if Node.js is installed.
run winget to install Node.js. this command needs to run outside the sandbox — Codex will prompt the user to approve it, which is fine:
winget install --id OpenJS.NodeJS.LTS --accept-package-agreements --accept-source-agreements
tell the user:
installing something we need — you might see a prompt asking to allow changes, click Yes.
after it finishes, silently refresh the PATH:
$env:PATH = [System.Environment]::GetEnvironmentVariable("PATH", "Machine") + ";" + [System.Environment]::GetEnvironmentVariable("PATH", "User")
silently verify node is available:
node -v
if node is still not found, tell the user:
hmm, let's try a quick fix — close Codex completely and reopen it, then type
$install-windowsagain.
stop here if node isn't found. don't continue.
silently run:
npm install
this takes a minute or two. don't say anything unless it fails.
tell the user:
you're all set! type
$startto begin building.