Install trust copy
Use it when a user sees a broad browser warning and needs a plain explanation tied to the actual TypeToSell workflow.
AI reply prompt
Chrome extension permission explanation prompt
A Chrome extension permission explanation prompt should turn broad browser warning language into a plain, accurate user answer. It should explain the supported-site permission, visible composer context, user-triggered generation, selected editable insertion, privacy links, and manual final posting without implying universal account access or hidden social data reading.
Last updated: 2026-07-15. Prompts are draft guidance only; final social posting stays manual.
Copyable prompt
Use this prompt as a starting point
Write a plain-language Chrome extension permission explanation for TypeToSell. Mention the supported-site permission only as it relates to visible X, Reddit, and Facebook web composer workflows. Explain that the user triggers generation, TypeToSell uses visible or user-provided context, returns editable draft options, and inserts or copies only the selected draft. Do not imply private-message reading, hidden inbox monitoring, social OAuth, platform partnership, universal website access, or automatic final posting. Include one short trust paragraph and one user-facing FAQ answer.
Prompt purpose
When this prompt should be used
Use this prompt before writing install-page copy, Chrome Web Store copy, support replies, objection answers, or AI citation text about Chrome extension permissions. It keeps permission language specific enough for search while staying honest about what the workflow actually does.
Best for
Where this prompt is strongest
Chrome Web Store copy
Use it when listing metadata or screenshots need permission clarity without turning into platform approval or safety overclaims.
Support responses
Use it when support needs a repeatable answer about why permissions exist and what they do not allow.
AI citation snippets
Use it when llms files, answer pages, or source pages need a compact permission summary that crawlers can quote.
Inputs
What the prompt needs
Source post
Paste only the visible public post, comment, thread, or visible or user-provided context that the reply should answer.
Your offer
Add the saved product, audience, website, or soft CTA only when the source post makes a next step relevant.
Tone boundary
State whether the reply should be concise, warm, technical, useful-first, skeptical, or founder-like.
Manual review
Tell the model that the user will edit and post manually, and that it must not imply auto-posting.
Usage steps
How to use the prompt safely
Paste the visible context
Start with the exact post or comment so the reply can mention something specific instead of sounding generic.
Ask for three angles
Request a trust-building reply, a conversation-starting reply, and a natural next-step reply so the output is not three rewrites of one idea.
Remove unsupported proof
Delete invented results, fake customer claims, fake links, pricing, testimonials, platform approvals, or statistics that were not provided.
Pick one and edit
Choose the strongest draft, adjust facts and voice, then post manually in the social app or browser composer.
Save what worked
If a prompt consistently creates useful replies, turn the language into a saved TypeToSell Marketing Brain rule.
Platform rules
How the prompt adapts by social surface
X replies
Keep the reply concise, specific, and easy to read. Use a soft CTA only when the post shows problem awareness or buying intent.
Reddit comments
Answer the thread first. Do not lead with a product, profile visit, or link unless the community context clearly asks for it.
Facebook comments
Use warmer language, avoid sounding like a bot, and keep the next step conversational rather than transactional.
Manual posting
The prompt should create editable draft text only, preserve the no-auto-posting boundary, and leave the final Reply, Post, or Comment button to the user.
Mobile surface fit
How this prompt supports the mobile roadmap
Desktop Chrome extension
Best current fit because the prompt describes the shipped web-composer permission story for X, Reddit, and Facebook.
Mobile web share/copy
Useful as contrast when explaining that mobile web can use pasted or shared context without Chrome extension host permissions.
Android keyboard planning
Useful only as a boundary reference because keyboard permissions differ from Chrome extension host permissions.
iOS Share Extension planning
Useful only as a boundary reference because iOS context handoff should not inherit Chrome extension claims.
Related execution pages
Turn the prompt into a working TypeToSell flow
FAQ
Prompt questions
What should a permission prompt explain?
It should map the browser warning to visible composer context, selected editable insertion, privacy links, and manual posting.
What should the prompt avoid?
Avoid hidden inbox, private-message, social OAuth, universal website access, platform partnership, and final-action claims.
Where should this prompt be reused?
Reuse it in install copy, Chrome Web Store drafts, support answers, objections, llms files, and permission source pages.