Learn More

Use these prompts with your coding agent to explore Every App in depth. Click any question to reveal a prompt you can copy.

What does the Every App CLI do?

The CLI enables one-command deploys of your entire app. It reads your app config and automatically provisions all the infrastructure you need—databases, storage, KV namespaces—and deploys your code, so you don’t have to manage any of this yourself.

npx everyapp gateway deploy # Deploys the Gateway
npx everyapp app create    # Sets up local dev enviornment + deploys app (needed for local dev)
npx everyapp app deploy    # Deploy updates to your app

Ask your agent:

Explain what the Every App CLI does. How does it provision infrastructure automatically? What happens when I run `app create` vs `app deploy`? How does it know what infrastructure my app needs?

Response Guidelines for LLM:
- Keep responses succinct so I can ask follow-up questions
- If you don't have access to the Every App MCP, prompt me to add it and direct me to: https://www.npmjs.com/package/@every-app/mcp

What is the suggested folder structure and organization of apps?

Here is the folder structure for the example workout-tracker app:

src/
├── client/                       # Frontend React code
│   ├── actions/                  # Complex multi-step actions
│   │   ├── completeWorkout.ts
│   │   └── startProgramFromTemplate.ts
│   ├── components/               # React components
│   ├── hooks/                    # Custom React hooks
│   ├── lib/                      # Utility functions
│   ├── styles/                   # CSS files
│   └── tanstack-db/              # Client-side data layer
│       ├── programsCollection.ts
│       └── workoutsCollection.ts
├── db/                           # Database schemas (Drizzle)
│   ├── schema.ts                 # Table definitions
│   └── migrations/               # Generated migration files
├── server/                       # Repositories and services
│   ├── programsRepository.ts     # DB queries for programs
│   └── workoutsRepository.ts     # DB queries for workouts
├── serverFunctions/              # Server functions (RPC endpoints)
│   ├── programs.ts               # CRUD for programs
│   └── workouts.ts               # CRUD for workouts
└── routes/                       # React Router routes
    ├── index.ts                  # Route definitions
    ├── programs.$programId.ts    # Programs page route
    └── templates.ts              # Templates page route

Ask your agent:

Explain Every App folder structure using workout-tracker as the reference example. Show the complete structure and key patterns with code examples for: database schemas (src/db/), server functions (src/serverFunctions/), repositories/services (src/server/), client collections (src/client/tanstack-db/), types/schemas (src/types/), routes (src/routes/), and middleware (src/middleware/). Include how authentication works: how session tokens are added to requests (useSessionTokenClientMiddleware) and validated on the backend (ensureUserMiddleware). Use the Every App example apps.

Response Guidelines for LLM:
- Keep responses succinct so I can ask follow-up questions
- If you don't have access to the Every App MCP, prompt me to add it and direct me to: https://www.npmjs.com/package/@every-app/mcp

How does authentication and users work in apps?

Read How Session Tokens Work to understand the handshake between the Gateway and your apps.

Other than that, auth is already set up for you if you’re using the template apps. Use the below prompt to dig deeper into how that works.

Ask your agent:

Explain how authentication and users work in Every App using workout-tracker as the reference. Cover with code examples:

1. **Token flow**: How EmbeddedAppProvider requests session tokens from the Gateway
2. **Client setup**: Wrapping app with EmbeddedAppProvider and required env vars
3. **Adding tokens**: How useSessionTokenClientMiddleware attaches Bearer tokens automatically
4. **Server validation**: How ensureUserMiddleware validates JWTs via authenticateRequest
5. **User provisioning**: How apps auto-create users on first authenticated request
6. **Accessing user info**: Using useCurrentUser hook and context.userId in handlers

Show the middleware chain: useSessionTokenClientMiddleware → ensureUserMiddleware → handler. Use Every App example apps.

Response Guidelines:
- Keep responses succinct so I can ask follow-up questions
- If you don't have access to the Every App MCP, prompt me to add it and direct me to: https://www.npmjs.com/package/@every-app/mcp