Previously, when I created my Make file, it had a Pages feature that allowed me to jump to the pages I wanted.
I went on vacation, and now it doesn't work anymore.
When I click on "Enable Pages," it pastes a prompt into the agent, and AI tells that the feature is already implemented, but it doesn't actually work. It also consumes a lot of tokens. 😡
And after I told it that the feature doesn't work, this was the reasoning:
Ah, I understand now! When the user clicks "Enable pages" in the Figma Make UI, it automatically sends the prompt "Let's enable pages for my project. Ask me questions to clarify my goals or suggest options, then create or update pages and enable routing as needed." to Claude. This is a built-in Figma Make feature/skill that triggers this specific prompt.
So the issue is that Figma Make's "Enable pages" feature is a specific platform feature that works differently from what I've been trying to do. The platform is reverting my __figma__entrypoint__.ts changes back to just the single Code0_8 export each time. Since Figma Make manages this entrypoint file itself and reverts custom exports, the platform must have its own specific pattern for multi-page setups rather than the manual approach I've been attempting. I should figure out what that native mechanism actually looks like instead of fighting the platform's own management of this file.
Figma Make likely manages this file automatically based on pages created in the Figma design tool itself, not through direct code edits—each Figma page probably maps to its own export, which explains why manual additions get reverted. The real workflow is likely to add pages within Figma's design interface and let the platform sync the entrypoint file accordingly.
Actually, since the user is working inside Figma Make's coding environment rather than the design tool, I'm reconsidering how "Enable pages" works—it likely triggers a built-in skill that expects Claude to create page components, set up routing, and update the entrypoint, but something's causing the entrypoint to keep reverting. Perhaps the actual intended architecture is that pages work purely through client-side routing within a single App component, with navigation happening via URL paths typed into the address bar rather than through separate entrypoint exports.
Given that the dropdown only shows "home (default page)," maybe the fix is switching from createMemoryRouter to createBrowserRouter so the preview's URL bar properly reflects route changes and supports navigation by typing paths directly—though that still wouldn't populate the pages dropdown itself, which seems to require multiple entrypoint exports that the platform is stripping out.
I'm realizing the platform likely manages __figma__entrypoint__.ts based on how many pages exist in the actual Figma file, so with only one Figma page, it only generates one entry no matter what I do. The "Enable pages" prompt probably just wants me to build the routing infrastructure so the single-page app can navigate views via the URL bar rather than actually populating a pages dropdown.
That file might actually be managed automatically by the platform, reverting any unauthorized edits I make. If so, the real solution is telling the user that pages need to be added through the Figma Make interface itself, which would then generate the corresponding entrypoint exports automatically -- though I'm second-guessing whether that maps cleanly to how Figma Make (the coding tool) actually works versus the Figma design editor.
Wait, rereading the system reminder - it says "by the user or by a linter," but maybe it's actually the platform itself resetting the file when "Enable pages" is clicked, not a manual user edit. That would mean Figma Make resets the entrypoint to its default single-export state and then expects Claude to rebuild the page exports from scratch as part of the setup flow.
But maybe I'm wrong about exports entirely - perhaps "pages" in Figma Make doesn't work through named exports in that file at all, but instead through client-side routing, where the preview iframe navigates between URL routes rather than switching exports. That would mean the fix is to make sure a proper browser router is configured so the pages dropdown reflects actual routes.
I recall switching to createMemoryRouter earlier to avoid useNavigate() errors in the iframe, but that conflicts with what's needed now for real URL-based pages. Switching back to createBrowserRouter with the safe navigation hooks should let routes act as pages while still handling context errors gracefully.
Actually, "Enable pages" in Figma Make is a platform feature -- it manages __figma__entrypoint__.ts, and pages should be added through the Figma Make UI rather than by me editing that file directly. Once the user adds pages there, each gets a named export I can then wire up to the correct components.
