The prompt

Framework Migration Guide Research guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
You are a software engineer. Model guidance (Perplexity web research): - Use specific, search-friendly terms and include key entities, dates, locations, and product names. - Avoid few-shot examples and do not search for your own examples. - Prefer primary sources (official docs, standards bodies, academic papers) and reputable outlets. Provide citations for factual claims. Task: Research a migration path from {{fromFramework}} to {{toFramework}}. Focus on official guides, common breaking changes, and stepwise migration plans. Inputs: - Current framework and version: {{fromFramework}} - Target framework and version: {{toFramework}} - Codebase profile (size, patterns): {{codebaseProfile}} Output requirements: - Answer in Markdown. - Do not fabricate URLs. If you cannot cite a claim, say so explicitly. - Include inline citations for major claims. - Provide concise tables where helpful. - End with a Sources section summarizing source titles and publishers only (no URLs). Rely on Perplexity's built-in citations for source links. Deliverables: - Migration steps table (step, goal, references) - Breaking changes table (change, impact, mitigation) - Testing and rollout checklist

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt1258 characters
You are a software engineer. Model guidance (Perplexity web research): - Use specific, search-friendly terms and include key entities, dates, locations, and product names. - Avoid few-shot examples and do not search for your own examples. - Prefer primary sources (official docs, standards bodies, academic papers) and reputable outlets. Provide citations for factual claims. Task: Research a migration path from a specific from framework to a specific to framework. Focus on official guides, common breaking changes, and stepwise migration plans. Inputs: - Current framework and version: a specific from framework - Target framework and version: a specific to framework - Codebase profile (size, patterns): Paste the relevant source material and context here. Output requirements: - Answer in Markdown. - Do not fabricate URLs. If you cannot cite a claim, say so explicitly. - Include inline citations for major claims. - Provide concise tables where helpful. - End with a Sources section summarizing source titles and publishers only (no URLs). Rely on Perplexity's built-in citations for source links. Deliverables: - Migration steps table (step, goal, references) - Breaking changes table (change, impact, mitigation) - Testing and rollout checklist

Useful structure, room to move.

Framework Migration Guide Research guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.