feat: add E-Commerce Engineer agent

[itlasso]

What does this PR do?

Adds a new E-Commerce Engineer agent to the Engineering Division, specializing in Shopify, WooCommerce, and Drupal Commerce storefront development, custom checkout flows, and payment gateway integration.

Agent Information (if adding/modifying an agent)

• Agent Name: E-Commerce Engineer
• Category: Engineering
• Specialty: Shopify Liquid theme development, WooCommerce custom product types and checkout, Drupal Commerce order processors and payment gateways, Stripe/PayPal/Klarna integration, product catalog architecture, and e-commerce performance optimization

Checklist

• Follows the agent template structure from CONTRIBUTING.md
• Includes YAML frontmatter with name, description, color
• Has concrete code/template examples (for new agents)
• Tested in real scenarios
• Proofread and formatted correctly

[mhc222]

Code Review

1 issue found.

---

Issue 1 — Section headers don't match required template format (score: 100)

The file has the right content areas but uses non-standard heading text throughout. The convert.sh script matches section headers exactly to split agents into tool-specific formats. Non-matching headers cause conversion to fail silently.

Required section	Actual heading
## 🧠 Your Identity & Memory	## Identity & Memory
## 🎯 Your Core Mission	## Core Mission
## 🚨 Critical Rules You Must Follow	## Critical Rules
## 📋 Your Technical Deliverables	## Technical Deliverables
## 🔄 Your Workflow Process	## Workflow Process
## 💭 Your Communication Style	## Communication Style
## 🔄 Learning & Memory	❌ Missing entirely
## 🎯 Your Success Metrics	## Success Metrics
## 🚀 Advanced Capabilities	❌ Missing (has ## When to Bring In Other Agents instead)

Each heading needs the correct emoji prefix and the full Your phrasing as shown in the CONTRIBUTING.md template (§ Agent File Structure).

---

Reviewed by Code Reviewer agent. Issues are only reported at confidence ≥80/100.

[itlasso]

@mhc222 Good catch — thanks for flagging this.

You're correct that the section headers must match the exact template format for convert.sh to properly parse and split the agent definition. I’ve updated all headings to include the required emoji prefixes and standardized “Your …” phrasing per CONTRIBUTING.md.

Also added the missing sections:

• Learning & Memory
• Advanced Capabilities

Everything should now align with the expected structure and support the conversion pipeline correctly.