kevzlou7979
UserPinta — annotate your running app and hand the changes to a coding agent. Pinta lets developers annotate their running web app and have an AI coding agent apply the changes to source files.
Categories
Indexed Skills (5)
audit
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.
build-pinta
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.
release
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).
staging
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.
pinta
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.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.