Bygga
Type the product name from the box. Bygga shows every assembly step in 3D, with the parts, screws and tools for each one, and reads it out loud.
Guided maintenance self-management for homeowners.
Translation pending
LifestyleTypeScript · HTMLGitHub @hypnoticdata777OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗One calm record for every home repair: capture it, share just that job, prove the work, keep the history.
Homeowners who manage their own repairs live in text threads, camera rolls and receipt drawers. TurnFlow Home gives each property one shared record. You log an issue with photos, compare quotes, invite a vendor or trusted helper to that one request only, and get before/after proof, a decision history and a cost record that stays with the house.
It is intentionally homeowner-first: not property-management dispatch software, and not a payment processor.
flowchart LR
O([Owner]) -->|creates| R[Repair request<br/>photos, urgency, access]
R -->|invites one person| V([Vendor])
R -->|invites one person| H([Helper])
V -->|bid| Q[Owner approves quote]
Q --> W[Work sessions<br/>before and after proof]
W --> C[Closeout]
C -->|owner approves| D[Complete + billing record]
D --> Hist[(Property history<br/>PDF, CSV, backup)]
H -->|updates| R
Key steps (status changes, invites, quote and closeout decisions) write an entry to a decision log, and helpers only ever see the request shared with them.
| Guided intake | Request detail | Vendor portal | Maintenance calendar |
|---|---|---|---|
| I want to… | Go to |
|---|---|
| Start with the visual and narrative system guide | PROJECT_SYSTEM_GUIDE.md |
| Understand the project in 10 minutes | docs/README.md → Problem → System map |
| See how each feature works (algorithm, pseudocode, flowchart) | docs/04-algorithms/ |
| Find a file | Code map |
| Read the latest review (PDF) | docs/review/ |
| Deploy or operate it | Deployment · P0 rollout runbook |
| See the history of changes | Build log |
| Read the previous (long) README | docs/history/README-2026-09-18.md |
npm install
cp .env.local.example .env.local # fill in DATABASE_URL, BLOB_READ_WRITE_TOKEN, AUTH_SECRET, SEED_PASSWORD...
npm run db:migrate
npm run db:seed # demo accounts; needs SEED_PASSWORD unless the DB is on localhost (see docs/DEPLOYMENT.md)
npm run dev
Before deploying:
npm run poc:ready # checks env values, including private file storage
npm run verify # lint, typecheck, tests, audit, schema drift, build
The curated investor demo (npm run db:seed:investor) needs
INVESTOR_DEMO_PASSWORD set. The password is shared privately and never
committed.
Next.js 16 (App Router, Server Actions, TypeScript) · Neon Postgres + Drizzle ORM · Auth.js v5 · Vercel Blob · Resend · Vercel Cron · Tailwind CSS v4 · Vitest · Playwright.
This is the fourth iteration. It was rebuilt from a static Firebase MVP onto a real server boundary with relational data and server-side authorization (why it was rebuilt).