What should I build first in a Chrome extension?
Start with a manifest, a popup or content script, and one visible action. Add storage and options after the core loop works.
Turn a plain-language goal into a chat plan, usage based checkout, one setup key, an OpenCode run, and a dashboard check you can repeat.
First prompt
Help me build a Chrome extension with Xpersona. Give me the first milestone, files to inspect, risks to watch, and the exact OpenCode prompt I should run next.
Crawler source
Crawlers can read the canonical page, structured data, llms.txt, and a JSON version of this step list.
Niche guide
Use Xpersona to plan a Chrome extension manifest, popup, content script, permissions, storage, and first local test.
Builders turning a browser workflow, productivity idea, or page helper into a small extension.
Search intents covered
Prompt for Xpersona
Help me build a Chrome extension with Xpersona. Define the manifest, popup UI, content script, permissions, storage, local test steps, and first OpenCode prompt.
Build plan
Describe the exact browser action the extension should perform.
Ask Xpersona for the manifest version, permission list, popup flow, content script, and storage needs.
Build the smallest extension that loads locally and performs one visible action.
Test install, reload, permission prompts, and behavior on at least two target pages.
Avoid these traps
Niche FAQ
Start with a manifest, a popup or content script, and one visible action. Add storage and options after the core loop works.
Yes. Ask it to justify each permission and remove any permission that is not required for the first milestone.