AIR-003medium SeverityAI-Generated Anti-Patterns & Dynamic Execution
System Prompts Protected from Direct Client-Side Exposure
In client-side AI apps, agents place detailed system instructions in frontend state, allowing users to extract proprietary prompts in DevTools.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "System Prompts Protected from Direct Client-Side Exposure" (AIR-003). Issue: In client-side AI apps, agents place detailed system instructions in frontend state, allowing users to extract proprietary prompts in DevTools. Remediation required: Store system prompts on the backend and make API calls to LLM providers through protected server routes only. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
In client-side AI apps, agents place detailed system instructions in frontend state, allowing users to extract proprietary prompts in DevTools.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: System Prompts Protected from Direct Client-Side Exposure
// Problematic pattern: In client-side AI apps, agents place detailed system instructions in frontend state, allowing users to extract proprietary prompts in DevTools.Launch-Ready Fix
// Production-ready fix for: System Prompts Protected from Direct Client-Side Exposure
// Recommended remediation: Store system prompts on the backend and make API calls to LLM providers through protected server routes only.Remediation & Verification Checklist
Remediation: Store system prompts on the backend and make API calls to LLM providers through protected server routes only.
- Search your codebase for pattern matching "System Prompts Protected from Direct Client-Side Exposure".
- Apply the recommended remediation: Store system prompts on the backend and make API calls to LLM providers through protected server routes only.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.