user-feedback: dashboard branching instructions do not match current UI

Start with SKILL.md, especially Core Principles and Supabase Documentation, then compare the linked branching documentation with the current dashboard UI. Update the branch-management guidance to prefer list_branches, get_cost, confirm_cost, and create_branch, and make manual steps depend on verified current UI such as Feature previews or the main / PRODUCTION selector.

What happened

Task: Safely create an isolated Supabase development branch to runtime-test a migration without touching production.

Skill said: The workflow, following the documentation surfaced by the skill, told the user to open the profile menu, select Branching via dashboard, and click Enable feature. In the current dashboard, that menu item does not exist; the menu shows Feature previews instead. An earlier instruction also incorrectly told the user to look for a Branches sidebar item.

Expected: The skill should account for the current public-alpha UI and avoid guessing dashboard navigation. For branch work, it should first use the available branch-management tools (list_branches, get_cost, confirm_cost, and create_branch) when available. If manual dashboard steps are necessary, it should verify the exact current UI and direct the user through Feature previews and/or the top main / PRODUCTION branch selector as actually displayed.

Source

File: SKILL.md

Section: Core Principles > Supabase changes frequently — verify against changelog and current docs before implementing and Supabase Documentation

The official page retrieved through the prescribed docs search was docs/guides/deployment/branching/dashboard, section Enable branch management via the dashboard. It currently says to select Branching via dashboard directly from the user menu, which did not match the live dashboard shown by the user.

Fix suggestion

Add a branch-management note that dashboard branching is public alpha and UI paths may lag the docs. Prefer direct branch MCP/API tools when available. For manual UI guidance, require inspection of the live screenshot or verified current UI before giving click-by-click steps, and note that feature opt-ins may now be nested under Feature previews.