My original application I had in mind, has to do specifically with systems management…
- User
My original application I had in mind, has to do specifically with systems management and glue code, for instance scripts or subroutines that mirror databases, or store certain structured data (one can think that a sort of meta-structure of that data would be abstracted out to yield benefit elsewhere). Can you reformulate my original prompt here without being overly specific (as that would cause bias in the prompt) to hint at such a mode of application?
- Assistant
I see - you're looking for a prompt that focuses on system integration patterns and "glue code" abstraction. This is an excellent application area where abstraction can provide tremendous value. Let me reformulate the prompt to subtly guide in this direction without over-constraining it:
Overlay Prompt for Abstract System Integration Patterns
You are a systems integration abstraction expert. When presented with programming or automation tasks, especially those involving data movement, synchronization, or integration between systems: 1. **Extract the architectural pattern** first, before discussing implementation details. Identify the abstract data flow pattern (e.g., "Incremental Synchronization", "Message Queue Consumer", "ETL Pipeline"). 2. **Model data structures generically**: - Represent schemas as abstract entity relationships - Replace specific field names with [DOMAIN_ATTRIBUTE] placeholders - Identify transformation patterns (normalization, denormalization, aggregation) 3. **Parameterize all environment-specific elements**: - Connection details as [SOURCE_CONNECTION] and [DESTINATION_CONNECTION] - Authentication as [AUTH_MECHANISM] - Scheduling as [TRIGGER_CONDITION] 4. **Present solutions in layers**: - [PATTERN] - The abstract integration archetype - [DATA_FLOW] - The sequence of data movement operations - [CONTROL_FLOW] - Error handling, retries, transaction boundaries - [OBSERVABILITY] - Logging, monitoring, alerting concepts - [IMPLEMENTATION_NOTES] - Technology-specific considerations (as secondary information) 5. **Focus on resilience patterns**: - Idempotence mechanisms - Partial failure handling - State management across process boundaries When providing examples, use pseudocode that emphasizes the structural relationships rather than syntax. For instance: ```plaintext [PATTERN] Bidirectional Synchronization with Conflict Resolution [DATA_FLOW] 1. Capture changes from [SOURCE_A] since [LAST_SYNC_TIMESTAMP] 2. Capture changes from [SOURCE_B] since [LAST_SYNC_TIMESTAMP] 3. Apply [CONFLICT_RESOLUTION_STRATEGY] to generate merged changeset 4. Apply merged changes to both systems 5. Record new [SYNC_TIMESTAMP] [CONTROL_FLOW] - If either system unavailable, queue changes for later application - If partial sync occurs, record [PARTIAL_SYNC_STATE] - Implement [RETRY_STRATEGY] with exponential backoff [OBSERVABILITY] - Log change counts by entity type - Alert on [THRESHOLD_EXCEEDED] for conflict rates - Maintain [SYNC_HEALTH_METRIC] [IMPLEMENTATION_NOTES] - Consider using Change Data Capture if available - Timestamp precision requirements vary by system--- This prompt guides the LLM to focus on discovering and abstracting common patterns in systems integration tasks. It encourages thinking about the meta-structure of data flows and transformations rather than getting lost in implementation details, while still acknowledging that environment-specific considerations are important as secondary information. The prompt naturally lends itself to areas like database mirroring, file synchronization, API integrations, event processing pipelines, and other "glue code" that ties systems together, without explicitly limiting its scope to just these applications. Would you like me to refine any aspect of this prompt further? - User
I mean that you should try to reformulate the initial query I posted to you right now in such a way that your generated prompt might have incorporated this. That is to say, I want to ask the same question again but with the added context I just gave you.
- Assistant
I understand now - you'd like me to reformulate your original question to me, incorporating the systems integration context. Here's how you might have asked the question initially:
"Can you help me write a prompt that I can use as an 'overlay' to an LLM which, when asked about programming examples involving system integration or data synchronization tasks, guides the AI to abstract the underlying patterns rather than focusing on implementation details? I'm particularly interested in having the LLM recognize common patterns in 'glue code' that connects different systems or mirrors data between databases, so that the solutions can be applied across different environments and technologies."
This reformulated question maintains your original request for an abstraction-focused prompt overlay, while providing the specific context around systems integration, data synchronization, and the meta-structure of data flows that you're interested in.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.