Prompt file imported from Yandievss/archon.ai (.windsurf/workflows/fix-dead-buttons.md). Copyright stays with the author.

You will make every button on the target page functional.

Steps:

Inventory all clickable UI elements (buttons, icon buttons, menu items, table row actions).
For each element, classify: A) Navigation (route change) B) Mutation (create/update/delete) C) UI state (open modal/drawer, tabs, filters)
Implement missing handlers end-to-end:
- UI action -> function -> API route/server action -> validation -> DB -> toast feedback.
If an action is intentionally not implemented:
- disable the button + tooltip "Binnenkort"
- add TODO with a tracking issue id.
Add loading state and error handling for every mutation.
Return a checklist of all buttons and their status (implemented/disabled).
Respect existing dashboard navigation contract in src/app/page.tsx (?page= sync + localStorage persistence).
Run and report:
- npm run typecheck
- npm run lint
- npm run build
- relevant Playwright spec(s)

You will make every button on the target page functional. Steps: 1) Inventory all clickable UI elements (buttons, icon buttons, menu items, table row actions). 2) For each element, classify: A) Navigation (route change) B) Mutation (create/update/delete) C) UI state (open modal/drawer, tabs, filters) 3) Implement missing handlers end-to-end: - UI action -> function -> API route/server action -> validation -> DB -> toast feedback. 4) If an action is intentionally not implemented: - disable the button + tooltip "Binnenkort" - add TODO with a tracking issue id. 5) Add loading state and error handling for every mutation. 6) Return a checklist of all buttons and their status (implemented/disabled). 7) Respect existing dashboard navigation contract in `src/app/page.tsx` (`?page=` sync + localStorage persistence). 8) Run and report: - npm run typecheck - npm run lint - npm run build - relevant Playwright spec(s)

Install fix-dead-buttons and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

fix-dead-buttons

About

Use it

Install fix-dead-buttons and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews