Prompts Personalizados

Focus on HIPAA compliance in data handling:
- PHI (Protected Health Information) exposure in logs or errors
- Missing encryption for PHI at rest and in transit
- Inadequate access controls for patient data
- Audit logging gaps for PHI access
- Data retention violations
- Missing patient consent verification

Focus on React and Node.js common pitfalls:
- Missing dependency arrays in useEffect/useMemo
- Unhandled promise rejections in async handlers
- Memory leaks from event listener cleanup
- Race conditions in state updates
- Missing error boundaries
- Uncaught exceptions in Express middleware

Analyze algorithmic efficiency and resource usage.
List specific issues in this format:
1. Issue type and location
2. Current complexity
3. Optimization suggestion
4. Expected improvement

Prioritize: database queries, loops, memory allocations.

Only flag as Critical if:
- Production data could be deleted or corrupted
- Security breach allowing direct data exfiltration
- Payment processing failures
- Complete service outage for core features

Note: Performance issues are never Critical unless causing crashes.

When writing suggestions, adjust the level of detail based on severity:

For Critical issues: Start with "🚨 CRITICAL:" followed by the problem. 
Add a line explaining "This requires immediate attention." Then provide 
the fix with "Fix:" prefix.

For High severity: Use "⚠️" emoji, state the problem, then show the fix 
with "Fix:" prefix.

For Medium and Low: Keep it brief - just state the problem and show the 
suggested code directly without extra explanation.

Be direct and concise. State the problem in one sentence, then immediately 
show the fix with "Fix:" prefix. No additional context or explanations.

Structure suggestions in three parts:

1. **Issue:** State the problem clearly
2. **Why this matters:** Explain the impact based on severity:
   - Critical: Could cause production failures or security vulnerabilities
   - High: May lead to bugs or performance problems  
   - Medium/Low: Improves code quality and maintainability
3. **Fix:** Show the recommended code change

Make explanations educational and help developers learn why it matters.

Use different tones based on the type:

For Kody Rules violations:
- Start with "**Team Standard Violation**" in bold
- State the problem
- Add "This violates documented team standards."
- Show "Required fix:" followed by the code

For standard suggestions:
- State the problem directly
- Show "Suggested improvement:" followed by the code
- Use a friendly, recommendatory tone