Project update
We have a clear outline and three follow-ups for the next meeting.
Browser companion overview
browser selection/command and installation boundary.
⌘SpaceOpens Raycast when installed
Context beside a command
Selected content, command choice and resulting prompt remain connected.
Prompt preview
Browser installation
The companion installs from the official browser store.
This public-interface specimen runs locally. Account, billing and native-app actions end at a labelled handoff.
Small actions, useful context
Each feature pairs one purpose with a concrete public structure.
Keep a note
A title, checklist and export affordance.
Find a command
A query, selection and result preview.
Share a starting point
A template, prerequisites and source link.
Show the work in context.
Text and media stay associated when the layout becomes a single column.
Explore a complete public flow.
Open the extension directoryQuestions, with a clear next step
Can this reference install an extension?
No. The install action identifies the official handoff. Installation and account permission happen in the real application.
Where are the public instructions?
The manual and developer documentation have their own external origins. They are labelled boundaries in this reference.
Does the feedback form send my message?
No. It validates the draft in memory and leaves it available for correction. It never sends or persists its contents.
Composition contract and public sources
browser selection/command and installation boundary. This authored implementation is distinct from original DOM/CSS replay. Automated presence, behavior and geometry are reported separately.
Family F-browser-extension; patterns hero, companion, features, faq.
Complete family contracts · Synthetic fixtures · Local schemas
Source capture IDs: CAP-inventory--secondary--browser-extension-1440, CAP-inventory--secondary--browser-extension-390.