AI Coding Prompts That Work Anywhere
Copy these into Claude Code, Cursor, Copilot, or any coding agent. They start by inspecting the existing codebase so the agent adapts what is already there before adding anything new.
Using Stacknaut? Use the Stacknaut-specific prompts instead. Auth, billing, deployment, and logging are already included and tested there.
Portable Setup Prompts
Use these in most codebases. If the feature already exists, the prompt tells the agent to adapt and verify it instead of rebuilding.
Configure authentication
Works in most full-stack apps. In Stacknaut, magic link and Google Sign-In are already included and tested.
Configure production-ready auth for this app. Prefer magic link email plus Google Sign-In. First inspect existing auth code and docs. If auth already exists, adapt and verify it instead of rebuilding. If it does not exist, add database schema, backend routes, frontend login flows, env validation, and setup docs.
Configure billing
Works in most SaaS apps. In Stacknaut, Stripe checkout, webhooks, and customer portal are already included.
Configure subscription billing for this app. Prefer Stripe Checkout, webhooks, and the hosted customer portal. First inspect existing billing code. If billing already exists, connect it to the real product and verify it. If it does not exist, add the backend routes, webhook handling, frontend pricing flow, env validation, and setup docs.
Prepare production deployment
Works in most repos. In Stacknaut, Hetzner Terraform and Kamal config are already included.
Prepare this app for production deployment. Inspect the current deployment setup, Dockerfiles, env vars, database needs, DNS assumptions, and logging. If deployment config already exists, verify it and produce a first-deploy checklist. If not, propose the smallest production-ready deployment path.
Add production logging
Works in most backend apps. In Stacknaut, Vector and Better Stack routing are already included.
Review production logging for this app. Check that logs are structured, useful for debugging, and do not leak private data. If a log pipeline already exists, verify it. If not, propose and implement a minimal production logging setup consistent with the repo.
Maintenance Prompts
Use these for debugging, hardening, docs, tests, and deploy prep after the first version ships.
Spec out a feature before building
Instead of jumping into code, have the agent ask about requirements, UX, edge cases, and tradeoffs first.
Help me spec a team collaboration feature with shared projects and role-based permissions. Ask clarifying questions first, then write a detailed implementation spec I can review before coding starts.
Find and fix a production bug
Start from symptoms, inspect logs, reproduce locally, then patch.
Investigate this bug: users sometimes see a blank dashboard after login. Check relevant frontend and backend code, identify what data could be missing or delayed, add defensive handling, and include the exact test or manual repro you used.
Harden a backend route
Review validation, auth, rate limits, timeouts, and error shape.
Harden the POST /projects route. Check authentication, zod validation, database constraints, rate limiting assumptions, logging, error messages, and frontend handling. Make focused changes only where there is real risk.
Improve loading and empty states
Make a page feel production-ready under slow, empty, and failed responses.
Improve the /projects page loading, empty, and error states. Account for slow networks, empty accounts, expired sessions, and failed saves. Keep the UI consistent in light and dark themes.
Prepare a deploy
Check the diff, run verification, and surface deployment risk.
Prepare this change for deployment. Review dirty files, run the required type checks and lint, check env var changes, look for database migration risk, and give me a short deploy checklist before deploying.
Update docs after a feature
Keep setup docs, app docs, and agent instructions aligned.
Update docs for the feature I just added. Search for all related setup, README, docs, and AGENTS.md references. Keep user-facing instructions accurate and avoid duplicating stale implementation details.
Add tests around a risky change
Ask the agent to target tests at behavior instead of snapshots.
Add focused tests for the billing webhook changes. Cover new subscription, cancelled subscription, duplicate event delivery, and unknown customer IDs. Prefer behavior-level tests and keep mocks small.
Growth Prompts
Use these to add SEO pages, lead magnets, comparison content, and conversion improvements.
Add an SEO article
Create a prerendered content page with sitemap and metadata updates.
Add an SEO article at /articles/saas-onboarding-checklist. Write practical copy for founders launching a B2B SaaS, add route metadata, prerender config, sitemap entry, and internal links from related pages.
Add a comparison page
Create a targeted landing page against a competitor or alternative.
Add a comparison page for our product vs building from scratch. Focus on time saved, production infrastructure, AI agent setup, and ongoing maintenance. Add route metadata, prerender config, sitemap entry, and links from the comparisons index.
Improve homepage conversion
Have the agent review copy and implement grounded changes.
Review the homepage for conversion. Identify unclear claims, weak CTAs, missing proof, and confusing sections. Then make focused copy and layout improvements without changing the visual system.
Create a lead magnet flow
Build email capture, delivery, and follow-up content.
Add a lead magnet for "The SaaS Launch Checklist". Create the downloadable file, email capture copy, welcome email with the download link, unsubscribe-safe follow-up emails, and frontend success/error states.