kombai-io/agent-plugins

work-with-kombai

Design UI with Kombai's taste agent.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/kombai-io/agent-plugins --skill work-with-kombai

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

When running in Codex's sandbox, first read codex-access.md beside this file and do what it says before the first command below: it says how to get network access without trying the restricted command first. Elsewhere, skip it.

Run Kombai's CLI (kombai below) from node "$HOME/.kombai/cli/install/latest/launch.mjs" if that file exists; if not, fall back to npx -y @kombai/cli@0.2.0.

Run kombai skill and follow what it prints; it is this skill's full text.

If that command fails before it prints anything:

  • `npx` or `node` not found. Kombai needs Node.js 20 or later. Tell the user, give them the steps for their OS, and wait; do not install Node yourself.
  • macOS: brew install node if Homebrew is installed, otherwise the LTS installer from https://nodejs.org.
  • Windows: winget install OpenJS.NodeJS.LTS, otherwise the LTS .msi from https://nodejs.org.
  • Linux: nvm (https://github.com/nvm-sh/nvm), then nvm install --lts. The distro's package is often older than 20.

When they say it is installed, run the command again. If node is still not found, ask them to restart this agent or its editor, so it picks up the new PATH; do not ask them to install again.

  • `CLI_NODE_TOO_OLD`. The same steps upgrade Node; with nvm, nvm install --lts then nvm alias default lts/*. If the error comes back after an upgrade, an older node is first on PATH: show the user which -a node (where node on Windows).
  • Windows PowerShell says running scripts is disabled. Run npx.cmd in place of npx.
  • The network is blocked (a sandboxed shell). Ask for network access the way your client does; Node is not missing.