From cf-powers
Reviews technical documents, designs, specs, and code for performance issues like missing indexes, N+1 queries, algorithm complexity, memory usage, caching strategies, and scalability.
npx claudepluginhub cloudfieldcz/cf-powers --plugin cf-powersThis skill uses the workspace's default tool permissions.
Review a technical analysis or specification document from a performance engineer perspective. Focus on whether the proposed solution will perform well under realistic load — checking database access patterns, algorithm complexity, memory usage, caching, and scalability.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Review a technical analysis or specification document from a performance engineer perspective. Focus on whether the proposed solution will perform well under realistic load — checking database access patterns, algorithm complexity, memory usage, caching, and scalability.
Announce at start: "I'm reviewing this document as a Performance Engineer."
docs/plans/YYYY-MM-DD-<topic>.md)CRITICAL: This is the most common source of performance problems. Read the actual schema and queries.
Structure your review exactly like this:
# Performance Review: <topic>
## Summary
[1-2 sentence performance assessment]
## Database access patterns
- ✅ [Well-indexed query pattern]
- CRITICAL: [Missing index — describe query, table size, expected impact]
- HIGH: [N+1 query pattern — describe loop, suggest eager loading/batch query]
## Algorithm complexity
- ✅ [Appropriate algorithm choice]
- HIGH: [Suboptimal algorithm — describe complexity, suggest alternative]
- MEDIUM: [Unnecessary work — describe and suggest optimization]
## Memory and resources
- ✅ [Efficient resource usage]
- HIGH: [Unbounded collection or memory leak risk — describe scenario]
- MEDIUM: [Opportunity to use streaming instead of loading all]
## Caching
- ✅ [Appropriate caching strategy]
- MEDIUM: [Missing cache opportunity — describe access pattern]
- MEDIUM: [Cache invalidation risk — describe staleness scenario]
## Network and I/O
- ✅ [Efficient I/O pattern]
- HIGH: [Unbatched external calls — describe N+1 HTTP/API pattern]
- MEDIUM: [Missing connection pooling or compression]
## Scalability
- ✅ [Scales well with data growth]
- HIGH: [Bottleneck at scale — describe what breaks at 10x/100x]
## Performance questions
1. [Question about expected data volume or access pattern]
2. [Clarification about load characteristics]
## Recommendations
1. [Actionable performance recommendation — priority order]
2. [Actionable performance recommendation]
## Verdict
**Performance assessment:** [OK / Needs optimization / Critical issues]
**Recommended next step:** [Proceed to planning / Incorporate feedback / Requires redesign of performance-critical parts]