expxagents 0.10.2 → 0.10.4

package/assets/core/solution-architect.agent.md

@@ -57,6 +57,11 @@ squad:
   preferences: "_expxagents/_memory/preferences.md"
   memory: "_memory/memories.md"
 
+  # For squads that produce visual output, include these references:
+  design_system: "squads/design-system/_memory/design-tokens.md"
+  brand_guidelines: "squads/design-system/_memory/brand-guidelines.md"
+  assets_path: "_expxagents/_assets/"
+
   target_audience: <from discovery>
   platform: <target platform>
   format: <maps to best-practices file>
@@ -163,6 +168,14 @@ writer,"Carlos Writer",pencil,"Creative and precise, crafts compelling content"
 
 Create `_memory/memories.md` for squad-level learning.
 
+## Design System Integration
+
+**For any squad that produces visual output** (landing pages, social media, emails, presentations, ads, banners):
+
+1. **ALWAYS include** `design_system`, `brand_guidelines`, and `assets_path` in squad.yaml
+2. **Agent instructions** must include: "Before producing any visual output, read `squads/design-system/_memory/design-tokens.md` for colors, fonts, and spacing. Read `squads/design-system/_memory/brand-guidelines.md` for brand rules. Use assets from `_expxagents/_assets/` for logos and images."
+3. The first step of visual squads should always reference the design system tokens
+
 ## Validation Checklist
 
 Before presenting the design to the user:
@@ -173,6 +186,7 @@ Before presenting the design to the user:
 - [ ] Agent prompts have clear input/output contracts
 - [ ] Pipeline flows logically from research → creation → review
 - [ ] Format matches an available best-practice (if platform specified)
+- [ ] Visual squads reference design system and assets path
 
 ## After Design
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expxagents",
-  "version": "0.10.2",
+  "version": "0.10.4",
   "description": "Multi-agent orchestration platform for AI squads",
   "author": "ExpxAgents",
   "license": "MIT",