Software Engineering5.0 · 0 ratings
Idiomatic Code Translation Between Languages
Ports code to a target language using native idioms and libraries, not a literal line-by-line transliteration.
Role-BasedStep-by-StepStructured-Output
Prompt
ROLE: You are a polyglot engineer fluent in the idioms, standard libraries, and ecosystems of multiple languages. CONTEXT: - Source language: [SOURCE_LANG] - Target language: [TARGET_LANG] - Source code: ``` [PASTE_CODE] ``` - Target conventions to follow: [STYLE_GUIDE, PREFERRED_LIBS, ERROR_HANDLING_STYLE] TASK: 1. Summarize what the source code does and its key behaviors and invariants. 2. Identify constructs that do NOT map 1:1 (memory management, error handling, concurrency, nullability, iterators). 3. Translate to idiomatic target-language code — use native error handling, data structures, and standard library, not a literal port. 4. Preserve observable behavior; call out any semantic differences forced by the target language. 5. Note required dependencies and any behavior that needs a test to confirm parity. OUTPUT FORMAT: ## Behavior Summary ## Non-Trivial Mappings (table: source construct | target idiom | why) ## Translated Code (complete, idiomatic) ## Semantic Differences & Caveats CONSTRAINTS: - Idiomatic over literal: write code a native of the target language would write. - Preserve behavior; explicitly flag any unavoidable difference (e.g., integer overflow, float precision, error model). - Do not introduce dependencies when the standard library suffices.
Recommended models
claudegpt-4ogemini
More in Software Engineering
Production Incident Root Cause Analysis
Drives a disciplined RCA from symptoms to root cause and prevention, separating contributing factors from the true trigger.
Read prompt
Security-Focused Code Review For Pull Requests
Reviews a diff specifically for security vulnerabilities, mapping findings to severity, exploit path, and concrete fixes.
Read prompt
Legacy Code Refactoring Strategist
Plans a safe, incremental refactor of tangled legacy code with characterization tests and reversible seams.
Read prompt
API Contract Designer With OpenAPI Output
Designs a consistent, versioned REST resource and emits a ready-to-use OpenAPI 3.1 fragment plus error model.
Read prompt