Fix Prompts

My Next.js website is missing a Content-Security-Policy (CSP) header.

Current state: No CSP header is present in HTTP responses.

Please:
1. Add a Content-Security-Policy header to my Next.js app via next.config.js headers()
2. Start with a policy that allows my own domain, common CDN sources, and inline styles (since the app uses Tailwind)
3. Explain each directive you add
4. Show the complete next.config.js headers configuration

Framework: Next.js 15 (App Router)

My website has an exposed API key in a public JavaScript bundle. The key is a [KEY_TYPE] key starting with [KEY_PREFIX].

Current state: The key is being used directly in client-side code, making it visible to anyone in devtools.

Please:
1. Move the API call to a Next.js API route (server-side)
2. Store the key in .env.local as [ENV_VAR_NAME]
3. Update the client-side code to call our API route instead
4. Add the API route with proper error handling
5. Confirm the key will not appear in any client bundle

Framework: Next.js 15 (App Router)

My website is missing an HTTP Strict Transport Security (HSTS) header.

Please add the Strict-Transport-Security header to my Next.js app with:
- max-age of at least 31536000 (1 year)
- includeSubDomains directive
- Via next.config.js headers() configuration

Show the complete headers configuration.

I need to create a /llms.txt file for my product to improve AI visibility.

My product: [PRODUCT_NAME]
What it does: [ONE_LINE_DESCRIPTION]
Target audience: [TARGET_AUDIENCE]
Key features: [LIST_KEY_FEATURES]
Pricing: [PRICING_SUMMARY]
Key URLs: homepage [URL], pricing [URL], docs [URL]

Please generate a complete llms.txt file following the llmstxt.org specification with all required sections: product name as H1, one-line description as blockquote, Overview, Target Audience, Key Features, Pricing, and Optional Links.