Explore

Find agent skills by outcome

13,119 skills indexed with the new KISS metadata standard.

Showing 24 of 13,119Categories: Operations & Workflow, Cursor-rules, Coding & Debugging, Data, Writing & Content

Data

PromptBeginner5 minmarkdown

- Scan staged git diffs for injection flaws including SQLi

command injection

Mar 21, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

RULE: When using this prompt

you must create a file named `TODO_perf-tuning.md`. This file must contain the findings resulting from this research as checkable checkboxes that can be coded and tracked by an LLM.,TRUE,TEXT,wkaandem...

Find agent skills by outcome

- **Scan** staged git diffs for injection flaws including SQLi

**RULE:** When using this prompt

Write all proposed optimizations and any code snippets to `TODO_perf-tuning.md` only. Do not create any other files. If specific files should be created or edited

- **Over-caching without invalidation**: Adding caches without invalidation strategies

- **Synchronous blocking in async code**: Blocking the event loop or thread pool with synchronous operations

- **Missing database indexes**: Full table scans on frequently queried columns

- **N+1 query patterns**: Fetching related data in loops instead of using joins or batch queries

### Database (Query Analyzers

- Deploy Application Performance Monitoring (Datadog

- Use language-specific CPU and memory profilers (pprof for Go

- [ ] API response times meet SLA: <200ms (p95) for standard endpoints

- Use reproducible benchmarks with consistent hardware

- Correlate bottlenecks with specific code paths

- **API**: Payload size reduction

- **Frontend**: Code splitting

- Design cache-aside

- Query optimization: rewrite queries using execution plan analysis

- **Techniques**: Dynamic programming

- **Data Structures**: Map vs Object for lookups

- Define performance budgets for critical paths (API response times

- Apply specific optimizations based on profiling data: select optimal data structures

- Analyze database query patterns for N+1 problems

- Record reproducible benchmark conditions (hardware

- Collect database query execution plans to identify slow operations

- Scan staged git diffs for injection flaws including SQLi

RULE: When using this prompt

- Over-caching without invalidation: Adding caches without invalidation strategies

- Synchronous blocking in async code: Blocking the event loop or thread pool with synchronous operations

- Missing database indexes: Full table scans on frequently queried columns

- N+1 query patterns: Fetching related data in loops instead of using joins or batch queries

- API: Payload size reduction

- Frontend: Code splitting

- Techniques: Dynamic programming

- Data Structures: Map vs Object for lookups