Implement to Pixel — Orchestrator

This is the entry point for the Mekari PRD/Figma → Vue/Nuxt code pipeline. It detects what the user attached and routes to the right workflow.

When this triggers

Any of the following:

• User attaches a Confluence PRD link (*.atlassian.net/wiki/...)
• User attaches a Figma URL (figma.com/design/... or figma.com/file/...)
• User invokes /implement-to-pixel with or without an attachment
• User says things like "build this for [Mekari product]", "implement this screen", "code this design" along with an attachment

If the user attaches a URL without specifying intent, assume code generation is the goal — Mekari teams default to this flow.

Token mode

Default to Pixel 2.4 in all cases. Switch only if the user or the source explicitly mentions Pixel 2.1, Enterprise tokens, or a known legacy project.