Ghoststack Docs
Concepts

File Structure

Start at the file that controls the behavior you want to change. Ask the agent to inspect it and nearby code before introducing another abstraction.

ChangeStart here
Landing pageapp/page.tsx
Header/footercomponents/header.tsx, components/footer.tsx
Theme and branding metadataapp/globals.css, app/layout.tsx
Plans and pricinglib/plans.ts, app/pricing/page.tsx
Sign-inapp/login/page.tsx, app/callback/route.ts, proxy.ts
Dashboard and settingsapp/dashboard/page.tsx, app/dashboard/settings/page.tsx
Auth clients and user querieslib/supabase/
Schemasupabase/setup.sql and any later migration files
Checkout and portalapp/api/stripe/, lib/stripe.ts
Stripe subscription eventsapp/api/webhooks/stripe/route.ts
Email templates and sendingemails/, lib/resend.tsx
AI callslib/openrouter.ts
Shared agent instructionsAGENTS.md; Claude Code adapter in CLAUDE.md
Offline guide referencedocs/ — generated Markdown for you and your agent, not app routes

Files under app/ define pages and API routes. Files under lib/ hold server/client helpers. components/ contains shared UI. emails/ uses React Email and inline styles, separately from the app's DaisyUI theme.

The current beginner guides are hosted at getghoststack.dev/docs; docs/ is an offline reference copy. The starter does not include a documentation website or its rendering dependencies. Add your own help pages when needed.

Prompt: find where to change something

I want to change [BEHAVIOR]. Read AGENTS.md and identify the files responsible.
Explain the smallest change and which user flow needs testing afterward.

See architecture for how requests pass between these files and services.