penpot-router

To automate Penpot design tasks, you can use a dispatcher skill to read your intent and route requests to designated workflows for building screens, managing tokens, or auditing accessibility. It identifies the best route and hands off control to the relevant skill.

The best way to route a Figma to Penpot migration is through an intent dispatcher that maps your request to a predefined migration workflow. It reads your migration intent and coordinates with the appropriate Penpot skill to execute the transfer.

Yes, you can use this dispatcher to manage design systems in Penpot without modifying the canvas directly. It acts as a router that ensures the right workflows are initiated based on user intent, handing off control instead of applying changes itself.

Yes, MCP initialization is required to coordinate Penpot workflows. The dispatcher relies on MCP and read-only discovery calls to ground its routing decisions in the current file state before mapping your intent to the correct skill.

Intent detection for Penpot dashboard creation works by reading your natural language task description and matching it against a predefined mapping. The dispatcher then routes the request to the specific workflow responsible for building that screen.

Penpot workflow routing fails to identify the correct skill if MCP is not initialized or if read-only discovery calls cannot ground the routing decisions in the current file state, preventing the dispatcher from accurately mapping user intent to workflows.