Vibecode PromptDC
track this build5 steps, step by step0%YES · one-shottable
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 project pack4 files · fastest path to a working personal build
You are building a lean indie version of PromptDC. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # PromptDC indie build ## Goal Build the smallest trustworthy replacement for the core PromptDC workflow for one developer or a tiny team. ## Scope Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Page Assist instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build 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. ## Required capabilities - OpenAI or Anthropic API key - Chrome developer mode with Load unpacked ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of PromptDC. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # PromptDC indie build ## Goal Build the smallest trustworthy replacement for the core PromptDC workflow for one developer or a tiny team. ## Scope Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Page Assist instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build 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. ## Required capabilities - OpenAI or Anthropic API key - Chrome developer mode with Load unpacked ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of PromptDC. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # PromptDC product brief ## Problem 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. ## Product outcome Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - OpenAI or Anthropic API key - Chrome developer mode with Load unpacked ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted PromptDC capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# PromptDC indie build ## Goal Build the smallest trustworthy replacement for the core PromptDC workflow for one developer or a tiny team. ## Scope Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Page Assist instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build 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. ## Required capabilities - OpenAI or Anthropic API key - Chrome developer mode with Load unpacked ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# PromptDC product brief ## Problem 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. ## Product outcome Select text, choose Writing or Coding, call an LLM with the matching rewrite prompt, then replace the selection or copy the result. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - OpenAI or Anthropic API key - Chrome developer mode with Load unpacked ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted PromptDC capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent
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.
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
share on X ↗"I just replaced PromptDC ($9/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Page AssistA browser sidebar that reads the page, rewrites the selection, and saves custom actions; your local model does the thinking.open source↗
Writing ToolsSelect text anywhere, hit a hotkey, and fix, rewrite, summarize, or obey a custom instruction without opening another tab.open source↗
WitsySystem-wide selected-text commands, reusable experts, a scratchpad, and document context; bring the model and skip the subscription.open source↗all 3 free alternatives to PromptDC →· no votes, no pay-to-list · just what's real
PromptDC pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| pro | $9 | — | 200 prompt enhancements/month; 50 prompt/Markdown files; unlimited profiles. |
| enterprise | $15 | — | Unlimited enhancements, prompt/Markdown files, and profiles. |
| lifetime | custom | — | Unlimited local/BYOK use. |
free tierno free tier
billingmonthly only for Pro and Enterprise; no annual plan; separate one-time Lifetime license
hidden costsThe Lifetime license is BYOK, so model-provider API charges are separate.
verified 2026-08-12 · source ↗
Vibecode PromptDC
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal PromptDC replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does PromptDC cost?
PromptDC costs about $9/month (Pro, checked 2026-07-30), which is $108 per year. That's what you save by replacing it with one prompt.
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?
Yes: Page Assist (A browser sidebar that reads the page, rewrites the selection, and saves custom actions; your local model does the thinking.) Writing Tools (Select text anywhere, hit a hotkey, and fix, rewrite, summarize, or obey a custom instruction without opening another tab.) Witsy (System-wide selected-text commands, reusable experts, a scratchpad, and document context; bring the model and skip the subscription.) All 3 curated free alternatives are at vibecodeit.com/promptdc/alternatives. The prompt is for when you want it exactly your way.