mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-03 15:43:11 +08:00
57636040d2
- Updated phase references in SKILL.md and 01-lite-plan.md to use "LP-Phase" prefix for consistency. - Added critical context isolation note in 01-lite-plan.md to clarify phase invocation rules. - Enhanced execution process descriptions to reflect updated phase naming conventions. Improve error handling in frontend routing - Introduced ChunkErrorBoundary component to handle lazy-loaded chunk load failures. - Wrapped lazy-loaded routes with error boundary and suspense for better user experience. - Created PageSkeleton component for loading states in lazy-loaded routes. Sanitize header values in notification routes - Added regex validation for header values to prevent XSS attacks by allowing only printable ASCII characters. Enhance mobile responsiveness in documentation styles - Updated CSS breakpoints to use custom properties for better maintainability. - Improved layout styles across various components to ensure consistent behavior on mobile devices.
115 lines
4.1 KiB
Markdown
115 lines
4.1 KiB
Markdown
---
|
|
prefix: STRATEGY
|
|
inner_loop: false
|
|
discuss_rounds: [DISCUSS-OPT]
|
|
subagents: [discuss]
|
|
message_types:
|
|
success: strategy_complete
|
|
error: error
|
|
---
|
|
|
|
# Optimization Strategist
|
|
|
|
Analyze bottleneck reports and baseline metrics to design a prioritized optimization plan with concrete strategies, expected improvements, and risk assessments.
|
|
|
|
## Phase 2: Analysis Loading
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Bottleneck report | <session>/artifacts/bottleneck-report.md | Yes |
|
|
| Baseline metrics | <session>/artifacts/baseline-metrics.json | Yes |
|
|
| shared-memory.json | <session>/wisdom/shared-memory.json | Yes |
|
|
| Wisdom files | <session>/wisdom/patterns.md | No |
|
|
|
|
1. Extract session path from task description
|
|
2. Read bottleneck report -- extract ranked bottleneck list with severities
|
|
3. Read baseline metrics -- extract current performance numbers
|
|
4. Load shared-memory.json for profiler findings (project_type, scope)
|
|
5. Assess overall optimization complexity:
|
|
|
|
| Bottleneck Count | Severity Mix | Complexity |
|
|
|-----------------|-------------|------------|
|
|
| 1-2 | All Medium | Low |
|
|
| 2-3 | Mix of High/Medium | Medium |
|
|
| 3+ or any Critical | Any Critical present | High |
|
|
|
|
## Phase 3: Strategy Formulation
|
|
|
|
For each bottleneck, select optimization approach by type:
|
|
|
|
| Bottleneck Type | Strategies | Risk Level |
|
|
|----------------|-----------|------------|
|
|
| CPU hotspot | Algorithm optimization, memoization, caching, worker threads | Medium |
|
|
| Memory leak/bloat | Pool reuse, lazy initialization, WeakRef, scope cleanup | High |
|
|
| I/O bound | Batching, async pipelines, streaming, connection pooling | Medium |
|
|
| Network latency | Request coalescing, compression, CDN, prefetching | Low |
|
|
| Rendering | Virtualization, memoization, CSS containment, code splitting | Medium |
|
|
| Database | Index optimization, query rewriting, caching layer, denormalization | High |
|
|
|
|
Prioritize optimizations by impact/effort ratio:
|
|
|
|
| Priority | Criteria |
|
|
|----------|----------|
|
|
| P0 (Critical) | High impact + Low effort -- quick wins |
|
|
| P1 (High) | High impact + Medium effort |
|
|
| P2 (Medium) | Medium impact + Low effort |
|
|
| P3 (Low) | Low impact or High effort -- defer |
|
|
|
|
If complexity is High, invoke `discuss` subagent (DISCUSS-OPT round) to evaluate trade-offs between competing strategies before finalizing the plan.
|
|
|
|
Define measurable success criteria per optimization (target metric value or improvement %).
|
|
|
|
## Phase 4: Plan Output
|
|
|
|
1. Write optimization plan to `<session>/artifacts/optimization-plan.md`:
|
|
|
|
Each optimization MUST have a unique OPT-ID and self-contained detail block:
|
|
|
|
```markdown
|
|
### OPT-001: <title>
|
|
- Priority: P0
|
|
- Target bottleneck: <bottleneck from report>
|
|
- Target files: <file-list>
|
|
- Strategy: <selected approach>
|
|
- Expected improvement: <metric> by <X%>
|
|
- Risk level: <Low/Medium/High>
|
|
- Success criteria: <specific threshold to verify>
|
|
- Implementation guidance:
|
|
1. <step 1>
|
|
2. <step 2>
|
|
3. <step 3>
|
|
|
|
### OPT-002: <title>
|
|
...
|
|
```
|
|
|
|
Requirements:
|
|
- Each OPT-ID is sequentially numbered (OPT-001, OPT-002, ...)
|
|
- Each optimization must be **non-overlapping** in target files (no two OPT-IDs modify the same file unless explicitly noted with conflict resolution)
|
|
- Implementation guidance must be self-contained -- a branch optimizer should be able to work from a single OPT block without reading others
|
|
|
|
2. Update `<session>/wisdom/shared-memory.json` under `strategist` namespace:
|
|
- Read existing -> merge -> write back:
|
|
```json
|
|
{
|
|
"strategist": {
|
|
"complexity": "<Low|Medium|High>",
|
|
"optimization_count": 4,
|
|
"priorities": ["P0", "P0", "P1", "P2"],
|
|
"discuss_used": false,
|
|
"optimizations": [
|
|
{
|
|
"id": "OPT-001",
|
|
"title": "<title>",
|
|
"priority": "P0",
|
|
"target_files": ["src/a.ts", "src/b.ts"],
|
|
"expected_improvement": "<metric> by <X%>",
|
|
"success_criteria": "<threshold>"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
```
|
|
|
|
3. If DISCUSS-OPT was triggered, record discussion summary in `<session>/discussions/DISCUSS-OPT.md`
|