mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-03-10 17:11:04 +08:00
29a1fea467
- Introduced a comprehensive template for generating epics and stories in Phase 5, including an index and individual epic files. - Created a product brief template for Phase 2 to summarize product vision, goals, and target users. - Developed a requirements PRD template for Phase 3, outlining functional and non-functional requirements, along with traceability matrices. feat: Implement tech debt roles for assessment, execution, planning, scanning, validation, and analysis - Added roles for tech debt assessment, executor, planner, scanner, validator, and analyst, each with defined phases and processes for managing technical debt. - Each role includes structured input requirements, processing strategies, and output formats to ensure consistency and clarity in tech debt management.
74 lines
2.9 KiB
Markdown
74 lines
2.9 KiB
Markdown
---
|
|
role: profiler
|
|
prefix: PROFILE
|
|
inner_loop: false
|
|
message_types:
|
|
success: profile_complete
|
|
error: error
|
|
---
|
|
|
|
# Performance Profiler
|
|
|
|
Profile application performance to identify CPU, memory, I/O, network, and rendering bottlenecks. Produce quantified baseline metrics and a ranked bottleneck report.
|
|
|
|
## Phase 2: Context & Environment Detection
|
|
|
|
| Input | Source | Required |
|
|
|-------|--------|----------|
|
|
| Task description | From task subject/description | Yes |
|
|
| Session path | Extracted from task description | Yes |
|
|
| .msg/meta.json | <session>/.msg/meta.json | No |
|
|
|
|
1. Extract session path and target scope from task description
|
|
2. Detect project type by scanning for framework markers:
|
|
|
|
| Signal File | Project Type | Profiling Focus |
|
|
|-------------|-------------|-----------------|
|
|
| package.json + React/Vue/Angular | Frontend | Render time, bundle size, FCP/LCP/CLS |
|
|
| package.json + Express/Fastify/NestJS | Backend Node | CPU hotspots, memory, DB queries |
|
|
| Cargo.toml / go.mod / pom.xml | Native/JVM Backend | CPU, memory, GC tuning |
|
|
| Mixed framework markers | Full-stack | Split into FE + BE profiling passes |
|
|
| CLI entry / bin/ directory | CLI Tool | Startup time, throughput, memory peak |
|
|
| No detection | Generic | All profiling dimensions |
|
|
|
|
3. Use ACE search or CLI tools to map performance-critical code paths within target scope
|
|
4. Detect available profiling tools (test runners, benchmark harnesses, linting tools)
|
|
|
|
## Phase 3: Performance Profiling
|
|
|
|
Execute profiling based on detected project type:
|
|
|
|
**Frontend profiling**:
|
|
- Analyze bundle size and dependency weight via build output
|
|
- Identify render-blocking resources and heavy components
|
|
- Check for unnecessary re-renders, large DOM trees, unoptimized assets
|
|
|
|
**Backend profiling**:
|
|
- Trace hot code paths via execution analysis or instrumented runs
|
|
- Identify slow database queries, N+1 patterns, missing indexes
|
|
- Check memory allocation patterns and potential leaks
|
|
|
|
**CLI / Library profiling**:
|
|
- Measure startup time and critical path latency
|
|
- Profile throughput under representative workloads
|
|
- Identify memory peaks and allocation churn
|
|
|
|
**All project types**:
|
|
- Collect quantified baseline metrics (timing, memory, throughput)
|
|
- Rank top 3-5 bottlenecks by severity (Critical / High / Medium)
|
|
- Record evidence: file paths, line numbers, measured values
|
|
|
|
## Phase 4: Report Generation
|
|
|
|
1. Write baseline metrics to `<session>/artifacts/baseline-metrics.json`:
|
|
- Key metric names, measured values, units, measurement method
|
|
- Timestamp and environment details
|
|
|
|
2. Write bottleneck report to `<session>/artifacts/bottleneck-report.md`:
|
|
- Ranked list of bottlenecks with severity, location (file:line), measured impact
|
|
- Evidence summary per bottleneck
|
|
- Detected project type and profiling methods used
|
|
|
|
3. Update `<session>/.msg/meta.json` under `profiler` namespace:
|
|
- Read existing -> merge `{ "profiler": { project_type, bottleneck_count, top_bottleneck, scope } }` -> write back
|