AI-native
Components can describe themselves — their state, their content, their intent — onto a live context bus. A built-in assistant and command palette read that bus, so AI features understand the page without you wiring prompts by hand. It's opt-in per component, and off unless you turn it on.
The assistant and command palette in this site's header read the same context bus these pages publish to. Open the assistant and it already has the page in context — no prompt wiring by hand.
Command palette: Ctrl / ⌘ + K
AI-aware components publish a structured summary of themselves — what they are, their current state, their content — to a shared bus the assistant can read in real time.
CAssistant reads the context bus, so it can answer about what's actually on the page. It's the panel wired into this site's header — try the Ask AI button.
A keyboard-first command surface that surfaces actions and navigation from the same context — the kind of palette power users expect, included.
An SEO primitive derives structured metadata from page content, so discoverability isn't an afterthought you bolt on later.
AI context is off by default. A component contributes only when you set its ai prop — silence one without affecting its siblings.
Message, prompt, reasoning, and tool components for building conversational surfaces — the UI of an AI feature, already designed.
The context bus, assistant, and command palette are part of the framework. Let's talk about what you want them to do.