Skip to main content

Configuring Custom Instructions

Overview​

You can customize ExploreChimp's behavior by providing custom instructions for each data source analyzed. This allows you to guide the agent's analysis strategy, focus areas, and bug detection priorities for different aspects of your application.

Setting Custom Instructions​

  1. Navigate to Settings → Project Settings
  2. Click on the ExploreChimp tab
  3. Configure custom instructions for each data source you want to customize
  4. Click "Save Changes" at the top of the page to save your configuration

Data Source Configuration​

Custom instructions can be configured for each data source that ExploreChimp analyzes:

DOM Analysis​

Provide custom instructions for DOM structure and content analysis:

Focus on identifying broken links, missing form labels, and accessibility issues. 
Pay special attention to semantic HTML structure.

Network Analysis​

Configure network analysis with two options:

API Regex to Analyze: Specify a regular expression pattern to match API endpoints for analysis. Only API calls matching this pattern will be analyzed.

Example: ^https://api\.example\.com/.* - Analyzes all API calls to api.example.com

Custom Instructions: Provide specific instructions for network analysis:

Prioritize identifying slow API responses (>500ms) and failed requests. 
Focus on authentication endpoints and payment processing APIs.

Screenshot Analysis​

Configure screenshot analysis with two options:

Default Viewports: Select which viewport sizes to capture screenshots by default:

  • Desktop (Laptop): 1366x768
  • Wide-screen: 1920x1080 (paid plans)
  • Mobile: 375x812 (paid plans)
  • Tablet: 768x1024 (paid plans)

Custom Instructions: Provide specific instructions for visual analysis:

Focus on layout breakages, alignment issues, and visual polish problems. 
Check for scroll bars appearing in unexpected places.

Console Analysis​

Provide custom instructions for console log analysis:

Prioritize JavaScript errors and warnings. Ignore informational console logs.
Focus on errors that might impact user experience.

Metrics Analysis​

Provide custom instructions for performance metrics analysis:

Monitor for slow interactions, long tasks blocking the main thread, and janky animations.
Flag any performance degradation compared to baseline thresholds.

Note: Performance thresholds can be set via Atlas → SiteMap for specific screen-states.

Content Analysis​

Provide custom instructions for content analysis:

Identify ambiguous content, dangling template strings (e.g., {{variable}}), 
and grammar/spelling errors. Check for missing translations.

Best Practices​

  1. Be specific: Clear, specific instructions work better than vague ones
  2. Focus on outcomes: Describe what you want to achieve, not how to do it
  3. Use API regex strategically: Narrow down network analysis to relevant endpoints to save credits
  4. Select appropriate viewports: Choose viewports that match your user base and testing priorities
  5. Update regularly: Review and update instructions as your priorities change

Examples​

E-commerce Application​

Network Analysis:

  • API Regex: ^https://api\.shop\.com/(checkout|payment|cart)/.*
  • Instructions: "Focus on payment processing APIs. Flag any 4xx or 5xx errors."

Screenshot Analysis:

  • Default Viewports: Desktop, Mobile
  • Instructions: "Check for layout breakages in product listings and checkout flow."

Content Analysis:

  • Instructions: "Identify any template strings that weren't replaced, especially in product descriptions and pricing."

Accessibility-Focused Testing​

DOM Analysis:

  • Instructions: "Prioritize missing alt text, missing form labels, and improper heading hierarchy."

Screenshot Analysis:

  • Default Viewports: Desktop, Tablet, Mobile
  • Instructions: "Check for color contrast issues and responsive design problems."

Custom instructions give you fine-grained control over how ExploreChimp analyzes each data source and what it focuses on during explorations.