Builderthread guides

What is in your repo

When you approve your product brief, Builderthread creates a private GitHub repository built for your product. Instead of handing your AI coding tool an empty folder or a generic template, Builderthread prepares working starter code, verifies that it installs and builds, and writes your PRDs and task list directly against that codebase.

How Builderthread prepares your repository

1. Stack matched to your product

Builderthread reads your approved brief and selects the right foundation for what you are building, whether that is a web SaaS app, an iOS and Android mobile app, a desktop app, a Chrome extension, or an API and AI backend.

If you have specific preferences, you can also switch your managed Postgres provider (Neon or Supabase), your deployment host, or your preferred AI coding tool (Cursor, Claude Code, Codex, Windsurf, VS Code with GitHub Copilot, Gemini CLI, Kiro, or OpenCode) before building.

2. Built and checked before you clone

When you click Prepare my build, Builderthread assembles and checks your repository in the background:

  1. Generates your starter foundation: sets up the project structure, authentication, database wiring, and billing for your stack.
  2. Writes PRDs for your actual code: maps every folder and script in PRD/CODEBASE_MAP.md and writes your modular PRDs in PRD/ referencing the real file paths in your repository.
  3. Adds your product data model and roles: drafts the initial database tables and user permission rules from your PRDs and documents them in PRD/GROUNDWORK.md.
  4. Bundles skills and agent instructions: adds curated guides for UI design, copywriting, security reviews, and the tools in your stack, placed in the folder your coding tool reads.
  5. Pushes to your private GitHub repo: creates the private repository on your GitHub account and emails you when it is ready to clone.

Supported stacks

Builderthread supports modern stacks across TypeScript, Python, React Native, Rust, and browser extensions:

ProductEcosystemStack includedShips to
Web app (SaaS)TypeScriptNext.js, Hono, tRPC, Drizzle, Postgres (Neon or Supabase), Better Auth, Stripe, Trigger.dev, Vercel AI SDK, ResendVercel and Railway
API, bot, or automationTypeScriptHono, OpenAPI, Drizzle, Postgres (Neon or Supabase), Better Auth, Trigger.dev, Apify, DockerRailway
AI or data backendPythonFastAPI, Postgres, SQLAlchemy, Pydantic, OpenAI SDK, Ruff, Pytest, uv, DockerRailway
Mobile appReact NativeExpo, Expo Router, Uniwind, Hono API, tRPC, Drizzle, Postgres (Neon or Supabase), Better Auth, StripeApp Store and Google Play via Expo EAS
Desktop appDesktop (TypeScript + Rust)Tauri, React, TanStack Router, shadcn/uiGitHub Releases (macOS, Windows, Linux installers)
Chrome extensionBrowser extensionWXT (Manifest V3 for Chrome and Firefox), React, TanStack Router, shadcn/ui, chrome.storageChrome Web Store

Files your coding agent reads first

When you paste your start prompt into your AI coding tool, it reads these files first so it understands your product and codebase from the first task:

  • AGENTS.md and CLAUDE.md: the rulebook covering how the agent works with you, how it picks up tasks through MCP, Git branching rules, which skills to use, and when to pause for your approval.
  • PRD/CODEBASE_MAP.md: a complete map of where each part of your app lives and which scripts to run.
  • PRD/product-requirements.md and PRD/*.md: your living PRD documents written against the files and packages in your repository.
  • PRD/GROUNDWORK.md: the initial database tables, roles, and permission rules prepared from your PRDs.
  • PRD/SKILLS.md and PRD/SKILL_COVERAGE.md: the list of official tool skills and design, copy, and security guides included in your repository.
  • .agents/product-marketing.md: your product positioning, target customer, and value proposition so your agent writes clear, consistent copy across every screen.

Setup guides and Git workflow

  • docs/database.md: step by step database setup. Web and mobile apps default to Neon (free cloud Postgres with a separate database branch for each feature, so you do not need Docker). Your agent asks before installing any CLI and pauses for browser login.
  • docs/deployment.md and docs/environment-variables.md: where your app deploys, which API keys it needs, and how to get each one.
  • .github/workflows/ci.yml (and .builderthread/ci/github-actions.yml): an automated GitHub Actions check that runs type checks, tests, and security checks on every push.
  • Safe Git branches: your agent works on a separate branch for each task, commits after each working step, and opens a pull request or merges into main once checks pass.