mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-07 16:41:06 +08:00
3d92478772
- Added role specifications for explorer, implementer, scanner, tester, and diagnoser. - Created dispatch and monitor commands for orchestrating task execution. - Defined team configuration for the UX improvement pipeline, including roles and responsibilities. - Established structured task descriptions for scanning, diagnosing, designing, implementing, and testing UI components. - Introduced caching mechanisms for exploration results and context accumulation for implementer tasks. - Enhanced error handling and validation processes across roles.
92 lines
2.4 KiB
Markdown
92 lines
2.4 KiB
Markdown
---
|
|
prefix: EXPLORE
|
|
inner_loop: false
|
|
message_types:
|
|
success: explore_complete
|
|
error: error
|
|
---
|
|
|
|
# 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:
|
|
|
|
| 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:
|
|
|
|
```
|
|
mcp__ace-tool__search_context(
|
|
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:
|
|
|
|
```markdown
|
|
# Exploration Summary
|
|
|
|
## Framework: React/Vue
|
|
|
|
## Component Patterns
|
|
- Button components use <pattern>
|
|
- Form components use <pattern>
|
|
|
|
## State Management Conventions
|
|
- Global state: Zustand/Pinia
|
|
- Local state: useState/ref
|
|
- Async state: custom hooks/composables
|
|
|
|
## Event Handling Patterns
|
|
- Form submit: <pattern>
|
|
- Button click: <pattern>
|
|
|
|
## Existing Feedback Mechanisms
|
|
- Loading: <pattern>
|
|
- Error: <pattern>
|
|
- Success: <pattern>
|
|
```
|
|
|
|
2. Cache results to `<session>/explorations/cache-index.json`
|
|
3. Write summary to `<session>/explorations/exploration-summary.md`
|
|
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>]
|
|
})
|
|
```
|