메뉴
Scan running terminals for dev server URLs (localhost ports), report them, and optionally open the app in Cursor's built-in browser.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate or edit images using the OpenAI Image API (gpt-image-2). Use when the user asks to generate, create, draw, render, illustrate, mock up, or edit an image, icon, logo, mockup, illustration, OG image, blog hero, marketing asset, or similar visual. Also use when the user supplies a reference image and asks to modify, restyle, or remix it. Triggers on: "generate an image", "create an image", "make a picture of", "edit this image", "restyle this", "make a mockup of", "draw a", "render a", "illustration of".
When the same multi-step workflow repeats in Cursor (user corrections or agent redos), capture it as a new SKILL.md under .cursor/skills/ so future sessions load it automatically.
After navigating and interacting in Cursor's built-in browser, use browser_network_requests to audit every fetch/XHR for failures, slowness, duplicate calls, and suspicious payloads. Use for API-heavy pages and after backend or client networking changes.
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel. Use for multi-job CI failures where jobs are independent.
Run four parallel read-only subagents that each review the same diff from a different lens — security, performance, correctness, and readability — then merge findings into one report. Use before merging large or risky PRs.
Execute a user flow step-by-step in Cursor's built-in browser while documenting each action, then emit a Playwright test that replays the same flow using stable selectors derived from the accessibility tree.
| name | finding-dev-server-url |
| description | Scan running terminals for dev server URLs (localhost ports), report them, and optionally open the app in Cursor's built-in browser. |
| user-invocable | true |
Detect which dev servers are running, what ports they're on, and open them.
Cursor stores live terminal output in text files. Each terminal has a file at:
<terminals_folder>/<id>.txt
The terminals folder path is provided in your system context. Each file contains metadata (pid, cwd, last command) followed by the full terminal output.
ls <terminals_folder>/*.txt
Read the first ~10 lines of each terminal file to see:
pid — process IDcwd — working directorylast_command — what's running (e.g. npm run dev, pnpm dev, python manage.py runserver)Skip terminals where the last command is clearly not a server (e.g. git status, ls, cd).
Read the full content of terminals that look like they're running a server. Search for these patterns:
| Framework | Pattern |
|---|---|
| Next.js | Local: http://localhost:XXXX or ▲ Ready |
| Vite | Local: http://localhost:XXXX/ |
| Create React App | Local: http://localhost:XXXX |
| Express | listening on port XXXX or listening at http://... |
| Django | Starting development server at http://127.0.0.1:XXXX/ |
| Rails | Listening on http://127.0.0.1:XXXX |
| Flask | Running on http://127.0.0.1:XXXX |
| Go | Listening on :XXXX or http server started on :XXXX |
| PHP | Development Server (http://localhost:XXXX) started |
| Remix | http://localhost:XXXX |
| Astro | http://localhost:XXXX |
| Nuxt | http://localhost:XXXX |
Regex to match most server output:
https?://(localhost|127\.0\.0\.1|0\.0\.0\.0)(:\d+)
Also check for standalone port patterns:
(listening|started|running|ready|serving).*(port\s*|:)\s*(\d{4,5})
Print a summary:
Dev servers found:
Terminal 1 (pid 12345) — npm run dev → http://localhost:3000 (cwd: /Users/me/app)
Terminal 3 (pid 67890) — python manage.py runserver → http://127.0.0.1:8000 (cwd: /Users/me/api)
If no servers are found, say so and suggest starting one.
If the user wants to view the app, use Cursor's built-in browser:
browser_navigate → http://localhost:<port>
Then take a screenshot to confirm it's rendering:
browser_take_screenshot
EADDRINUSE, address already in use), report the conflictexit_code in the terminal file footer