profullstack.com/stack: the stack, per use case, written for agents

Profullstack published a machine-readable stack reference at profullstack.com/stack, with Markdown and JSON copies, so AI coding agents can read the company's conventions before writing code. The page organizes roughly 170 active repos into use-case combos — web-app, api-service, cli-tui, desktop, mobile, library and systems — and documents shared defaults, twelve house rules, reusable packages, and technologies deliberately excluded from the stack. The content is based on a survey of all 251 repos under the org, 171 of which had human commits since June 2025, and it supersedes an older skill file where the two disagree.

We put the current Profullstack stack at profullstack.com/stack https://profullstack.com/stack . It has a Markdown copy at /stack.md https://profullstack.com/stack.md and a JSON copy at /stack.json https://profullstack.com/stack.json . It exists so an agent can read it before it writes code for us. We run about 170 active repos, and they do not all look alike. A web app, an API service, a CLI and a desktop app want different things. So the page is organised as combos, and the first thing on it is a table that maps the job to the combo. web-app : Next 16 with a Hono API mounted inside it, Turso for data, one Railway service. The default for anything new. web-app-postgres : the previous generation, on Supabase or a self-hosted Postgres. Still the largest by count. Stay on it if the app is already there. api-service : Hono on Bun or Node, Turso, a rate limit that answers with a price, an MCP bridge. cli-tui : Node, commander, hqtui for dashboards, published to npm with a curl installer. desktop : Electron with the CLI bundled inside the app, so one install gives both. mobile : Expo inside the product monorepo. library : a runtime-neutral @profullstack/ package with subpath exports. systems : Rust or Go when it has to be a single fast binary. Each combo says when to use it, lists its layers with the reasons, and names the live repos built on it. Below the combos are the defaults that apply everywhere: Railway and Porkbun, secrets in the vault rather than .env files, magic link and passkeys for auth, Resend for mail, CoinPay for payments, the x402 gateway and throttle in front of every public site, vitest, GitHub Actions, and myna for promotion. Then twelve house rules, the published packages to reuse before writing anything, and a list of what is not in the stack. That last one is for the habits an agent brings from elsewhere: Vercel, next-auth, Prisma, a hand-rolled video player. The content is from a survey of all 251 repos under the org, 171 of them with human commits since June 2025. It counted frameworks, databases, package managers, deploy targets and which of our own packages each repo actually imports. Some of what our older skill file claimed turned out not to be true, and the page says so. Oxc and Rolldown are in six repos, not the default. The Shared AppKit packages were never published. The page now wins where the two disagree. Point an agent at it: curl https://profullstack.com/stack.md Or install the Profullstack skill from profullstack.com/agents https://profullstack.com/agents , which links to it. The page, the Markdown and the JSON all render from one data file in the site repo, so when a default changes, one file changes.