Save & Access Prompts Across AI Tools

Convert the following prompt into a universal format that works consistently across ChatGPT, Claude, Gemini, and Copilot.

Original prompt:
{{original_prompt}}

Original tool: {{original_tool}}

Generate:
1. A tool-agnostic version that preserves all instructions
2. Notes on which parts relied on tool-specific features
3. Any adjustments needed for each target tool
4. The recommended structure: role, context, task, constraints, output format
5. Variable placeholders (using {{variable}} syntax) for parts that change per use

I have a prompt that works well in {{source_tool}} but I need to optimize it for {{target_tool}}.

Working prompt:
{{working_prompt}}

What it produces in {{source_tool}}: {{current_output_description}}

Adapt the prompt for {{target_tool}} by:
1. Adjusting for the model's known strengths and weaknesses
2. Reformatting instructions to match the tool's conventions
3. Updating any system/user message split as appropriate
4. Preserving the exact same output format and quality
5. Adding tool-specific optimizations (e.g., Claude's XML tags, GPT's function calling)

I have {{prompt_count}} prompts saved across various tools and documents. Help me organize them into a structured library.

Current prompts (titles/descriptions):
{{prompt_list}}

Design an organization system with:
1. Folder structure (max 2 levels deep) based on these prompts
2. Tagging taxonomy (categories, use cases, models, status)
3. Naming convention for prompt titles
4. Which prompts should be merged (similar/duplicate)
5. Which prompts need a description or metadata added
6. Priority order for migration (most-used first)

I use {{tools_list}} daily and need a strategy for keeping my prompts in sync across all of them.

Current pain points:
{{pain_points}}

Design a sync workflow that:
1. Identifies a single source of truth for each prompt
2. Defines when and how updates propagate to other tools
3. Handles conflicts when the same prompt is edited in two tools
4. Minimizes manual copy-paste steps
5. Leverages MCP or API integrations where available
6. Includes a weekly maintenance routine (5 minutes max)

I'm migrating my prompts from {{source_system}} to {{target_system}}.

Total prompts: {{prompt_count}}
Current organization: {{current_organization}}
Key requirements: {{requirements}}

Create a migration plan:
1. Pre-migration audit: what to clean up before moving
2. Mapping: how the current structure maps to the target system
3. Migration order: which prompts to move first (by priority/usage)
4. Validation: how to verify each prompt works after migration
5. Cutover plan: when to switch from old system to new
6. Rollback: how to revert if something goes wrong

Design a backup strategy for my prompt library of {{prompt_count}} prompts stored in {{primary_system}}.

Critical prompts: {{critical_prompt_descriptions}}
Update frequency: {{update_frequency}}

The backup strategy should cover:
1. What to back up (prompts, versions, metadata, folder structure, tags)
2. Backup format (JSON, Markdown, or both) with a sample structure
3. Backup frequency and automation options
4. Storage locations (at least 2 for redundancy)
5. Restore procedure: step-by-step instructions
6. Verification: how to confirm backups are complete and restorable