尚未检测到更新。GitHub 发布版本后会显示在这里。
按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
Tickets, Doku, Zeiterfassung und Kundengespräche an einem Ort, durchsuchbar per KI. Für Softwarefirmen mit Kundenprojekten. Open Source: auf deinem eigenen Server oder in unserer Cloud in Deutschland.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权，自行管理介绍，无需管理员批准。
登录并生成验证文件，在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件，即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录，将前往登录页面。登录后请回到此处，再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify，即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
The dispute-grade evidence layer for short-term-rental hot-tub turnovers (B2B SaaS).
TrackTub captures tamper-evident proof of each turnover — server-timestamped photos and an
audit log — so operators can resolve guest disputes and prove the tub was serviced.
Build-first. The app in apps/web is a clickable thin-MVP demo
(Next.js 15, localStorage, no backend) that serves as the UX/design reference.
v1 is a schema-first rebuild on Supabase (Postgres + RLS + Auth + Storage + server
timestamps + audit log), built on feature branches.
Quality gate (run before opening a PR; CI runs the same):查看完整 README ↗The dispute-grade evidence layer for short-term-rental hot-tub turnovers (B2B SaaS). TrackTub captures tamper-evident proof of each turnover — server-timestamped photos and an audit log — so operators can resolve guest disputes and prove the tub was serviced.
Build-first. The app in apps/web is a clickable thin-MVP demo
(Next.js 15, localStorage, no backend) that serves as the UX/design reference.
v1 is a schema-first rebuild on Supabase (Postgres + RLS + Auth + Storage + server
timestamps + audit log), built on feature branches.
| Path | What |
|---|---|
apps/web | Next.js 15 app (the demo today; v1 backend lands here) |
branding/ | Single brand package — logo/icon/social assets (SVG + PNG), spec, tokens, generator |
docs/ | PRD (product source of truth), design specs, validation collateral |
.github/workflows/ci.yml | CI: install → lint → typecheck → build |
cd apps/web
npm install
npm run dev # http://localhost:3000
Quality gate (run before opening a PR; CI runs the same):
npm run lint && npm run typecheck && npm run build
Code flows one direction via pull requests — never push directly to a protected branch:
feature branch → main (trunk) → test (staging) → prod (production)
main → test → prod move only via fast-forward promotion PRs.
Read CLAUDE.md first — it holds the contributor/agent guide, the golden
rules (one worktree = one branch = one task), and the full worktree → PR → promotion
workflow. Product decisions live in docs/PRD.md; the visual spec lives
in branding/.