is-app
Web application for Intentional Society — an authenticated app for a small, globally distributed membership network.
Live at app.intentionalsociety.org
How the app works
A Next.js frontend talks to a Hono API backend, both running in the same codebase. Data lives in PostgreSQL (managed by Supabase), accessed via Drizzle ORM. Supabase also handles authentication. For local development, the entire Supabase stack runs in Docker on your machine.
Getting started
1. Install prerequisites
Git, Node.js 24, and Docker Desktop. See docs/setup-dev-machine.md for install instructions.
2. Clone and install
git clone https://github.com/Intentional-Society/is-app.git
cd is-app
npm install
3. Set up environment
npm run setup
Generates .env.local with the deterministic local Supabase defaults, installs the Playwright Chromium browser for e2e tests, and applies local workflow setup. Safe to re-run.
4. Run
npm run dev
This starts a local Supabase stack in Docker (Postgres, Auth, Studio), runs any pending database migrations, then launches the Next.js dev server at http://localhost:3000.
First run pulls Docker images and takes a few minutes. After that, startup is near-instant.
Useful commands
| Command | What it does |
|---|
npm run dev | Start Supabase + Next.js dev server |
npm run dev:db:stop | Stop local Supabase containers |
npm run dev:db:reset | Wipe local DB and reapply migrations |
npm test | Run all tests (functional + e2e) |
npm run watch | Vitest in watch mode |
npm run lint | Biome |
Project structure
src/
app/ Next.js pages and layouts
app/api/ Catch-all route that delegates to Hono
server/api.ts Hono API routes (the backend)
server/schema.ts Drizzle database schema
server/db.ts Database connection
lib/api.ts Typed API client (apiClient) for frontend use
lib/supabase/ Supabase auth helpers (server, client, middleware)
docs/ Architecture specs, strategy docs, config references
tests/ Functional and e2e tests
supabase/ Local Supabase config (config.toml)
drizzle/ Database migration files
Working with AI assistants
Claude Code Skills under .claude/skills/ encode the team's check-in workflow. /commit and /pr fire on a typed slash command or on plain-language intent ("commit this", "open a PR") — including a bare "yes" to an assistant's own offer; when one fires from plain language it announces Using /commit or Using /pr first, so you can see it. /ship is explicit-only: type it.
/commit [issue-or-context] — stage, test, draft a Conventional Commit-style message, bundled human approval, push./pr [PR#|URL|issue-or-context] — fetch + rebase if needed, push, open or update the PR./ship [PR#|URL|issue-or-context] — orchestrates the full chain (/pr → /commit as needed), waits for CI green, merges, watches main.
Design rationale and the full step lists are in docs/spec-portable-ai-procedures.md.
Documentation
