Polyxd

ClaudeCommunityby Polyxd

Polyxd shows interactive screens right in the conversation. Ask Claude to split a bill, return an order, fill in a form, compare plans or summarise a week of numbers, and instead of a wall of text you get a real interface: fields to fill in, choices to make, a receipt that adds up, a chart with a plain-words summary, and buttons that do what they say. Claude writes each screen as a small Polyxd document, a JSON description of what the screen means rather than how it looks. The connector checks it against the open Polyxd specification before anything is shown: every value bound to real data, labels that say what happens, one primary action at a time, no more than six inputs per view, and confirmations before anything consequential. A screen with errors is never shown; Claude fixes it first. Then Polyxd draws it in the design system you choose. The same screen looks native in Material 3, IBM Carbon, GOV.UK, Fluent 2, shadcn/ui, Shopify Polaris, GitHub Primer, Adobe Spectrum 2, Ant Design, Bootstrap, Chakra UI, Mantine and Radix Themes, or in one of twelve original templates, in light or dark mode. When you press a button, the choice comes back to Claude as your next message, with the values you entered, so the conversation carries on from what you did. Ask about Polyxd itself, such as how to add it to a React app or run the verifier in CI, and Claude answers from the Polyxd docs, with links to the pages. Designers and product teams use it to try out a flow in their own design system in seconds. Anyone can use it to get a clear, usable screen instead of a long answer. Every tool is read-only. The connector needs no account, sees only the screens Claude sends it, stores nothing, and does not reach the internet. Polyxd is open source (Apache-2.0); the specification is CC-BY-4.0.