Best Practices

Recommended workflows, optimization strategies, and expert tips for getting the most out of PeerScripts.

---

General Principles

1. Be Proactive, Not Reactive

Don't wait for problems to find you:

• Schedule regular scans - Weekly at minimum
• Set up alerts - Get notified before issues escalate
• Monitor trends - Catch regressions early
• Review changes - Know what's happening in your store

2. Prioritize by Impact

Focus on what matters most:

Priority	Criteria	Examples
Critical	Security risk or revenue loss	XSS vulnerabilities, broken checkout
High	Significant customer impact	Slow pages, broken navigation
Medium	Best practice violations	Missing meta tags, deprecated code
Low	Minor improvements	Code cleanup, optimization

3. Track Everything

Use the ticket system for accountability:

• Create tickets for all significant issues
• Assign clear ownership
• Set realistic due dates
• Document resolutions

4. Measure and Iterate

Continuously improve:

• Track metrics over time
• Compare periods to see progress
• Celebrate wins and learn from misses
• Adjust processes based on data

---

Feature-Specific Best Practices

Theme Intelligence

Scanning Frequency

Scenario	Frequency
Active development	After each significant change
Stable theme	Weekly
Before deployments	Always
After theme updates	Immediately

Issue Management

1. Address critical and high issues immediately
2. Group similar issues for efficient fixes
3. Use "Ignore" sparingly and document why
4. Re-scan after making changes

Code Quality

• Follow Shopify's theme guidelines
• Use semantic HTML
• Keep Liquid logic simple
• Comment complex code sections

---

Quality Audits

SEO Optimization

• Every page needs unique meta title (50-60 chars)
• Every page needs unique meta description (120-160 chars)
• All images need descriptive alt text
• Use proper heading hierarchy (H1 → H2 → H3)

Content Quality

• Review before publishing (catch spelling errors)
• Remove all placeholder content
• Aim for 300+ words on key pages
• Use unique, original content

Accessibility

• Add labels to all form inputs
• Ensure sufficient color contrast
• Provide text alternatives for images
• Use semantic HTML elements

---

Lighthouse Performance

Target Scores

Metric	Good	Needs Work
Performance	90+	< 50
LCP	< 2.5s	> 4s
CLS	< 0.1	> 0.25
INP	< 200ms	> 500ms

Quick Wins

1. Compress and properly size images
2. Defer non-critical JavaScript
3. Preload key resources (fonts, hero images)
4. Enable lazy loading for off-screen content
5. Use modern image formats (WebP, AVIF)

Testing Approach

• Test both mobile and desktop
• Run multiple scans for consistent baselines
• Test key pages (home, product, collection)
• Re-test after optimizations

---

Catalog Intelligence

Catalog Hygiene

• Complete all product data fields
• Use high-quality product images
• Set accurate weights for shipping
• Maintain consistent pricing

Inventory Management

• Monitor top seller stock levels
• Set reorder points for key items
• Balance inventory across locations
• Track stockout frequency

Fulfillment Optimization

• Minimize order splits
• Review carrier performance regularly
• Set realistic delivery estimates
• Track and address return reasons

---

Discount Intelligence

Discount Code Hygiene

Practice	Why
Set end dates	Prevent forgotten active codes
Use unique codes	Enable tracking and attribution
Set usage limits	Prevent abuse
Regular cleanup	Remove old/unused codes

Preventing Revenue Leaks

1. Limit public/generic codes
2. Monitor for unusual usage patterns
3. Restrict discount stacking
4. Review findings weekly

Effective Promotions

• Track ROI for each discount
• Segment customers with targeted codes
• A/B test discount amounts
• Set clear objectives before launching

---

Store Health

Baseline Period

• Allow 7 full days for accurate baselines
• Avoid major changes during baseline
• Mark known special events for exclusion

Responding to Anomalies

1. Don't panic - review the data first
2. Check correlations - what changed?
3. Use AI analysis for insights
4. Create tickets to track investigation
5. Document resolution for future reference

Maintaining Healthy Baselines

• Keep operations consistent
• Mark sales events as special
• Review and adjust thresholds periodically

---

Tickets & Sprints

Effective Tickets

• Clear, specific titles
• Detailed descriptions with context
• Proper priority assignment
• Realistic time estimates
• Single responsibility (one task per ticket)

Sprint Planning

Guideline	Recommendation
Capacity	Don't overcommit (70-80% of available time)
Buffer	Leave room for unexpected work
Priority	High-priority items first
Size	Break large tasks into smaller ones

Daily Practices

• Update ticket status promptly
• Add notes for context
• Log time consistently
• Move blockers to team attention

---

Action Center

Before Executing

1. Always preview first
2. Review every item in the preview
3. Start small - test with subset
4. Execute during low-traffic periods
5. Document the action and why

During Execution

1. Monitor progress actively
2. Be ready to cancel if needed
3. Don't leave until complete

After Execution

1. Verify results with spot checks
2. Handle any failures immediately
3. Update related tickets
4. Keep rollback info until verified

---

AI Features

Getting Good Results

• Be specific in your questions
• Provide context when asking
• Ask one question at a time
• Follow up for deeper understanding

Code Editor AI

• Select relevant code before asking
• Ask about specific behaviors
• Request explanations, not just fixes
• Review suggestions before applying

Explanation Engine

• Reference specific IDs, dates, or metrics
• Ask "why" questions
• Use follow-up questions to dig deeper
• Create tickets from recommendations

---

Workflow Templates

New Store Setup

1. Day 1: Install and initial sync
2. Day 2: Run all initial scans
3. Day 3-7: Monitor baseline building
4. Day 8: Review first alerts
5. Week 2: Set up scheduled scans
6. Week 3: Configure team access
7. Month 1: Establish regular review cadence

Pre-Launch Checklist

• Theme Intelligence scan (all clear on critical/high)
• Quality audit (90+ score)
• Lighthouse mobile (70+ performance)
• Catalog detection (no critical issues)
• Discount codes reviewed
• Team access configured

Monthly Health Check

1. Run fresh scans across all systems
2. Compare metrics to previous month
3. Review and close stale tickets
4. Check for new team training needs
5. Update documentation if processes changed

---

Common Mistakes to Avoid

Over-Optimization

• Don't fix every low-priority issue
• Focus on high-impact changes first
• Avoid premature optimization
• Keep solutions simple

Ignoring Alerts

• Don't dismiss alerts without investigation
• False positives should be properly ignored
• Set appropriate thresholds
• Review ignored issues periodically

Skipping Previews

• Always preview bulk actions
• Review item lists before executing
• Test with small batches first
• Verify results after execution

Poor Documentation

• Document why issues were ignored
• Note resolutions on tickets
• Keep team informed of changes
• Maintain runbooks for common scenarios

---

Team Collaboration

Roles and Responsibilities

Role	Responsibilities
Owner	Overall strategy, billing, access control
Admin	Day-to-day management, issue triage
Editor	Fix issues, update content
Viewer	Monitor, report issues

Communication

• Use ticket notes for async discussion
• Tag team members on relevant issues
• Share weekly summaries
• Celebrate completed sprints

Handoffs

• Document context when reassigning
• Ensure tickets have sufficient detail
• Update status promptly
• Follow up on blocked items

---

Continuous Improvement

Track These Metrics

Metric	Target	Review Frequency
Theme health score	85+	Weekly
Quality score	90+	Weekly
Lighthouse performance	70+	Monthly
Open critical issues	0	Daily
Ticket velocity	Improving	Sprint

Retrospectives

After each sprint:

1. What went well?
2. What could improve?
3. What will we do differently?
4. What help do we need?

Staying Current

• Watch for new PeerScripts features
• Review Shopify platform updates
• Monitor industry best practices
• Share learnings with team