菜单
Run and talk to the template app from the terminal — serve the api/mcp/auth/dashboard surfaces, call any API endpoint through the generated SDK, and manage login. Use when asked to start a local server, hit an endpoint, or check the current user.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/andre-brandao/template --skill template-cli命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Scaffold a feature prototype under docs/prototype/<feature> — a PROTOTYPE.md (UX, features, high-level data model) with self-contained .html mockups, plus an optional PLAN.md technical companion written in a later step. Use when the user wants to prototype, spec, or mock up a feature before implementing it.
Build the frontend vertical of a feature inside the real app (routes, pages, components, remote functions) backed by an in-memory mock namespace — without touching packages/core or any backend package. Use after a /prototype is validated, when the user wants the feature clickable in the actual app before core exists.
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
基于 SOC 职业分类
正在显示 SKILL.md
| name | template-cli |
| description | Run and talk to the template app from the terminal — serve the api/mcp/auth/dashboard surfaces, call any API endpoint through the generated SDK, and manage login. Use when asked to start a local server, hit an endpoint, or check the current user. |
bun run cli <command> from the repo root, or template-cli <command> once the bin is
linked.
template-cli serve api # Hono API on API_PORT (default 3000)
template-cli serve mcp # MCP server on MCP_PORT (default 3001), at /mcp
template-cli serve auth # OpenAuth issuer on PORT (default 3002)
template-cli serve dashboard # SvelteKit prod build on PORT (auto-builds if missing)
All except dashboard need a reachable DATABASE_URL. For a local DB run bun dev
first.
The method list is reflected off the generated @template/sdk, so it always matches the
current endpoints. Discover before guessing:
template-cli api # list callable methods
template-cli api getTodo # GET /todo
template-cli api postTodo --title "Ship it" # POST /todo
template-cli api postTodo '{"title":"Ship"}' # same, as a JSON blob
template-cli api getTodoById --id tod_123
Flags become call params (--key value, --key=value, or bare --flag for true).
Values coerce to number/boolean when they look like one. --token and --url are
consumed by the client and never sent as params.
Results print as JSON on stdout; errors print as JSON on stderr and exit non-zero — so
pipe into jq and check the exit code.
template-cli login # opens the browser, PKCE, saves tokens
template-cli whoami # current user
template-cli logout
login writes ~/.config/template/config.json (respects XDG_CONFIG_HOME) and opens a
loopback server on port 3006 for the callback; it times out after 2 minutes. It needs a
browser — in a headless session, set TEMPLATE_TOKEN to an sk- API key instead.
Token: --token › TEMPLATE_TOKEN › saved key › saved OAuth access (auto-refreshed).
Base URL: --url › API_URL › saved config › http://localhost:3000.
Issuer: --issuer › AUTH_URL › saved config › http://localhost:3002.