The named artifact for this chapter is a plugin directory, not a Node.js script. It runs inside the Figma editor.

The plugin gives you the write path. The audit gives you the findings. What you do not yet have is a way to run this loop continuously , not as a one-time remediation effort, but as an ongoing check that fires whenever the file changes. Chapter 7 covers webhooks and event-driven automation: how Figma notifies external systems when a file is updated, and how to use those notifications to trigger the audit pipeline automatically so that the 247 errors never accumulate in the first place.