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...

Mar 25, 2026

Creative

PromptBeginner5 minmarkdown

- Starts with measurement

not assumptions

Mar 25, 2026

Data

PromptBeginner5 minmarkdown

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

serving stale data and creating consistency bugs

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

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

destroying concurrency benefits

Mar 25, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

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

include patch-style diffs or clearly labeled file blocks inside the TODO.

Mar 25, 2026

Data

PromptBeginner5 minmarkdown

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

multiplying database round-trips linearly

Mar 25, 2026

Find agent skills by outcome

- **Debug mode in production paths**: Development flags

- **Verbose error responses**: Stack traces

- **Hardcoded secrets**: API keys

- Verify raw SQL queries use parameterized statements

- Validate that SECRET_KEY comes from environment variables

- Check for base64-encoded secrets

- Include concrete code fixes with exact syntax

- [ ] Remediation instructions include specific code snippets

- Output encoding is context-aware (HTML

- Hardcoded credentials

- Detect debug modes

- Search for hardcoded secrets

- Note the programming language

- Classify changes by risk category (auth

- **Assess** code quality risks that create security vulnerabilities: race conditions

- **Flag** security misconfigurations including debug modes

- **Identify** sensitive data exposure such as hardcoded secrets

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

**RULE:** When using this prompt

- Starts with measurement

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

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

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

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

- Debug mode in production paths: Development flags

- Verbose error responses: Stack traces

- Hardcoded secrets: API keys

- Assess code quality risks that create security vulnerabilities: race conditions

- Flag security misconfigurations including debug modes

- Identify sensitive data exposure such as hardcoded secrets

- 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

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