People pay for confidence that rewriting works across the sites and editors they use every day, plus maintained profiles, a polished interface, account features, and fixes when web apps change. A personal BYOK clone covers the basic loop well, but keeping rich editors reliable is continuing product work.
REPLACEMENT BRIEF
ai writing
Can AI replace PromptDC?
Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result.
Build the personal version →AT A GLANCE
- price
- $9/mo
- listed annual price
- $108/yr
- replaceable scope
- Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result.
- build time
- one sitting
what AI can build
Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result.
A useful personal version is highly one-shot-able: an MV3 content script can capture selected text, send it to an LLM with one of two system prompts, then replace a normal editable field or copy the result. The commercial product earns its keep through Writing profiles (grammar fix, email, social post, shorten, tone), a Coding mode that auto-detects which AI tool you are prompting and tailors the rewrite, polished interaction design, and defensive handling of complex editors where naive DOM replacement can fail or corrupt text.
The prompt was editor-reviewed; no completed build is recorded.
The honest tradeoff
why people still pay
what you lose
xWriting profiles tuned for grammar fix, email replies, social posts, shortening, and tone
xCoding mode platform detection that tailors the rewrite to the AI tool you are prompting (ChatGPT, Claude, Cursor, Lovable and more)
xReliable behavior across Gmail, LinkedIn, Google Docs, Shadow DOM, and framework-managed rich text editors
xCloud accounts, usage credits, profile sync, and a managed billing flow
xPolished mode controls, error recovery, ongoing compatibility updates, and support
Start with existing software
prior art · use these instead of building, if you'd rather
No mature prior art is listed yet. The workaround prompt below is still an unverified starting point.
EVIDENCE LEDGER
What this page can prove
The verdict judges replaceability. The evidence level records what DeepFeather actually checked.
The prompt was editor-reviewed; no completed build is recorded.
Pro · monthly per user
known limits · Writing profiles tuned for grammar fix, email replies, social posts, shortening, and tone; Coding mode platform detection that tailors the rewrite to the AI tool you are prompting (ChatGPT, Claude, Cursor, Lovable and more)
Build promptreviewed prompt · not run
the prompt
Curated promptBuild me a personal Chrome extension for rewriting selected text with an LLM. Use Manifest V3, vanilla HTML, CSS, and JavaScript, with no framework, bundler, package manager, or build step. Create manifest.json, background.js, content.js, content.css, options.html, options.js, and simple generated placeholder icons. Request only storage, contextMenus, activeTab, and scripting permissions, plus host permissions for the chosen LLM API. Add an options page that stores provider, API key, and model in chrome.storage.local, never chrome.storage.sync. Support OpenAI and Anthropic through direct fetch calls from the background service worker. Use the OpenAI Responses API or Chat Completions API and the Anthropic Messages API with correct headers and response parsing. Never log the API key or selected text, and show clear errors for a missing key, HTTP failure, rate limit, or malformed response. Provide exactly two modes: Writing and Coding, with the last choice saved locally. Writing mode must offer selectable profiles: Improve, Grammar fix, Shorten, Email, Social post, and Tone, each with its own system prompt that preserves facts and meaning, matches the input language, and returns only the revised text. Coding's system prompt must turn a vague request into an implementation-ready specification with goal, context, requirements, constraints, acceptance criteria, and likely files, while preserving user intent and returning only the enhanced prompt. Create a context menu named Enhance selected text that works on selection and editable contexts. Also inject a small accessible floating button beside any nonempty text selection after mouseup or keyboard selection. The floating UI must include a compact mode selector with the Writing profiles and Coding, an Enhance button, a loading state, and a dismiss control. Capture selections in input and textarea elements with selectionStart and selectionEnd, and capture contenteditable selections with a cloned DOM Range. For input and textarea, replace only the captured range, preserve surrounding text and caret position, and dispatch bubbling input and change events. For contenteditable, restore the saved Range, replace only its contents with a text node, dispatch a bubbling input event, and avoid innerHTML assignment. If the selection is read-only, detached, stale, or cannot be safely replaced, copy the result with navigator.clipboard.writeText and show a small Copied notification. If no selection exists in an editable field, enhance the field's full current value; otherwise show a helpful Select some text message. Pass requests from the content script to the service worker with chrome.runtime.sendMessage so page scripts never receive the API key. Keep the interface unobtrusive, keyboard accessible, responsive, and isolated with prefixed CSS class names and a high z-index. Include an options-page Test API button and a concise README with Load unpacked instructions, provider setup, security caveats, and a manual test checklist. Handle extension reloads and restricted chrome:// pages gracefully, and remove injected UI when the selection collapses or Escape is pressed. Deliberately leave out accounts, sync, per-site profiles, billing, telemetry, analytics, history, and any backend server. Return every file with finished code, not pseudocode or TODOs, so loading the folder as an unpacked extension works immediately.
The prompt stays readable first. Choose a launch option when you are ready.
$ open in your agent (prompt prefilled, you press enter) or copy it raw
BUILD FEEDBACK
Did you try this build?
Report the outcome. Submissions enter a manual evidence queue and never auto-upgrade the verdict.
Want next week’s replacements?
New verdicts + most-wanted, weekly. Free. One-click out.
Share this verdict
questions
Can AI replace PromptDC?
Likely for the core workflow, based on an editorial catalog judgment. This entry is not a verified build yet; use the prompt as a starting point and validate the result against your own acceptance criteria.
How much does PromptDC cost?
PromptDC is listed at about $9/month (Pro, checked 2026-07-30), or $108 per year. This is a pricing reference, not evidence of a completed replacement or realized savings.
What do I lose by replacing PromptDC?
Honestly: Writing profiles tuned for grammar fix, email replies, social posts, shortening, and tone; Coding mode platform detection that tailors the rewrite to the AI tool you are prompting (ChatGPT, Claude, Cursor, Lovable and more); Reliable behavior across Gmail, LinkedIn, Google Docs, Shadow DOM, and framework-managed rich text editors; Cloud accounts, usage credits, profile sync, and a managed billing flow; Polished mode controls, error recovery, ongoing compatibility updates, and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to PromptDC?
No mature open-source alternative is listed yet. The prompt is an unverified starting point, not proof that a one-shot replacement will work.