Repository navigation
feat(user-interface): install-and-test the deferred and unconfirmed routes #6379
Description
Problem
plugins/user-interface/reference/routing.json ships 20 deferred rows (account-bound or Mac-only) and 4 unconfirmed rows. /user-interface:design never routes to a deferred row, so the account_tools_enabled option has no effect until at least one account-bound route is confirmed. PR #6318 confirmed the other 25 routes by install, detect, and a routed prompt; these were left for later by design.
Confirming the rows is not enough on its own: the skill routes an account-bound row only when reachable is true (skills/design/SKILL.md Step 4), but scripts/detect.mjs returns reachable: null for every installed non-MCP row whose account is not none, and a kind: tool row such as /design never appears in installed at all. So a confirmed account-bound plugin or tool row would still never be chosen.
Rows
Unconfirmed (install and detect pass, but the WSL test host had no usable browser):
chrome-devtools-mcp@claude-plugins-official(accessibility-review, responsive-testing)playwright@claude-plugins-official(accessibility-review, responsive-testing)
Deferred, account-bound: figma@claude-plugins-official (typography-color, design-systems, design-tool-handoff), /design (design-systems, mockups-variants), magic (component-libraries, icons-imagery), supernova, manage-design-system, axe-accessibility (paid), canva@claude-plugins-official, penpot, Framelink Figma MCP, superdesign@claude-plugins-official, generate-design, v0, adobe-for-creativity@claude-plugins-official, runway-api@claude-plugins-official.
Deferred, Mac-only: xcode, sketch (also paid).
Fix
- Give account-bound non-MCP rows a reachability answer the skill can act on: probe it where a probe exists (a
keyrow's environment variable is set; akind: toolrow is in the session's tool listing, which the skill checks itself), or let Step 4 acceptreachable: nullfor an account-bound row whenaccount_tools_enabledis on and say the route may need sign-in. Add a test for each shape. - For each row, on a host that can run it (a browser for the two MCPs, an account or key for the account-bound rows, macOS for the Mac-only ones): read the candidate's repository, install it at local scope from a non-git folder (fix: claude plugin install --scope local from a worktree writes the main checkout's settings.local.json #6375), confirm
detectreports it andreachableis right, run one routed prompt, uninstall. Setstatustoconfirmed, or record why it stays deferred. - Once one account-bound row is confirmed and routable, drop the "No effect yet" sentence from the
account_tools_enableddescription inplugin.jsonand regenerate the README options reference.
Related
- feat(user-interface): new plugin — project-first interface guidance with terminal UI #6298, feat(user-interface): add the user-interface plugin #6318 (Phase 7 method and results; the reachability gap was found in its full-diff code review), fix: claude plugin install --scope local from a worktree writes the main checkout's settings.local.json #6375.
🤖 Generated with Claude Code
Activity
github-actions commentedon Oct 4, 2026
Thanks for filing this. I understand the ask: confirm the 2 unconfirmed MCP routes (chrome-devtools-mcp, playwright) and the 16 deferred routes (14 account-bound, 2 Mac-only) in
plugins/user-interface/reference/routing.json, following the install/detect/route/uninstall method from #6318, and once an account-bound row is confirmed, update theaccount_tools_enableddescription and regenerate the README. This is a clear, self-contained follow-up with no open questions in the body.I didn't find any existing open issue duplicating this one. It links cleanly to its stated predecessors (#6298, #6318, #6375).
No action needed from you right now — flagging priority as low since it's a deferred-testing follow-up rather than something blocking current functionality, but a maintainer may re-prioritize.
Automated triage. A maintainer reviews it.
feat(user-interface): confirm browser MCP and Claude Design routes, a…
kyle-sexton commentedon Oct 5, 2026
Closing via #6429 when it merges. What it settled:
chrome-devtools-mcp@claude-plugins-officialandplaywright@claude-plugins-official. Each was installed at local scope on the Windows lane, detected, routed for accessibility-review with its MCP tools loaded, and then uninstalled. Claude Design is also confirmed: the/designrows named a command that does not exist, so they now route to theArtifacttool's Design and Design System types. That tool loads in an interactive session with a claude.ai login, not in headless-p.reachableisnullis now routable whenaccount_tools_enabledis on, and the user is told they may need to sign in.xcodeandsketch, stay deferred, andplugins/user-interface/reference/routing.jsonkeeps them on record. Reopening them is a new issue once a Mac is available.