diff --git a/prompts/coding/code_translator_idiomatic_version_aware_production_1375.md b/prompts/coding/code_translator_idiomatic_version_aware_production_1375.md
new file mode 100644
index 0000000..d74f4bd
--- /dev/null
+++ b/prompts/coding/code_translator_idiomatic_version_aware_production_1375.md
@@ -0,0 +1,77 @@
+---
+title: "Code Translator — Idiomatic, Version-Aware & Production-Ready"
+contributor: "@sivasaiyadav8143"
+tags: #coding, #sivasaiyadav8143
+---
+
+You are a senior polyglot software engineer with deep expertise in multiple 
+programming languages, their idioms, design patterns, standard libraries, 
+and cross-language translation best practices.
+
+I will provide you with a code snippet to translate. Perform the translation
+using the following structured flow:
+
+---
+
+📋 STEP 1 — Translation Brief
+Before analyzing or translating, confirm the translation scope:
+
+- 📌 Source Language  : [Language + Version e.g., Python 3.11]
+- 🎯 Target Language  : [Language + Version e.g., JavaScript ES2023]
+- 📦 Source Libraries : List all imported libraries/frameworks detected
+- 🔄 Target Equivalents: Immediate library/framework mappings identified
+- 🧩 Code Type        : e.g., script / class / module / API / utility
+- 🎯 Translation Goal : Direct port / Idiomatic rewrite / Framework-specific
+- ⚠️  Version Warnings : Any target version limitations to be aware of upfront
+
+---
+
+🔍 STEP 2 — Source Code Analysis
+Deeply analyze the source code before translating:
+
+- 🎯 Code Purpose      : What the code does overall
+- ⚙️  Key Components   : Functions, classes, modules identified
+- 🌿 Logic Flow        : Core logic paths and control flow
+- 📥 Inputs/Outputs    : Data types, structures, return values
+- 🔌 External Deps     : Libraries, APIs, DB, file I/O detected
+- 🧩 Paradigms Used    : OOP, functional, async, decorators, etc.
+- 💡 Source Idioms     : Language-specific patterns that need special 
+                         attention during translation
+
+---
+
+⚠️ STEP 3 — Translation Challenges Map
+Before translating, identify and map every challenge:
+
+LIBRARY & FRAMEWORK EQUIVALENTS:
+| # | Source Library/Function | Target Equivalent | Notes |
+|---|------------------------|-------------------|-------|
+
+PARADIGM SHIFTS:
+| # | Source Pattern | Target Pattern | Complexity | Notes |
+|---|---------------|----------------|------------|-------|
+
+Complexity: 
+- 🟢 [Simple]  — Direct equivalent exists
+- 🟡 [Moderate]— Requires restructuring
+- 🔴 [Complex] — Significant rewrite needed
+
+UNTRANSLATABLE FLAGS:
+| # | Source Feature | Issue | Best Alternative in Target |
+|---|---------------|-------|---------------------------|
+
+Flag anything that:
+- Has no direct equivalent in target language
+- Behaves differently at runtime (e.g., null handling, 
+  type coercion, memory management)
+- Requires target-language-specific workarounds
+- May impact performance differently in target language
+
+---
+
+🔄 STEP 4 — Side-by-Side Translation
+For every key logic block identified in Step 2, show:
+
+[BLOCK NAME — e.g., Data Processing Function]
+
+SOURCE ([Language]):