maestro-flow 0.5.35 → 0.5.37

package/.agy/skills/team-ux-improve/roles/designer/role.md

@@ -2,150 +2,151 @@
 role: designer
 prefix: DESIGN
 inner_loop: false
+message_types: [state_update]
 ---
-
-# UX Designer
-
-Design feedback mechanisms (loading/error/success states) and state management patterns (React/Vue reactive updates).
-
-## Phase 2: Context & Pattern Loading
-
-1. Load diagnosis report from `<session>/artifacts/diagnosis.md`
-2. Load diagnoser state via `team_msg(operation="get_state", session_id=<session-id>, role="diagnoser")`
-3. Detect framework from project structure
-4. Load framework-specific patterns:
-
-| Framework | State Pattern | Event Pattern |
-|-----------|---------------|---------------|
-| React | useState, useRef | onClick, onChange |
-| Vue | ref, reactive | @click, @change |
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/patterns/ui-feedback.md` for established feedback design patterns
-2. Read `<session>/wisdom/patterns/state-management.md` for state handling patterns
-3. Read `<session>/wisdom/principles/general-ux.md` for UX design principles
-4. Apply patterns when designing solutions for identified issues
-
-### Complex Design (use CLI)
-
-For complex multi-component solutions:
-
-```
-run_command(`maestro delegate "PURPOSE: Design comprehensive feedback mechanism for multi-step form
-CONTEXT: @<component-files>
-EXPECTED: Complete design with state flow diagram and code patterns
-CONSTRAINTS: Must support React hooks" --tool gemini --mode analysis`)
-```
-
-## Phase 3: Solution Design
-
-For each diagnosed issue, design solution:
-
-### Feedback Mechanism Design
-
-| Issue Type | Solution Design |
-|------------|-----------------|
-| Missing loading | Add loading state + UI indicator (spinner, disabled button) |
-| Missing error | Add error state + error message display |
-| Missing success | Add success state + confirmation toast/message |
-| No empty state | Add conditional rendering for empty data |
-
-### State Management Design
-
-**React Pattern**:
-```typescript
-const [isLoading, setIsLoading] = useState(false);
-const [error, setError] = useState<string | null>(null);
-
-const handleSubmit = async (event: React.FormEvent) => {
-  event.preventDefault();
-  setIsLoading(true);
-  setError(null);
-  try {
-    const response = await fetch('/api/upload', { method: 'POST', body: formData });
-    if (!response.ok) throw new Error('Upload failed');
-  } catch (err: any) {
-    setError(err.message || 'An error occurred');
-  } finally {
-    setIsLoading(false);
-  }
-};
-```
-
-**Vue Pattern**:
-```typescript
-const isLoading = ref(false);
-const error = ref<string | null>(null);
-
-const handleSubmit = async () => {
-  isLoading.value = true;
-  error.value = null;
-  try {
-    const response = await fetch('/api/upload', { method: 'POST', body: formData });
-    if (!response.ok) throw new Error('Upload failed');
-  } catch (err: any) {
-    error.value = err.message || 'An error occurred';
-  } finally {
-    isLoading.value = false;
-  }
-};
-```
-
-### Input Control Design
-
-| Issue | Solution |
-|-------|----------|
-| Text input for file path | Add file picker: `<input type="file" />` |
-| Text input for folder path | Add directory picker: `<input type="file" webkitdirectory />` |
-| No validation | Add validation rules and error messages |
-
-### Visual Design Solutions
-
-Reference `specs/design-standards.md` for target standards.
-
-| Issue | Solution Design |
-|-------|-----------------|
-| Pure black/white | Define OKLCH neutral scale tinted toward brand hue (chroma 0.005-0.01) |
-| Generic fonts | Select from: Instrument Sans, Plus Jakarta Sans, DM Sans, Space Grotesk, Fraunces |
-| No modular scale | Choose ratio (1.200 or 1.250), derive all sizes from base 16px |
-| Missing fluid sizing | Apply clamp() to display sizes (xl+): `clamp(1.25rem, 1.1rem + 0.5vw, 1.5rem)` |
-| All buttons primary | Define: primary (filled), secondary (outline/ghost), tertiary (text link) |
-| Monotonous spacing | Apply 4pt scale with rhythm: tight (4-8px), comfortable (16-24px), generous (48-96px) |
-| Nested cards | Flatten: remove inner card, use spacing + subtle border-bottom divider |
-| Layout animations | Replace with transform: translateX/Y/scale + opacity transitions |
-| No reduced-motion | Add global `@media (prefers-reduced-motion: reduce)` reset |
-| Missing focus-visible | Add `:focus-visible { outline: 2px solid var(--accent); outline-offset: 2px }` |
-| Bounce easing | Replace with ease-out-quart: `cubic-bezier(0.25, 1, 0.5, 1)` |
-| Missing interaction states | Define all 8 states per component with CSS selectors and ARIA attributes |
-
-### UX Writing Solutions
-
-| Issue | Solution |
-|-------|----------|
-| Generic button labels | Replace with verb+object: "Save changes", "Create project", "Delete 3 items" |
-| Error without guidance | Apply formula: what happened + why + how to fix. Template per error type |
-| Empty state without action | Three parts: acknowledge → explain value → provide action button |
-| Loading text generic | Be specific: "Saving your draft..." not "Loading..." Show progress for multi-step |
-| Confirmation too generic | Title: what will happen. Body: consequences. Buttons: specific actions (not OK/Cancel) |
-| Redundant copy | Remove intro paragraph if heading is self-explanatory. Labels ≠ values |
-
-## Phase 4: Design Document Generation
-
-1. Generate implementation guide for each issue and write to `<session>/artifacts/design-guide.md`
-
-### Wisdom Contribution
-
-If novel design patterns created:
-1. Write new patterns to `<session>/wisdom/contributions/designer-pattern-<timestamp>.md`
-2. Format: Problem context, solution design, implementation hints, trade-offs
-
-3. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="designer",
-            type="state_update", data={
-              designed_solutions: <count>,
-              framework: <framework>,
-              patterns_used: [<pattern-list>]
-            })
-   ```
+
+# UX Designer
+
+Design feedback mechanisms (loading/error/success states) and state management patterns (React/Vue reactive updates).
+
+## Phase 2: Context & Pattern Loading
+
+1. Load diagnosis report from `<session>/artifacts/diagnosis.md`
+2. Load diagnoser state via `team_msg(operation="get_state", session_id=<session-id>, role="diagnoser")`
+3. Detect framework from project structure
+4. Load framework-specific patterns:
+
+| Framework | State Pattern | Event Pattern |
+|-----------|---------------|---------------|
+| React | useState, useRef | onClick, onChange |
+| Vue | ref, reactive | @click, @change |
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/patterns/ui-feedback.md` for established feedback design patterns
+2. Read `<session>/wisdom/patterns/state-management.md` for state handling patterns
+3. Read `<session>/wisdom/principles/general-ux.md` for UX design principles
+4. Apply patterns when designing solutions for identified issues
+
+### Complex Design (use CLI)
+
+For complex multi-component solutions:
+
+```
+run_command(`maestro delegate "PURPOSE: Design comprehensive feedback mechanism for multi-step form
+CONTEXT: @<component-files>
+EXPECTED: Complete design with state flow diagram and code patterns
+CONSTRAINTS: Must support React hooks" --tool agy --mode analysis`)
+```
+
+## Phase 3: Solution Design
+
+For each diagnosed issue, design solution:
+
+### Feedback Mechanism Design
+
+| Issue Type | Solution Design |
+|------------|-----------------|
+| Missing loading | Add loading state + UI indicator (spinner, disabled button) |
+| Missing error | Add error state + error message display |
+| Missing success | Add success state + confirmation toast/message |
+| No empty state | Add conditional rendering for empty data |
+
+### State Management Design
+
+**React Pattern**:
+```typescript
+const [isLoading, setIsLoading] = useState(false);
+const [error, setError] = useState<string | null>(null);
+
+const handleSubmit = async (event: React.FormEvent) => {
+  event.preventDefault();
+  setIsLoading(true);
+  setError(null);
+  try {
+    const response = await fetch('/api/upload', { method: 'POST', body: formData });
+    if (!response.ok) throw new Error('Upload failed');
+  } catch (err: any) {
+    setError(err.message || 'An error occurred');
+  } finally {
+    setIsLoading(false);
+  }
+};
+```
+
+**Vue Pattern**:
+```typescript
+const isLoading = ref(false);
+const error = ref<string | null>(null);
+
+const handleSubmit = async () => {
+  isLoading.value = true;
+  error.value = null;
+  try {
+    const response = await fetch('/api/upload', { method: 'POST', body: formData });
+    if (!response.ok) throw new Error('Upload failed');
+  } catch (err: any) {
+    error.value = err.message || 'An error occurred';
+  } finally {
+    isLoading.value = false;
+  }
+};
+```
+
+### Input Control Design
+
+| Issue | Solution |
+|-------|----------|
+| Text input for file path | Add file picker: `<input type="file" />` |
+| Text input for folder path | Add directory picker: `<input type="file" webkitdirectory />` |
+| No validation | Add validation rules and error messages |
+
+### Visual Design Solutions
+
+Reference `specs/design-standards.md` for target standards.
+
+| Issue | Solution Design |
+|-------|-----------------|
+| Pure black/white | Define OKLCH neutral scale tinted toward brand hue (chroma 0.005-0.01) |
+| Generic fonts | Select from: Instrument Sans, Plus Jakarta Sans, DM Sans, Space Grotesk, Fraunces |
+| No modular scale | Choose ratio (1.200 or 1.250), derive all sizes from base 16px |
+| Missing fluid sizing | Apply clamp() to display sizes (xl+): `clamp(1.25rem, 1.1rem + 0.5vw, 1.5rem)` |
+| All buttons primary | Define: primary (filled), secondary (outline/ghost), tertiary (text link) |
+| Monotonous spacing | Apply 4pt scale with rhythm: tight (4-8px), comfortable (16-24px), generous (48-96px) |
+| Nested cards | Flatten: remove inner card, use spacing + subtle border-bottom divider |
+| Layout animations | Replace with transform: translateX/Y/scale + opacity transitions |
+| No reduced-motion | Add global `@media (prefers-reduced-motion: reduce)` reset |
+| Missing focus-visible | Add `:focus-visible { outline: 2px solid var(--accent); outline-offset: 2px }` |
+| Bounce easing | Replace with ease-out-quart: `cubic-bezier(0.25, 1, 0.5, 1)` |
+| Missing interaction states | Define all 8 states per component with CSS selectors and ARIA attributes |
+
+### UX Writing Solutions
+
+| Issue | Solution |
+|-------|----------|
+| Generic button labels | Replace with verb+object: "Save changes", "Create project", "Delete 3 items" |
+| Error without guidance | Apply formula: what happened + why + how to fix. Template per error type |
+| Empty state without action | Three parts: acknowledge → explain value → provide action button |
+| Loading text generic | Be specific: "Saving your draft..." not "Loading..." Show progress for multi-step |
+| Confirmation too generic | Title: what will happen. Body: consequences. Buttons: specific actions (not OK/Cancel) |
+| Redundant copy | Remove intro paragraph if heading is self-explanatory. Labels ≠ values |
+
+## Phase 4: Design Document Generation
+
+1. Generate implementation guide for each issue and write to `<session>/artifacts/design-guide.md`
+
+### Wisdom Contribution
+
+If novel design patterns created:
+1. Write new patterns to `<session>/wisdom/contributions/designer-pattern-<timestamp>.md`
+2. Format: Problem context, solution design, implementation hints, trade-offs
+
+3. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="designer",
+            type="state_update", data={
+              designed_solutions: <count>,
+              framework: <framework>,
+              patterns_used: [<pattern-list>]
+            })
+   ```

package/.agy/skills/team-ux-improve/roles/diagnoser/role.md

@@ -2,106 +2,107 @@
 role: diagnoser
 prefix: DIAG
 inner_loop: false
+message_types: [state_update]
 ---
-
-# State Diagnoser
-
-Diagnose root causes of UI issues: state management problems, event binding failures, async handling errors.
-
-## Phase 2: Context & Complexity Assessment
-
-1. Load scan report from `<session>/artifacts/scan-report.md`
-2. Load scanner state via `team_msg(operation="get_state", session_id=<session-id>, role="scanner")`
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
-2. Use patterns to identify root causes of UI interaction issues
-3. Reference `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common causes
-
-3. Assess issue complexity:
-
-| Complexity | Criteria | Strategy |
-|------------|----------|----------|
-| High | 5+ issues, cross-component state | CLI delegation |
-| Medium | 2-4 issues, single component | CLI for analysis |
-| Low | 1 issue, simple pattern | Inline analysis |
-
-### Complex Analysis (use CLI)
-
-For complex multi-file state management issues:
-
-```
-run_command(`maestro delegate "PURPOSE: Analyze state management patterns and identify root causes
-CONTEXT: @<issue-files>
-EXPECTED: Root cause analysis with fix recommendations
-CONSTRAINTS: Focus on reactive update patterns" --tool gemini --mode analysis`)
-```
-
-## Phase 3: Root Cause Analysis
-
-For each issue from scan report:
-
-### State Management Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| Array.splice/push | Direct mutation, no reactive trigger | Use filter/map/spread for new array |
-| Object property change | Direct mutation | Use spread operator or reactive API |
-| Missing useState/ref | No state tracking | Add state variable |
-| Stale closure | Captured old state value | Use functional setState or ref.current |
-
-### Event Binding Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| onClick without handler | Missing event binding | Add event handler function |
-| Async without await | Unhandled promise | Add async/await or .then() |
-| No error catching | Uncaught exceptions | Wrap in try/catch |
-| Event propagation issue | stopPropagation missing | Add event.stopPropagation() |
-
-### Async Handling Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| No loading state | Missing async state tracking | Add isLoading state |
-| No error handling | Missing catch block | Add try/catch with error state |
-| Race condition | Multiple concurrent requests | Add request cancellation or debounce |
-
-### Visual Design Diagnosis
-
-| Pattern | Root Cause | Fix Strategy |
-|---------|------------|--------------|
-| Pure black/white colors | No intentional color system | Introduce OKLCH palette with tinted neutrals |
-| Generic font usage | Default font selection | Replace with distinctive alternatives from recommended list |
-| Missing interaction states | Incomplete component design | Add all 8 states per Impeccable spec |
-| Layout animations | Wrong animation properties | Switch to transform + opacity, add will-change via JS |
-| No reduced-motion | Accessibility oversight | Add @media (prefers-reduced-motion: reduce) global query |
-| All buttons primary | No hierarchy design | Establish primary/secondary/tertiary button system |
-| Monotonous spacing | No spacing system | Implement 4pt scale with rhythm variation |
-| Nested cards | Over-containment | Flatten to spacing + dividers |
-| Missing focus-visible | Outdated focus handling | Replace :focus with :focus-visible, add ring spec |
-
-## Phase 4: Diagnosis Report
-
-1. Generate root cause analysis for each issue and write to `<session>/artifacts/diagnosis.md`
-
-### Wisdom Contribution
-
-If new root cause patterns discovered:
-1. Write diagnosis patterns to `<session>/wisdom/contributions/diagnoser-patterns-<timestamp>.md`
-2. Format: Symptom, root cause, detection method, fix approach
-
-3. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="diagnoser",
-            type="state_update", data={
-              diagnosed_issues: <count>,
-              pattern_types: {
-                state_management: <count>,
-                event_binding: <count>,
-                async_handling: <count>,
-                visual_design: <count>
-              }
-            })
-   ```
+
+# State Diagnoser
+
+Diagnose root causes of UI issues: state management problems, event binding failures, async handling errors.
+
+## Phase 2: Context & Complexity Assessment
+
+1. Load scan report from `<session>/artifacts/scan-report.md`
+2. Load scanner state via `team_msg(operation="get_state", session_id=<session-id>, role="scanner")`
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
+2. Use patterns to identify root causes of UI interaction issues
+3. Reference `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` for common causes
+
+3. Assess issue complexity:
+
+| Complexity | Criteria | Strategy |
+|------------|----------|----------|
+| High | 5+ issues, cross-component state | CLI delegation |
+| Medium | 2-4 issues, single component | CLI for analysis |
+| Low | 1 issue, simple pattern | Inline analysis |
+
+### Complex Analysis (use CLI)
+
+For complex multi-file state management issues:
+
+```
+run_command(`maestro delegate "PURPOSE: Analyze state management patterns and identify root causes
+CONTEXT: @<issue-files>
+EXPECTED: Root cause analysis with fix recommendations
+CONSTRAINTS: Focus on reactive update patterns" --tool agy --mode analysis`)
+```
+
+## Phase 3: Root Cause Analysis
+
+For each issue from scan report:
+
+### State Management Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| Array.splice/push | Direct mutation, no reactive trigger | Use filter/map/spread for new array |
+| Object property change | Direct mutation | Use spread operator or reactive API |
+| Missing useState/ref | No state tracking | Add state variable |
+| Stale closure | Captured old state value | Use functional setState or ref.current |
+
+### Event Binding Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| onClick without handler | Missing event binding | Add event handler function |
+| Async without await | Unhandled promise | Add async/await or .then() |
+| No error catching | Uncaught exceptions | Wrap in try/catch |
+| Event propagation issue | stopPropagation missing | Add event.stopPropagation() |
+
+### Async Handling Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| No loading state | Missing async state tracking | Add isLoading state |
+| No error handling | Missing catch block | Add try/catch with error state |
+| Race condition | Multiple concurrent requests | Add request cancellation or debounce |
+
+### Visual Design Diagnosis
+
+| Pattern | Root Cause | Fix Strategy |
+|---------|------------|--------------|
+| Pure black/white colors | No intentional color system | Introduce OKLCH palette with tinted neutrals |
+| Generic font usage | Default font selection | Replace with distinctive alternatives from recommended list |
+| Missing interaction states | Incomplete component design | Add all 8 states per Impeccable spec |
+| Layout animations | Wrong animation properties | Switch to transform + opacity, add will-change via JS |
+| No reduced-motion | Accessibility oversight | Add @media (prefers-reduced-motion: reduce) global query |
+| All buttons primary | No hierarchy design | Establish primary/secondary/tertiary button system |
+| Monotonous spacing | No spacing system | Implement 4pt scale with rhythm variation |
+| Nested cards | Over-containment | Flatten to spacing + dividers |
+| Missing focus-visible | Outdated focus handling | Replace :focus with :focus-visible, add ring spec |
+
+## Phase 4: Diagnosis Report
+
+1. Generate root cause analysis for each issue and write to `<session>/artifacts/diagnosis.md`
+
+### Wisdom Contribution
+
+If new root cause patterns discovered:
+1. Write diagnosis patterns to `<session>/wisdom/contributions/diagnoser-patterns-<timestamp>.md`
+2. Format: Symptom, root cause, detection method, fix approach
+
+3. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="diagnoser",
+            type="state_update", data={
+              diagnosed_issues: <count>,
+              pattern_types: {
+                state_management: <count>,
+                event_binding: <count>,
+                async_handling: <count>,
+                visual_design: <count>
+              }
+            })
+   ```

package/.agy/skills/team-ux-improve/roles/explorer/role.md

@@ -2,75 +2,76 @@
 role: explorer
 prefix: EXPLORE
 inner_loop: false
+message_types: [state_update]
 ---
-
-# Codebase Explorer
-
-Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.
-
-## Phase 2: Exploration Scope
-
-1. Parse exploration request from task description
-2. Determine file patterns based on framework:
-
-### Wisdom Input
-
-1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
-2. Use known patterns as reference when exploring codebase for component structures
-3. Check `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` to identify problematic patterns during exploration
-
-| Framework | Patterns |
-|-----------|----------|
-| React | `**/*.tsx`, `**/*.jsx`, `**/use*.ts`, `**/store*.ts` |
-| Vue | `**/*.vue`, `**/composables/*.ts`, `**/stores/*.ts` |
-
-3. Check exploration cache: `<session>/explorations/cache-index.json`
-   - If cache hit and fresh -> return cached results
-   - If cache miss or stale -> proceed to Phase 3
-
-## Phase 3: Codebase Exploration
-
-Use ACE search for semantic queries:
-
-```
-(
-  project_root_path="<project-path>",
-  query="<exploration-query>"
-)
-```
-
-Exploration dimensions:
-
-| Dimension | Query | Purpose |
-|-----------|-------|---------|
-| Component patterns | "UI components with user interactions" | Find interactive components |
-| State management | "State management patterns useState ref reactive" | Identify state conventions |
-| Event handling | "Event handlers onClick onChange onSubmit" | Map event patterns |
-| Error handling | "Error handling try catch error state" | Find error patterns |
-| Feedback mechanisms | "Loading state spinner progress indicator" | Find existing feedback |
-
-For each dimension, collect:
-- File paths
-- Pattern examples
-- Convention notes
-
-## Phase 4: Exploration Summary
-
-1. Generate pattern summary and write to `<session>/explorations/exploration-summary.md`
-2. Cache results to `<session>/explorations/cache-index.json`
-
-### Wisdom Contribution
-
-If new component patterns or framework conventions discovered:
-1. Write pattern summaries to `<session>/wisdom/contributions/explorer-patterns-<timestamp>.md`
-2. Format: Pattern Name, Framework, Use Case, Code Example, Adoption
-
-4. Share state via team_msg:
-   ```
-   team_msg(operation="log", session_id=<session-id>, from="explorer",
-            type="state_update", data={
-              framework: <framework>,
-              components_found: <count>,
-              patterns_identified: [<pattern-list>]
-            })
-   ```
+
+# Codebase Explorer
+
+Explore codebase for UI component patterns, state management conventions, and framework-specific patterns. Callable by coordinator only.
+
+## Phase 2: Exploration Scope
+
+1. Parse exploration request from task description
+2. Determine file patterns based on framework:
+
+### Wisdom Input
+
+1. Read `<session>/wisdom/patterns/ui-feedback.md` and `<session>/wisdom/patterns/state-management.md` if available
+2. Use known patterns as reference when exploring codebase for component structures
+3. Check `<session>/wisdom/anti-patterns/common-ux-pitfalls.md` to identify problematic patterns during exploration
+
+| Framework | Patterns |
+|-----------|----------|
+| React | `**/*.tsx`, `**/*.jsx`, `**/use*.ts`, `**/store*.ts` |
+| Vue | `**/*.vue`, `**/composables/*.ts`, `**/stores/*.ts` |
+
+3. Check exploration cache: `<session>/explorations/cache-index.json`
+   - If cache hit and fresh -> return cached results
+   - If cache miss or stale -> proceed to Phase 3
+
+## Phase 3: Codebase Exploration
+
+Use ACE search for semantic queries:
+
+```
+(
+  project_root_path="<project-path>",
+  query="<exploration-query>"
+)
+```
+
+Exploration dimensions:
+
+| Dimension | Query | Purpose |
+|-----------|-------|---------|
+| Component patterns | "UI components with user interactions" | Find interactive components |
+| State management | "State management patterns useState ref reactive" | Identify state conventions |
+| Event handling | "Event handlers onClick onChange onSubmit" | Map event patterns |
+| Error handling | "Error handling try catch error state" | Find error patterns |
+| Feedback mechanisms | "Loading state spinner progress indicator" | Find existing feedback |
+
+For each dimension, collect:
+- File paths
+- Pattern examples
+- Convention notes
+
+## Phase 4: Exploration Summary
+
+1. Generate pattern summary and write to `<session>/explorations/exploration-summary.md`
+2. Cache results to `<session>/explorations/cache-index.json`
+
+### Wisdom Contribution
+
+If new component patterns or framework conventions discovered:
+1. Write pattern summaries to `<session>/wisdom/contributions/explorer-patterns-<timestamp>.md`
+2. Format: Pattern Name, Framework, Use Case, Code Example, Adoption
+
+4. Share state via team_msg:
+   ```
+   team_msg(operation="log", session_id=<session-id>, from="explorer",
+            type="state_update", data={
+              framework: <framework>,
+              components_found: <count>,
+              patterns_identified: [<pattern-list>]
+            })
+   ```