Prompts for Stacknaut Projects

Copy these into Claude Code, Cursor, Copilot, or any coding agent after installing Stacknaut. They configure, extend, or verify included code instead of rebuilding the foundations.

Skill-Backed Workflow Prompts

Stacknaut includes pre-built skills that turn short prompts into multi-step workflows. Type these and your agent handles the rest.

Start onboarding

Use the included onboarding wizard to clone repos, collect project decisions, configure integrations, and get the app ready for local development.

Onboard me

Customize the starter app

Use the setup-app workflow to rename the product, replace placeholder copy, configure integrations, and remove starter examples.

set up the app for a B2B SaaS called Acme CRM at acmecrm.com. Include Stripe billing, Postmark email, Google Sign-In, and Better Stack logs.

Hand off and walk away

You've been building a feature and it's mostly done. Say this and the agent reviews your changes, fixes issues, then commits and deploys when the work is ready.

take over

Fix everything that's wrong

You've made a bunch of changes and want a sanity check. The agent reviews all uncommitted code, fixes what it finds, then reviews again -- repeating until everything passes cleanly.

review+fix

Get a code review

Before committing, have the agent review all your uncommitted changes without touching anything. Catches issues you might have missed.

review dirty

Commit with a good message

The agent looks at what changed, writes a succinct commit message following your project conventions, and commits atomically.

commit succinct

Retrospective on your changes

After finishing a task, the agent reflects deeply on what was built and what it would do differently next time.

improve AGENTS.md

Setup Prompts

Use these to configure the starter kit's included auth, billing, infrastructure, and logging for your real project.

Set up a fresh local project

Have the agent configure the repo, environment files, database, and local services after cloning.

Set up this project locally from a fresh clone. Read the README and AGENTS.md first. Tell me what env vars I need, create safe example .env files if missing, install dependencies with pnpm, run type checks, and stop before using real secrets.

Configure the included authentication

Magic link and Google Sign-In are already built and tested. Use this to adapt them to your domain.

Configure the included Stacknaut auth for acmecrm.com. Keep the existing magic link and Google Sign-In implementation. Walk me through the Postmark and Google Cloud dashboard setup, update env values and setup docs, and verify login works locally.

Configure the included billing

Stripe checkout, webhooks, subscriptions, and customer portal are already included. Use this to connect your real plan.

Configure the included Stacknaut Stripe billing for one Pro plan at $29/month. Show me exactly what to create in Stripe, update env values, verify webhook handling, update pricing page copy, and add a smoke-test checklist for checkout, portal, and cancellation.

Provision the included Hetzner server

Stacknaut ships a Terraform repo and a setup skill for creating a tested Hetzner server.

Set up Hetzner

Configure the included deployment

After the server exists, use the deployment skill to set up DNS, Kamal secrets, and the first deploy.

Set up deployment

Connect the included observability

Vector and Better Stack routing are already in the deployment config. Use this to connect the real source.

Connect Stacknaut's included Vector logging to Better Stack for this project. Walk me through creating the Better Stack source, update the required env values, verify Kamal/Vector config, check pino logs include useful context, and make sure no private data is logged.

Feature Prompts

Copy these into your coding agent to build features on top of Stacknaut.

Add a new database table and API endpoint

Create a feature from schema to API in one shot.

Add a "projects" feature. Create a Drizzle table projects.ts with columns: id (serial primary key), userID (integer, references users.id), name (varchar), description (varchar), createdAt (timestamp). Add CRUD endpoints in the backend following the widgetRoutes.ts pattern.

Build a new frontend page with API integration

Scaffold a Vue page that fetches data and handles loading states.

Create a /projects page that lists the current user's projects. Include loading and empty states. Add a "New Project" button that opens a dialog with a form (name + description fields) and POSTs to /projects.

Add multiple Stripe subscription plans

Extend the existing Stripe billing to support tiered pricing with a monthly/annual toggle.

Extend the existing pricing page to support two plans: Starter ($9/mo or $90/yr) and Pro ($29/mo or $290/yr). Add a monthly/annual toggle. Each plan card should list features and have a "Subscribe" button. Support both light and dark themes.

Add a settings page with profile editing

Create an account settings page with form validation.

Create a /settings page with a form to update the user's display name and email. Show success/error toast notifications. Support both light and dark themes.

Add a new transactional email

Create and send a branded email using the existing email system.

Add a "project invitation" email using the sendEmail function in backend/src/lib/email.ts. The email should include: the inviter's name, the project name, and an accept link. Add a POST /projects/:id/invite endpoint that accepts an email address, creates a pending invitation record, and sends the email.

Add an admin dashboard

Build a protected admin area with user and revenue metrics.

Add an /admin route only accessible to admin users. Add an isAdmin boolean column to the users schema and generate the migration. Create a verifyAdminPreHandler middleware similar to verifyJWTTokenPreHandler. Add backend endpoints under /admin/* for: total users count, new users this week, and recent signups. Create a frontend dashboard page for these metrics.

Add a public API with key authentication

Create API key management and a public-facing API endpoint.

Add API key authentication to the api/ service. Create a schema for api_keys with columns: id, userID (references users), key, name, createdAt, lastUsedAt, revokedAt. Add backend endpoints for managing keys: POST /account/api-keys, GET /account/api-keys, DELETE /account/api-keys/:id. In the API service, add middleware that validates the Bearer token against api_keys. Add a frontend UI on the account page for managing keys with copy-to-clipboard.

Add team accounts

Move from single-user accounts to organizations, members, and roles.

Add team accounts. Create organizations, organization_members, and invitations tables. Add owner/admin/member roles. Update auth/session responses with the active organization. Add backend routes to invite members, accept invitations, switch organizations, and remove members. Add a frontend team settings page with role management.

Add file uploads

Build a storage-backed upload flow with size and type validation.

Add avatar uploads. Support PNG/JPEG/WebP up to 1MB. Add backend validation, storage adapter functions, signed or proxied image URLs, and a frontend upload control on the settings page with preview, progress, and error states.

Add audit logs

Track important account, billing, and admin actions.

Add audit logs for security-sensitive actions. Create an audit_logs table with actorUserID, organizationID, action, targetType, targetID, metadata, createdAt. Log login, logout, billing changes, invitation creation, role changes, and API key creation/revocation. Add an admin-visible audit log page with filters.

Add notification preferences

Let users choose which transactional and product emails they receive.

Add notification preferences. Create a user_notification_preferences table, add backend GET/PUT endpoints, and build a settings UI with toggles for product updates, weekly summaries, billing alerts, and security alerts. Security alerts should be mandatory and disabled in the UI.

Add a usage-based limit

Enforce plan limits across backend and UI.

Add a plan limit for projects. Free users can create 1 project, Pro users can create unlimited projects. Enforce this in the backend before project creation, return a structured error, and update the frontend to show an upgrade prompt when the limit is reached.

Add CSV export

Export user-owned data with permissions and streaming in mind.

Add CSV export for projects. Add a backend endpoint that streams a CSV of the current user's projects, escapes fields correctly, includes createdAt, and rejects unauthenticated requests. Add an Export CSV button to the projects page with loading and error states.

These prompts work because Stacknaut includes a comprehensive AGENTS.md that gives your coding agent full context about the project structure, conventions, and patterns.

Learn more about the AI agent config →

Need prompts for any codebase? See portable AI coding prompts →

ec1c2f81