菜单
Guides correct usage of the Portless CLI for local named URLs, monorepo workflows, HTTPS/LAN/Tailscale modes, and proxy routing pitfalls, when developers need stable local domains instead of port juggling, resulting in reproducible commands and fewer misconfiguration loops.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Long-running iterative development loops with pacing control and verifiable progress. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
Use ask_user as a decision, research, and requirements gate before ambiguous or high-stakes choices.
Versitile project planning skill for tracking ideas, defining detail and tracking progress on delivery. Use when you need to create, manage, or understand project planning artifacts like Epics, Stories, Tasks, Research, and Decisions. Follow the defined workflow phases and artifact relationships to ensure consistent and effective project planning. Results in well-structured project plans, clear traceability, and informed decision-making throughout the project lifecycle.
Use when understanding an unfamiliar code library, reusing cached local repo docs, or generating repo-native AGENTS.md and llms.txt navigation for cloned libraries.
Search local markdown knowledge bases, notes, docs, and wikis with QMD. Use when users ask to find notes, retrieve documents, inspect a wiki, answer from indexed markdown, or set up QMD access.
Working with Pi-Coding-Agent and modifying it via extensions. Use when you need to modify Pi-Coding-Agent's behavior or add new features to it. This skill routes you to the correct subskill.
| name | portless-cli |
| description | Guides correct usage of the Portless CLI for local named URLs, monorepo workflows, HTTPS/LAN/Tailscale modes, and proxy routing pitfalls, when developers need stable local domains instead of port juggling, resulting in reproducible commands and fewer misconfiguration loops. |
Portless maps local apps to stable named URLs like https://myapp.localhost. It removes manual port juggling and reduces cross-app cookie/origin clashes.
Source of truth: vercel-labs/portless GitHub README and portless --help.
Use when you need:
localhost:NNNNDo not use for public production ingress.
npm install -g portless
portless run next dev
# -> https://<project>.localhost
Explicit name:
portless myapp next dev
# -> https://myapp.localhost
portless / portless run — run package dev script through proxyportless run <cmd> — run command through proxyportless <name> <cmd> — explicit app nameportless proxy start|stopportless listportless get <name>portless trustportless hosts sync|cleanportless service install|status|uninstallportless cleanportless.json in repo root.apps map for naming overrides.portless starts all workspace packages with a dev script.Example portless.json:
{
"apps": {
"apps/web": { "name": "web" },
"apps/api": { "name": "api" }
}
}
--from/--to/--path flow. Use run, <name> <cmd>, alias, get, list.portless, not vercel-labs/portless.changeOrigin: true.portless hosts sync.run|get|alias|hosts|list|trust|clean|prune|proxy|service cannot be app names unless forced with --name.portless http ... (not a valid subcommand in this CLI).apps schema: In portless.json, app entries SHOULD be objects (e.g. { "name": "web" }), not ad-hoc undocumented shapes.server: {
proxy: {
'/api': {
target: 'https://api.myapp.localhost',
changeOrigin: true,
ws: true,
},
},
}
portless proxy start --lanportless myapp --tailscale next devportless myapp --funnel next devportless --help shows command used exists.https://<name>.localhost.portless list shows active route.portless http, --from, --to, or --path.