Open Prompts
Submit a prompt
Coding

Framework and Database Migration Assistant

Plans a framework, database, or API migration from your current setup to a target one, honoring the compatibility window, downtime limit, and behavior you say must be preserved. - Takes old/new stack, current and target setup, and hard constraints as input - Outputs an ordered migration checklist, tackling the riskiest changes first - Generates code transformations for common patterns and lists breaking changes - Includes a rollback plan and validation tests to confirm the migration worked

Prompt
Help me migrate from {{old}} to {{new}}.

Current setup:
{{current_setup}}

Target:
{{target_setup}}

Constraints:
- Must maintain backwards compatibility for {{compat_duration}}
- Cannot have downtime longer than {{downtime_limit}}
- Must preserve {{preserved_behavior}}

Generate:
1. Migration checklist (ordered steps)
2. Code transformations for common patterns
3. Breaking changes to watch for
4. Rollback plan
5. Validation tests to confirm migration worked

Start with the riskiest parts first.
Download .md

Variables

Related prompts

Coding

Database schema design assistant

Describe a feature in plain language along with your database engine, expected scale, and existing tables to get a second opinion before writing migrations that are painful to undo. Returns proposed tables, keys, and indexes with the reasoning behind each normalization or denormalization decision, flags which constraints belong at the database level instead of application code, and stress-tests the design against one likely future change.

Coding

Architecture Tradeoff Advisor

Describe a system you're about to build along with its scale, team, timeline, and current plan, and get tradeoffs surfaced instead of textbook best practices. - Ranks the top 3 risks specific to your approach - Identifies what would break first at 10x scale - Proposes the simplest version you could ship first - Best used before writing code — for schema design, API contracts, or system boundaries

Coding

Structured Feature Implementation Request

Fill in the feature you want built, the language, and up to three specific requirements, and get an implementation request structured enough that nothing important gets skipped. It explicitly asks for error handling, edge cases, performance, and framework best practices to be considered up front, and instructs the output to keep existing comments intact and explain its own logic inline.