> vscode-port-monitor-config
This skill should be used when configuring VS Code Port Monitor extension for development server monitoring. Use when the user asks to "set up port monitoring for Vite", "monitor my dev server ports", "configure port monitor for Next.js", "track which ports are running", "set up multi-port monitoring", "monitor frontend and backend ports", or "check port status in VS Code". Provides ready-to-use configuration templates for Vite (5173), Next.js (3000), and microservices architectures with trouble
curl "https://skillshub.wtf/libukai/awesome-agent-skills/vscode-port-monitor-config?format=md"VS Code Port Monitor Configuration
Configure the VS Code Port Monitor extension to monitor development server ports in real-time with visual status indicators in your status bar.
Extension: dkurokawa.vscode-port-monitor
Core Concepts
Port Monitor Features
- ๐ Real-time monitoring - Live status bar display
- ๐ท๏ธ Intelligent configuration - Supports arrays, ranges, well-known ports
- ๐ Process management - Kill processes using ports
- ๐จ Customizable display - Icons, colors, positioning
- ๐ Multiple groups - Organize ports by service/project
Status Icons
- ๐ข = Port is in use (service running)
- โช๏ธ = Port is free (service stopped)
Configuration Workflow
Step 1: Create Configuration File
Add configuration to .vscode/settings.json:
{
"portMonitor.hosts": {
"GroupName": {
"port": "label",
"__CONFIG": { ... }
}
}
}
Step 2: Choose a Template
Select from common scenarios (see examples/ directory):
| Scenario | Template File | Ports |
|---|---|---|
| Vite basic | vite-basic.json | 5173 (dev) |
| Vite with preview | vite-with-preview.json | 5173 (dev), 4173 (preview) |
| Full stack | fullstack.json | 5173, 4173, 3200 |
| Next.js | nextjs.json | 3000 (app), 3001 (api) |
| Microservices | microservices.json | Multiple groups |
Step 3: Apply Configuration
- Copy template content to
.vscode/settings.json - Customize port numbers and labels for your project
- Save file - Port Monitor will auto-reload
Quick Start Examples
Example 1: Vite Project
{
"portMonitor.hosts": {
"Development": {
"5173": "dev",
"__CONFIG": {
"compact": true,
"bgcolor": "blue",
"show_title": true
}
}
},
"portMonitor.statusIcons": {
"inUse": "๐ข ",
"free": "โช๏ธ "
}
}
Display: Development: [๐ข dev:5173]
Example 2: Microservices
{
"portMonitor.hosts": {
"Frontend": {
"3000": "react",
"__CONFIG": { "compact": true, "bgcolor": "blue", "show_title": true }
},
"Backend": {
"3001": "api",
"5432": "postgres",
"__CONFIG": { "compact": true, "bgcolor": "yellow", "show_title": true }
}
}
}
Display: Frontend: [๐ข react:3000] Backend: [๐ข api:3001 | ๐ข postgres:5432]
Best Practices
โ Do
- Use descriptive labels:
"5173": "dev"not"5173": "5173" - Add space after emojis:
"๐ข "for better readability - Group related ports: Frontend, Backend, Database
- Use compact mode for cleaner status bar
- Set reasonable refresh interval (3000-5000ms)
โ Don't
- Reverse port-label format:
"dev": 5173โ - Use empty group names
- Set refresh interval too low (<1000ms)
- Monitor too many ports (>10 per group)
Common Issues
Port Monitor Not Showing
- Check extension is installed:
code --list-extensions | grep port-monitor - Verify
.vscode/settings.jsonsyntax - Reload VS Code:
Cmd+Shift+Pโ "Reload Window"
Configuration Errors
Check port-label format is correct:
// โ
Correct
{"5173": "dev"}
// โ Wrong
{"dev": 5173}
For more troubleshooting, see references/troubleshooting.md
Reference Materials
- Configuration Options:
references/configuration-options.md- Detailed option reference - Troubleshooting:
references/troubleshooting.md- Common issues and solutions - Integrations:
references/integrations.md- Tool-specific configurations - Advanced Config:
references/advanced-config.md- Pattern matching, custom emojis - Examples:
examples/- Ready-to-use JSON configurations
Workflow Summary
- Choose template from examples/ directory based on your stack
- Copy to
.vscode/settings.json - Customize port numbers and labels
- Save and verify status bar display
- Troubleshoot if needed using references/troubleshooting.md
Port Monitor will automatically detect running services and update the status bar in real-time.
> related_skills --same-repo
> obsidian-to-x
ๅๅธๅ ๅฎนๅๆ็ซ ๅฐ X (Twitter)ใๆฏๆๅธธ่งๆจๆ(ๆๅญ/ๅพ็/่ง้ข)ๅ X Articles(้ฟๆ Markdown)ใไฝฟ็จ็ๅฎ Chrome ๆต่งๅจ็ป่ฟๅๆบๅจไบบๆฃๆตใๅฝ็จๆท่ฏด"ๅๆจ"ใ"ๅๅฐ X"ใ"ๅๅฐ twitter"ใ"ๅไบซๅฐ X"ใ"ๅไบซๅฐ twitter"ใ"ๅ tweet"ใ"ๅๆญฅๅฐ X"ใ"ๅๅธๅฐ X"ใๆๅฐ"X Articles"ใๆณไป Obsidian ็ฌ่ฎฐๅๅธ้ฟๆๅ ๅฎนใๆ้่ฆ่ฝฌๆข Obsidian Markdown ๅฐ X ๆ ผๅผๆถไฝฟ็จใ้็จไบๆๆ X/Twitter ๅๅธไปปๅกใ
> vscode-sftp-config
This skill should be used when setting up SFTP deployment for static websites to production servers, including converting projects from Docker/Express to static hosting, deploying Vue/React/Angular builds, setting up Slidev presentations, or configuring Hugo/Jekyll/Gatsby sites. Use this when the user asks to "setup SFTP deployment", "deploy static site to server", "configure Nginx for static files", "convert from Docker to static hosting", "deploy Vue build to production", "setup subdomain host
> vscode-httpyac-config
Configure VSCode with httpYac for API testing and automation. This skill should be used specifically when converting API documentation to executable .http files (10+ endpoints), setting up authentication flows with pre-request scripts, implementing request chaining with response data, organizing multi-file collections with environment management, or establishing Git-based API testing workflows with CI/CD integration.
> mcp-config
Configure MCP (Model Context Protocol) servers for Claude Code. Manage MCP servers at user or project scope with best practices to avoid context pollution.