Documentation

Creating Reusable Files.

PromptDC can store reusable prompt assets as files so you stop rewriting the same context repeatedly. Use files for technical specs, migration checklists, architecture rules, and task templates.

Recommended file types

Project rules

Shared coding standards, naming rules, linting expectations.

Feature specs

Reusable scaffolds for CRUD, auth, dashboards, billing, uploads.

Debugging prompts

Bug triage templates with logs, reproduction, and success criteria.

Review checklists

Code review, QA, security, and release validation prompts.

Where to create files

You can create and manage files from PromptDC in both Chrome and IDE extensions. In Chrome, you can save content from selected text on a page or open Community / Library from the floating toolbar. In IDEs, file creation and management is done from the PromptDC sidebar.

  • Chrome: select/hover text on supported pages and use the right-click action to save it to Library.
  • Chrome: use the floating toolbar above chat to open Community or Library-related flows, then reuse prompts/files.
  • Chrome: type // in supported chat inputs to search and insert library/community prompts and files.
  • IDE: open the PromptDC activity-bar icon, then use the Library tab in the sidebar.
  • Store prompts, system prompts, and markdown files in one place for reuse.

What to put in a reusable file

Good reusable files contain stable instructions that apply across many prompts. They should save setup time, not repeat one-off task details.

  • Project conventions (framework, folder structure, naming, linting, testing).
  • System prompts for specific workflows (frontend feature builds, API debugging, security review).
  • Markdown specs you paste into AI chats before enhancement.
  • Templates with placeholders like feature name, endpoint, schema, or acceptance criteria.

Workflow

  1. Create a prompt, system prompt, or markdown file in your PromptDC Library (Chrome floating toolbar / sidebar flow, or IDE sidebar).
  2. Name it by intent (e.g. “API error handling spec template” or “React strict TypeScript system prompt”).
  3. Tag by type/category/model context for fast filtering and reuse.
  4. In Chrome, insert items from Community/Library using the floating toolbar or // on supported chats. In IDEs, open the Library tab from the PromptDC sidebar and copy/paste into chat.
  5. Enhance the prompt with PromptDC after inserting the file context (or use your saved system prompt override).