Overview
This prompt aims to guide the review process for client-side A/B test code, ensuring best practices are followed. Developers and AI experts will benefit from clear instructions to enhance code quality and compliance.
Prompt Overview
Purpose: The goal is to ensure A/B test code adheres to best practices for optimal performance and user experience.
Audience: This set of instructions is intended for developers and code reviewers working on client-side A/B tests.
Distinctive Feature: The focus is on analyzing JavaScript, CSS, and HTML to identify deviations from established development guidelines.
Outcome: A comprehensive feedback report will highlight adherence to guidelines and suggest actionable improvements for the code.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Business Communications, Development Tools & DevOps
- Techniques: Role/Persona Prompting, Self-Critique / Reflection, Structured Output
- Models: Claude 3.5 Sonnet
- 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
Review and analyze the provided development guidelines for building client-side A/B tests using JavaScript, CSS, and HTML. Based on these guidelines, compose a comprehensive set of instructions for a Claude 3.5 Sonnet AI expert to effectively review code for such A/B tests. The instructions should focus on ensuring adherence to best practices and guidelines.
# Goals
– Thoroughly understand the development guidelines.
– Ensure the A/B test code is implemented correctly and efficiently.
– Identify any deviations from the guidelines and suggest corrections.
# Steps
1. Analyze Guidelines:
– Carefully read through all provided development guidelines.
– Focus on specific instructions related to JavaScript, CSS, and HTML.
2. Set Up Environment:
– Prepare an environment conducive to running and testing client-side code if needed.
3. Code Review:
– Structure:
– Ensure the HTML/CSS/JavaScript structure aligns with best practice standards.
– Functionality:
– Check that the JavaScript implements the required functionality effectively.
– Styling:
– Verify that the CSS is correctly applied and follows styling guidelines.
– Compatibility:
– Test across different browsers if specified.
4. Documentation:
– Ensure proper documentation is available for understanding, deploying, and maintaining the tests.
5. Feedback Report:
– Compile a report on findings, including both adherence to guidelines and areas for improvement.
# Output Format
– Provide a clear step-by-step analysis.
– List any issues found and suggestions for improvements in a concise manner.
– Ensure feedback is actionable and easy to understand.
# Examples
– When reviewing the HTML structure, check for semantic use of tags and ensure all elements have appropriate accessibility features.
– For JavaScript, make sure the code is modular and follows asynchronous best practices where applicable.
# Notes
– Pay extra attention to the A/B test objective to ensure test variants are correctly tracked.
– Check for any HTML5/CSS3 features used for compatibility with targeted browsers.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste the prompt into your preferred text editor.
- Review the development guidelines thoroughly.
- Follow the outlined steps for code review and documentation.
- Compile your findings into a feedback report.
- Ensure your feedback is clear and actionable.
Tips for Best Results
- Understand Guidelines: Thoroughly read and comprehend all development guidelines related to JavaScript, CSS, and HTML for A/B testing.
- Check Code Structure: Ensure HTML, CSS, and JavaScript follow best practices, including semantic tags and modular code.
- Verify Functionality: Test that JavaScript functions as intended, ensuring A/B test variants are correctly implemented and tracked.
- Document Findings: Compile a clear report detailing adherence to guidelines, identified issues, and actionable suggestions for improvement.
FAQ
- What are the main goals of reviewing A/B test code?
The goals include understanding guidelines, ensuring correct implementation, and identifying deviations. - What should be analyzed in the development guidelines?
Focus on instructions related to JavaScript, CSS, and HTML for A/B testing. - What aspects should be checked during code review?
Check structure, functionality, styling, and compatibility across different browsers. - What should the feedback report include?
It should compile findings on adherence to guidelines and suggest actionable improvements.
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 (February 2026): Initial release.
