菜单
Use when the user wants to build and install Pinta from scratch — installs npm dependencies, builds the Chrome extension and the companion server, installs the Claude Code skill into ~/.claude/skills/pinta/, and prints the steps to load the unpacked extension in Chrome. One-shot setup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Cut a new Pinta release end-to-end. Bumps versions, updates CHANGELOG, builds + zips the extension, commits, tags, pushes, publishes pinta-companion to npm, and creates a GitHub release with the zip attached. Chrome Web Store upload is the only manual step left (Google doesn't expose a key-free publish API).
Use when the user wants to visually annotate their running app to make UI changes. Picks up annotation sessions submitted from the Pinta Chrome extension and edits the matching component files in the user's project. Accepts an optional `--push` (default) or `--polling` argument controlling how the agent waits for sessions.
Use when the user wants to visually annotate their running app to make UI changes. Picks up annotation sessions submitted from the Pinta Chrome extension and edits the matching component files in the user's project. Accepts an optional `--push` (default) or `--polling` argument controlling how the agent waits for sessions.
Use when the user wants a security + performance audit of the Pinta Chrome extension. Walks the manifest, content scripts, service worker, message passing, WebSocket / HTTP layer, IndexedDB store, composite + screenshot pipeline, and Svelte 5 runes usage; produces a prioritized findings list with file:line refs and concrete fixes.
Use when the user wants a single-shot release-readiness check before shipping Pinta. Runs `/test`, `/audit`, and `/spec` in sequence and produces one consolidated verdict — green-light to publish, fix-the-criticals-and-ship, or hold. Recommended before any `npm publish`, `git tag`, or Chrome Web Store push.
Use when the user wants to find gaps between Pinta's design spec and the actual codebase before a release. Walks every section of `spec/SPEC.md`, verifies each requirement against the current `extension/`, `companion/`, and `skill/` source, and produces a prioritized punch list of: (a) spec items not implemented, (b) spec sections out of date with shipped code, (c) phases marked Shipped that aren't actually complete, (d) wire-protocol drift between extension and companion, (e) docs (README/CHANGELOG) out of sync. Recommended before cutting any version tag.
| name | build-pinta |
| description | Use when the user wants to build and install Pinta from scratch — installs npm dependencies, builds the Chrome extension and the companion server, installs the Claude Code skill into ~/.claude/skills/pinta/, and prints the steps to load the unpacked extension in Chrome. One-shot setup. |
Run the full local build + install for Pinta. End state: an extension dist
ready to load into Chrome, a built companion, and a working /pinta skill.
test -f package.json && grep -q '"name": "pinta"' package.json && echo "OK in pinta repo" || { echo "ERROR: run this from the pinta repo root"; exit 1; }
If that fails, ask the user to cd into their pinta clone and re-invoke.
npm install
(safe to re-run; idempotent.)
npm run build --workspace @pinta/extension &
npm run build --workspace @pinta/companion &
wait
Both should print built in <X>s with no errors. If either fails, surface
the failure and stop.
bash scripts/install-skill.sh
Writes ~/.claude/skills/pinta/SKILL.md and a start-companion.js that
points back to the absolute path of this repo. Re-running overwrites both.
Tell the user, with the resolved absolute path:
✅ Pinta is built and the /pinta skill is installed.
Next:
1. Open Chrome → chrome://extensions
2. Enable "Developer mode" (top right)
3. Click "Load unpacked" → pick:
<REPO_ROOT>/extension/dist
4. Pin the Pinta icon to your toolbar.
To use it on a project:
- In another terminal, in your project root:
node ~/.claude/skills/pinta/start-companion.js .
- Open your app in Chrome, click the Pinta icon → Open side panel.
- Annotate (S = select, D = draw), hit "Send to agent".
- In Claude Code (in the project root), run /pinta.
Resolve <REPO_ROOT> with pwd when you print, so the user can copy-paste
the path directly.
/build-pinta after pulling new commits. It's
idempotent.rm -rf ~/.claude/skills/pinta removes the skill;
uninstall the extension from chrome://extensions.