Practical Notes
- Quant: start with 1 bulk text replace task and measure time saved vs manual edits.
- Quant: track failure rate for tool calls (connection, auth, plugin channel) over 10 runs.
Recommended workflow
- Keep the socket server running while you work.
- Use small, reversible actions first (read-only, then text replacement).
- Add a review step: export a before/after summary (list of nodes changed).
Safety note
Design automation can create large diffs. Prefer running changes on a copy, and only apply to the main file after review.
FAQ
Q: Do I need Cursor specifically? A: Cursor is one supported client; the README also mentions Claude Code usage patterns.
Q: What usually breaks first? A: The socket connection and plugin channel setup—start with a simple read-only call.
Q: Can I run it in teams? A: Yes, but standardize config and add a review process for large automated edits.