Salesprompter

Docs that map the app, CLI, and extension as one system.

Public documentation for the Salesprompter contracts, workflows, and runtime behavior. This deployment is generated directly from the docs source in the CLI repository.

Source repository

The Chrome extension implementation is not in this repository, but the product contract is already clear from the CLI and app expectations.

The extension is a companion surface

The extension should help users work inside the browser, but it should still feel like Salesprompter, not a disconnected tool. Its role is to:

  • capture account or contact context from browser pages
  • assist with prospecting and workflow handoff
  • send structured data back into the app or CLI-compatible artifact flow

Identity rules

The extension should share the same identity model as the app and CLI.

That means:

  • no separate extension-only login system
  • no duplicate user records for the same person
  • no shadow token format that the app cannot verify

If the extension needs privileged backend calls, it should rely on the app’s authenticated session model or app-issued tokens, not invent a fourth auth path.

Data contract rules

When the extension captures structured data, it should map toward the same contracts documented in JSON Contracts:

  • account-like data should converge on AccountProfile
  • captured contacts should converge on Lead
  • enriched or scored objects should preserve the same field semantics as the CLI

If the extension exports domain-candidate or review data, it should preserve provenance so humans can tell whether the source was:

  • page scrape
  • manual user input
  • app lookup
  • warehouse-derived data

Good handoffs:

  • extension captures a company and sends it to the app for account review
  • extension exports account or lead JSON that the CLI can enrich or score later
  • extension opens an app flow that reuses the same user session

Bad handoffs:

  • extension invents its own lead shape that must be transformed ad hoc later
  • extension stores identity independently from the app
  • extension mutates production data without auditable provenance

Documentation status

Because the extension code is not in this repository yet, this page is intentionally contract-first. Once the extension repo exists or is imported, extend this page with:

  • install instructions
  • permissions model
  • supported sites and selectors
  • UX flows
  • release process