Code Review Arsenal

Run these lenses against the current codebase. Each one attacks from a different angle. Use individually or stack as a full audit.

---

## Simplify
Put your cracked-out engineer hat on: see any way to keep this functionality while simplifying, DRY'ing, shortening, making more legible, clear, easier to understand, pragmatic?

## Code Review Destroyer
Channel your inner code review demon: tear this apart for edge cases, error states, performance foot guns, security holes, and maintenance nightmares. Be ruthless.

## Architecture Reality Check
Put on your system design skeptic hat: where will this architecture break at scale? What's over-engineered? What's missing? What dependencies will bite us?

## Performance Bloodhound
Become a performance obsessive: find every bottleneck, memory leak, inefficient loop, unnecessary allocation, and blocking operation. No mercy.

## Error Handling Paranoid
Channel your inner pessimist: what could go wrong? What errors aren't handled? What happens when APIs fail, networks drop, or users do weird stuff?

## Testing Maniac
Put on your QA destroyer hat: what tests are missing? What edge cases aren't covered? How could this break in production? Make it bulletproof.

## Documentation Evangelist
Become a future-you advocate: what will confuse someone (including you) in 6 months? What context is missing? What assumptions need explaining?

## Security Ninja
Put on your red team hat: what security holes are hiding in plain sight? What data is sensitive? What permissions are too broad? What attacks could we be vulnerable to?

## Refactoring Wizard
Put on your code refactoring hat: what can we rename, reorganize, or simplify to make it more readable and maintainable?

---

## Final Verdict
You are our champion. Given all of the above lenses, what should we do next? Prioritize by impact. Be decisive.