Overview
This prompt guides developers to align the `anchorPosition` logic between two codebases, ensuring consistent behavior. It benefits software engineers maintaining the DQEStudiesGrid component and its integration with dqeClient.
Prompt Overview
Purpose: To align anchorPosition logic between DQEStudiesGrid and dqeClient.
Audience: Developers maintaining the programming and coding project.
Distinctive Feature: Ensures both components use identical positioning behavior.
Outcome: DQEStudiesGrid now matches dqeClient’s anchorPosition implementation exactly.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Development Tools & DevOps, Productivity & Workflow
- Techniques: Decomposition, Self-Critique / Reflection, Structured Output
- Models: GPT-4, Claude 3 Opus, Llama 4 Maverick
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
Update the logic for `anchorPosition` in `DQEStudiesGrid` to match the logic used in `dqeClient`, ensuring it behaves identically and not in the opposite way. Review the current implementation of `anchorPosition` in both `DQEStudiesGrid` and `dqeClient`. Refactor or modify `DQEStudiesGrid` so that the `anchorPosition` aligns exactly with the behavior and logic of `dqeClient`.
# Steps
1. Analyze the existing `anchorPosition` logic in `dqeClient`.
2. Analyze the existing `anchorPosition` logic in `DQEStudiesGrid`.
3. Identify differences or opposing behavior between them.
4. Refactor the `anchorPosition` logic in `DQEStudiesGrid` to mirror `dqeClient`’s implementation.
5. Test changes to confirm that `DQEStudiesGrid` now has the correct, matching behavior.
# Output Format
Provide a detailed explanation or code snippet showing the updated `anchorPosition` logic in `DQEStudiesGrid` that matches `dqeClient`. Include before and after comparisons if applicable. Use clear, commented code or a summary of changes.
# Notes
– Ensure no unintended behavior changes occur elsewhere in `DQEStudiesGrid`.
– Maintain consistency and readability in code.
– If possible, include unit tests that verify the correction.
Screenshot Examples
[Insert relevant screenshots after testing]
How to Use This Prompt
- Analyze anchorPosition logic in both components.
- Identify differences causing opposite behavior.
- Refactor DQEStudiesGrid to match dqeClient exactly.
- Test thoroughly to confirm matching behavior.
- Add unit tests to verify the correction.
- Document changes for clarity and maintenance.
Tips for Best Results
- Review dqeClient logic: Examine the exact calculation and conditions used for anchorPosition in dqeClient to understand the target behavior.
- Compare DQEStudiesGrid logic: Identify where DQEStudiesGrid currently deviates or implements the opposite condition or offset.
- Refactor with matching logic: Replace the anchorPosition calculation in DQEStudiesGrid with the same logic as dqeClient, ensuring identical variable usage and conditional checks.
- Validate with tests: Run existing tests and add new ones to confirm both components now behave identically for all edge cases.
FAQ
- What is the main goal of updating anchorPosition?
To make DQEStudiesGrid behave identically to dqeClient, not oppositely, by matching their anchorPosition logic. - How should you start the refactoring process?
Analyze both implementations, identify differences, then modify DQEStudiesGrid to mirror dqeClient’s logic. - What must you ensure after making changes?
Test thoroughly to confirm matching behavior without unintended side effects elsewhere in DQEStudiesGrid. - What should the output include?
Detailed explanation or code snippet showing updated logic, with before/after comparisons if applicable.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (March 2026): Initial release.
