Techlahoma Google Apps Starter

Oklahoma's public launchpad for building small Google-powered apps with agents.

Techlahoma maintains this Bun and TypeScript monorepo so Antigravity can turn one prompt into one isolated, runnable apps/<slug> project with a Google-aligned control plane and app-scoped Firebase Hosting configuration. New here? Open the GDG Tulsa Builder Kit in Notion or follow the no-terminal setup below and let Antigravity be your developer.

Table of contents

• Start here: let Antigravity set everything up
• Intro to GDG workshop links
• Clone and start
• Fork setup
• One-prompt demo builds
• What Google-aligned means
• Put it on Firebase Hosting
  • Protection and safety
  • Advanced lifecycle commands
• Tear the environment down
• Complexity ladder
• Agent contract
• About Techlahoma
• GDG Tulsa Builder Kit

Start here: let Antigravity set everything up

You do not need to know Git, use Terminal, or type any commands yourself.

1. Download Google Antigravity for macOS or Windows, install it, and open it. Sign in if Antigravity asks you to.
2. Create a blank Antigravity project:
   • Click the folder with a + in the left sidebar.
   • Choose New Project, then Add Folder.
   • Create or select an empty folder named GDG Tulsa Workshop, then click Create.
3. Paste the prompt below into Antigravity's chat and press Enter. When Antigravity asks which mode to use, choose Local Mode.

Antigravity may ask permission before it runs a command or installs a missing tool. Read its plain- English explanation and approve only actions that match the setup described in this prompt.

I am a non-technical user. Be my developer and complete this setup for me. Do not
tell me to open Terminal, type commands, clone a repository, or install developer
tools myself. Use your own terminal and browser tools to do the work.

Work only inside the folder attached to this Antigravity Project. Set up this public
starter repository:
https://github.com/techlahoma/techlahoma-google-apps-starter.git

Before changing anything, inspect the Project folder. Never delete or overwrite an
existing folder. If a techlahoma-google-apps-starter folder already exists, verify
that it is the correct repository and reuse it. Otherwise, use your terminal to clone
the repository into a new techlahoma-google-apps-starter folder.

Then complete all of these steps for me:

1. Detect whether this computer is running macOS or Windows.
2. Check for Git and for the version of Bun required by the repository. If either is
   missing, install it from its official source using the normal method for this
   operating system. The only system-level changes you may make are installing Git
   and Bun when they are required. Explain any permission prompt in plain English.
3. Enter the cloned repository and read README.md, AGENTS.md, PROJECT.md, and the
   repository's active instructions before continuing.
4. Install the locked dependencies with `bun install --frozen-lockfile`.
5. Run the repository verification with `bash scripts/verify.sh`.
6. Start the known-good welcome app with `bun run dev` on an available local port and
   keep it running.
7. Open the local app in your browser, confirm that the welcome page loads, and report
   any browser or console error you actually observe.

Do not modify tracked files, commit, push, deploy, create cloud resources, sign in to
Firebase or Google Cloud, or authenticate any external account. If setup cannot finish
without one of those actions, stop and explain the blocker in plain English.

Finish by showing me the exact local website URL first. Then give me a short summary
of what you installed, what you ran, whether verification passed, and any warning or
step that still needs me.

Once the starter is running, continue with the copy-ready one-shot demo prompts to build a new app.

Intro to GDG workshop links

This starter is the public build workspace for Techlahoma's Intro to Google Developer Group workshop with GDG Tulsa. Start with the public repository handout or directory; the linked Notion kit may require a Notion session:

• GDG Tulsa Builder Kit in Notion
• Public event handout in this repository
• Play Tulsa Gravity Rally — scan the in-game QR code to join from a phone
• Complete README resource directory

The working presentation is intentionally not linked here until its Google Drive sharing setting is public. The resource directory at the bottom preserves its attendee-relevant links and safety guidance without exposing the private deck.

Start on a new machine

The native workshop path supports Windows PowerShell without WSL and Apple Silicon macOS without Homebrew. If Git, Bun, or other developer tooling may be missing, start with the fresh-machine setup guide. It documents official, versioned installation paths and the authority boundary for machine changes.

The basic path requires Git and Bun 1.3.14. Mise and the additional tools in mise.toml are optional for starting the app.

git clone https://github.com/techlahoma/techlahoma-google-apps-starter.git
cd techlahoma-google-apps-starter
bun run setup:doctor
bun install --frozen-lockfile
bun run setup:doctor
bun run dev

The root dev command launches the known-good apps/welcome workspace. It runs without a Google account.

Fork setup

Local development works without changing any account-specific values. Before enabling repository ownership or Firebase deployment in a fork, replace these examples with values owned by that fork:

1. Update the repository identity and expected branch-ruleset name in .starter/project.json.

2. Replace @YOUR-GITHUB-USERNAME in .github/CODEOWNERS with a GitHub user or organization team that has write access, then uncomment the ownership rules you want GitHub to enforce.

3. Create the ignored local Firebase binding with the fork's immutable project ID and display name:

   bun run google:config plan --project-id YOUR_PROJECT_ID --display-name "Your Project Name"
   bun run google:config apply --project-id YOUR_PROJECT_ID --display-name "Your Project Name"

4. Run bun run google:doctor and a deployment --dry-run before any remote change. After an authorized deployment, replace the app README's unconfigured live-demo note with the verified Hosting URL.

The tracked .env.example and google.project.example.json files are templates. Their uppercase REPLACE_WITH_* values are deliberately invalid so setup fails until they are replaced. Do not commit the real .env, google.project.json, Firebase CLI authentication, ADC credentials, or service-account keys.

Create another app without touching the existing workspaces:

bun run app:create plan --name example-crm --title "Example CRM"
bun run app:create apply --name example-crm --title "Example CRM"
bun run --cwd apps/example-crm dev

plan is read-only. apply refuses an existing target and creates the app from templates/vite-app. The repository keeps one lockfile while each app owns its source, tests, package metadata, TypeScript config, app.contract.json, and Firebase Hosting config.

App verification workflow

Distinguish between app compilation (check) and app completion (verify):

bun run --cwd apps/example-crm check            # App typecheck, unit tests, and production build
bun run browser:install                         # One-time pinned Chromium download
bun run app:browser:verify --app example-crm   # Shared Playwright browser verification
bun run app:verify --app example-crm           # Full completion check (contract, markers, policy, tests, browser)
bun run agent:finish --changed                 # Verify all changed app workspaces

One-prompt demo builds

Open the cloned repository as the Antigravity workspace, then paste one of the demo prompts. The repository includes the workspace skill build-and-launch-demo. Compatible coding agents should use it automatically to create one unused apps/<slug> workspace, build the complete local artifact, verify it in the browser, launch its development server, and return the app path plus usable local URL without stopping for intermediate approval.

For the live business-interview demo, use the Relationship Workbench prompt kit. It combines a Granola transcript with a tested CRM product, local persistence, and browser-proof contract.

The skill permits local work only. A one-prompt build does not authorize GitHub changes, Google Cloud provisioning, authentication, deployment, publication, or deletion.

Verify the production build, tests, formatting, lint, types, and starter contract through the cross-platform Bun entrypoint:

bun run verify

scripts/verify.sh remains an optional Unix wrapper. Native Windows does not require Bash; Unix shell syntax and shellcheck remain enforced in Linux CI.

Use bun run format to apply GTS to TypeScript and Biome to JSON, HTML, and CSS. Run bun run audit:dependencies for the current registry-backed vulnerability report; its known upstream Firebase CLI exception is documented in the verification record.

What “Google-aligned” means

• TypeScript uses GTS, maintained by Google's Node.js team, with its published Prettier settings and strict compiler base.
• HTML and CSS follow Google's public guidance on semantics, accessibility, and separating structure, presentation, and behavior.
• The contribution workflow favors small self-contained changes, tests with behavior, and concise documentation beside the code.
• Exact dependency versions, a committed lockfile, and one local/CI verification command preserve reproducibility.

It does not claim to reproduce Google's internal monorepo or build environment, and GTS itself is not an official Google product. Bazel, enterprise cloud foundations, and Google open-source legal boilerplate are intentionally outside this Level 0 starter. The complete rationale is in the research and decision.

Put it on Firebase Hosting

Deploy your app workspace to Firebase Hosting with one simple command:

bun run deploy

Running without arguments opens an interactive terminal picker showing discovered app workspaces, active project settings, and destination URLs.

You can also deploy directly by specifying an app slug or workspace directory:

bun run deploy numeronym-generator
bun run deploy apps/numeronym-generator
bun run deploy ./apps/numeronym-generator

Additional options:

bun run deploy --all                    # Build and deploy all discovered apps sequentially
bun run deploy numeronym-generator --dry-run  # Preview deployment targets without mutating
bun run deploy numeronym-generator --yes      # Deploy unattended without interactive confirmation
bun run deploy numeronym-generator --json     # Output machine-readable JSON deployment receipts

Protection and Safety

• Default Site Protection: Deployments will never modify your primary default Hosting site (projectId.web.app). Each app is automatically assigned a dedicated secondary Hosting site.
• First-Run Setup: Interactive execution guides login, connects an existing Firebase project, provisions secondary sites, and updates local configuration.
• Build Preflight: Local builds run before remote deployment. For --all, every app is built before the first site is updated.
• Receipt & Live Verification: Successful deployments query Firebase Hosting metadata, display the public URL and console links, and verify HTTP responsiveness.

Advanced lifecycle commands

For advanced granular control or project teardown, low-level lifecycle commands remain available:

# Destroy a single Hosting site without touching the project
bun run google:sites:destroy plan --app welcome

# Destroy the whole shared project (destructive operation)
bun run google:destroy plan

Tear the environment down

Delete a single Hosting site without deleting the shared project:

bun run google:sites:destroy plan --app welcome
bun run google:sites:destroy apply --app welcome --confirm YOUR_PROJECT_ID

To delete the entire shared Google Cloud project:

bun run google:destroy plan
bun run google:destroy apply --confirm YOUR_PROJECT_ID

Deletion is destructive. Export anything durable first. Google may provide a limited recovery window, but the starter does not treat that window as a backup.

Complexity ladder

Level	Add when	Google products	Infrastructure approach
0 — generated app	A static site or SPA is enough	Firebase Hosting	Root shared config plus pinned root Firebase CLI
1 — app data	The product needs identity or shared records	Firebase Auth, Firestore, Emulator Suite	Add only the selected Firebase features and rules
2 — server work	A trusted API, job, or long-running request is necessary	Cloud Run, Cloud Tasks, Secret Manager	Billing and explicit service enablement become required
3 — platform	Multiple environments or services drift across a team	Google Cloud resources	Terraform/OpenTofu modules plus remote state and CI federation

Do not pre-install the next level. Each level has a real operational cost and a separate decision boundary.

Agent contract

• Run bun run google:doctor for a local, read-only readiness report.
• Run plan before every apply.
• Never infer a project from Firebase or gcloud's global defaults.
• Never link billing, enable APIs, create credentials, deploy, or delete a project without explicit authority for that effect.
• Prefer Application Default Credentials locally and Workload Identity Federation in CI; do not create long-lived service-account keys.

The complete command/effect table and current proof live in PROJECT.md.

About Techlahoma

Techlahoma is an Oklahoma technology community nonprofit. Find a user group, join the Techlahoma Slack, or contact the organization to get involved.

This is a Techlahoma community project, not an official Google product. GDG Tulsa is an independent Google Developer Group; its activities and opinions are not affiliated with or endorsed by Google.

GDG Tulsa Builder Kit

This is the complete public resource directory for the Intro to Google Developer Group workshop. The same links are maintained in the GDG Tulsa Builder Kit in Notion.

Start here

• Techlahoma Google Apps Starter repository
• Tulsa Gravity Rally live demo
• Tulsa Gravity Rally source, verification, and prompts
• Public event handout and resource hub
• Download Google Antigravity for macOS or Windows
• Copy-ready Antigravity demo prompts
• Transcript-conditioned Relationship Workbench prompt
• Intro to Google Developer Group event page
• Follow Techlahoma Events on Luma for future events, newsletters, and reminders
• Official GDG Tulsa chapter

Build with Google

• Open Google AI Studio
• AI Studio Build mode guide
• Deploy an app from AI Studio
• Google Cloud Starter Tier
• Cloud Run Button

Stay connected

• GDG Tulsa community website — browse community information here; use the official GDG Tulsa chapter for official membership and event registration
• GDG Tulsa on Instagram
• Techlahoma
• Techlahoma user groups
• Techlahoma on LinkedIn
• Techlahoma on GitHub
• Techlahoma membership and Slack access
• Join Techlahoma Slack directly and open #ug-google for GDG Tulsa questions, event links, and follow-up
• Techlahoma talks on YouTube

Community standards

• Techlahoma Code of Conduct
• Google Event Community Guidelines and Anti-Harassment Policy

Both standards apply. Talk to a volunteer immediately when it is safe to do so if you experience or observe a problem.

Build responsibly

• Use invented demo data. Do not paste private customer, employee, donor, health, financial, or personal records into a live build.
• A working first version is not automatically production-ready. Real use may require authentication, authorization, privacy review, accessibility checks, tests, cost controls, monitoring, backups, and maintenance ownership.
• Take one artifact from the workshop, show it to one person, and try a second version within seven days. Bring back what worked, what broke, and what assumption changed.

Coming next

The August 2026 workshop slide plan lists OklahomAI Google Edition as planned for September 23, 2026 at 6 PM. The public Techlahoma Events calendar does not yet confirm the event, so treat the date as planned and follow the calendar for the authoritative registration link, schedule, and venue when they are published.

Luma documents calendar Follow as the public signup for a calendar's events, newsletters, and reminders, so this directory does not invent a second “blast signup” URL.