Documentation

System Prompt Logic.

PromptDC uses built-in system prompt logic to rewrite vague coding requests into clearer, implementation-ready prompts. That logic works with your selected settings (Simple/Structured mode, language, format, and other rewrite controls) so the output matches your coding workflow.

How PromptDC logic works

PromptDC applies internal rewrite logic before the prompt is sent to the target AI workflow. It restructures vague requests into clearer coding instructions, adds scope/constraints, and shapes output expectations based on your selected settings.

This is not one generic prompt enhancer path. PromptDC uses platform-aware / model-aware rewrite profiles so the rewrite logic matches where you are using it (Chrome web AI apps vs IDE extensions and the selected target profile).

  • Simple mode for faster, compact rewrites.
  • Structured mode for more explicit specs and multi-step tasks.
  • Language + format settings affect the final rewritten output.
  • PromptDC remains a coding-first rewriter unless you choose to override the logic.
  • Chrome flow: PromptDC detects the supported web app and applies the matching rewrite behavior.
  • IDE flow: you choose the target model/IDE profile in the sidebar, and PromptDC uses that profile for rewriting.

How target detection works

PromptDC supports three main usage paths: Chrome web apps, Cursor-family IDE workflows, and the VS Code extension workflow. The rewrite logic is selected from that context first, then refined by your settings (mode, language, format, and custom override).

  • Chrome extension: PromptDC detects the supported AI site and shows the floating toolbar above the chat input.
  • Cursor extension path: you choose the target profile (Cursor, Windsurf, Trae, Kiro, Claude Code, Codex, etc.) in the sidebar.
  • VS Code extension path: you choose the target profile (Copilot, Cline, Codex, Claude Code, Gemini, etc.) in the sidebar.
  • PromptDC then applies the matching coding-first rewrite logic before inserting/replacing the prompt.

Override with your own system prompt

You can replace PromptDC's default rewrite logic with your own custom system prompt. This is useful when you want strict internal standards, framework rules, or organization-specific prompt behavior.

  • Override PromptDC logic with your own system instructions.
  • Keep custom standards consistent across repeated coding tasks.
  • Combine with Simple/Structured mode and format controls.
  • Use for framework rules, testing requirements, and codebase conventions.

Save and reuse multiple system prompts

Save custom system prompts in your PromptDC Library so you can reuse multiple prompt setups for different projects (frontend, backend, debugging, security, etc.). You can manage and reuse them from the PromptDC sidebar in both Chrome and IDE extensions.

  • Chrome extension: open the sidebar from the floating toolbar Settings button and access Library / Community.
  • IDE extensions: open the PromptDC sidebar (Settings, Library, Community) from the activity bar.
  • Store system prompts as reusable library items and copy/paste them into your workflow when needed.
  • Maintain multiple system prompts for different teams, stacks, or task types.