Different checks answer different questions.
Static validation
Does Claude recognize the package, hook names and host API calls?
Behavior and host tests
Do the handlers and supported element contracts behave as expected?
Live application check
Does the installed example actually appear and work in your target app build?
A passing browser simulation does not establish Claude Desktop compatibility. Record what you actually ran and the relevant version.
npm test npm run validate npm run test:native npm run site:build npm run site:check
Give the next person a useful handoff.
- The outcome and a small synthetic input.
- The smallest setup and the expected result.
- The event and host APIs used.
- What data persists and how to remove it.
- The exact surface/version checked and any missing acceptance.
Read the repository’s validation record for this starter’s actual scope and remaining live-app checks.
Get unstuck
I installed it in Cowork. Where is the custom pane?
The Cowork plugin demonstrates prompt commands. The UI pane belongs to the separate kitchen-sink mod in a supported Claude Code session. Start with the Desktop Code or Terminal path above.
/kitchen isn’t in the command list.
Check /plugin for an active kitchen-sink mod, then /status for the version. Validate the correct plugin directory. In an existing session, try /reload-plugins. Managed policy can prevent mods from loading.
The command works, but no UI appears.
Run /kitchen-status and inspect the reported surfaces. Headless sessions do not draw. Remote Control shows mod drawings in the host terminal. VS Code has different supported render sites, and the full desktop example should be checked in a local Code session.
My edit isn’t showing up.
For mod development, launch with --plugin-dir ./plugins/kitchen-sink from the repository root. An installed marketplace copy may differ from your working tree. For Cowork, rebuild the ZIP and re-upload. In-memory counters reset when the module reloads.
The draft button did nothing.
It preserves an existing prompt. Clear or send your draft first; the button displays a notice instead of combining unrelated text. It fills the box and leaves sending to you.
Can this be my production command-security policy?
The sample guard only checks the plugin’s imaginary mixing tool. It is a teaching example, not a general shell policy. Read the host’s permission and managed-policy documentation before designing real controls.
How do I remove it or delete my scratch note?
Use the Notes tab’s delete button for the saved note. For an installed plugin, open /plugin and disable or uninstall it. A session loaded with --plugin-dir stops using that copy when you exit. In Cowork, remove the uploaded plugin through Customize.