尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
An AI-assisted hiring app for main-street small businesses. An employer posts a
job, candidates apply and go through a screening flow (quiz, chat/voice
interview, portfolio, etc.) guided by an in-app assistant called Ava, and the
employer reviews a scored pipeline, messages candidates, and sends documents for
signature. Candidates never see the words "AI" or "Ava" — the copy stays plain
and everyday.
Live at https://hireflownow.com.檢視完整 README ↗An AI-assisted hiring app for main-street small businesses. An employer posts a job, candidates apply and go through a screening flow (quiz, chat/voice interview, portfolio, etc.) guided by an in-app assistant called Ava, and the employer reviews a scored pipeline, messages candidates, and sends documents for signature. Candidates never see the words "AI" or "Ava" — the copy stays plain and everyday.
Live at https://hireflownow.com.
api/*.mjs serverless functions), auto-deploys mainSee docs/BACKEND-SCHEMA.md for the live database schema and docs/ARCHITECTURE.md for how the frontend talks to it.
npm install
npm run dev
# http://localhost:8080
Requires VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY in .env,
pointing at the Supabase project in CLAUDE.md.
Before committing, all of the following must pass:
npm run build
npm run typecheck:ratchet # type errors must never exceed the recorded baseline
node scripts/guardrails.mjs # repo-specific rules: design tokens, safety invariants, etc.
node scripts/*.test.mjs # unit tests
node scripts/*pglite*.mjs # RLS/RPC/trigger tests against a real Postgres (PGlite)
Any edge function you add or change should also pass deno check.
Guardrail failures come with a fix-it style explanation in scripts/guardrails.mjs;
add new guards under scripts/guards/ per scripts/guards/README.md (each guard
must fail on the old code and pass on the fix).
| Doc | What it covers |
|---|---|
docs/LAUNCH-PLAN.md | The current phased plan, the rules for working it, and the progress log |
docs/ARCHITECTURE.md | Frontend ↔ Supabase schema shape, layer map |
docs/BACKEND-SCHEMA.md | Live tables, storage buckets, key RPCs |
docs/MIGRATION-HISTORY.md | Repo migration file ↔ live migration version mapping |
docs/CANDIDATE-FLOW.md | Candidate-facing UX flow and routes |
docs/MODEL-DEADLINES.md | Which AI model each edge function uses, and how to swap one |
docs/DISTRIBUTION.md | Where a published job actually gets distributed, automatically |
docs/DOCUMENT-SIGNING.md | Document-signing flow and integrity guarantees |
docs/TRUSTED-RESULTS.md | Server-trusted vs self-reported screening step results |
Push to main — Vercel auto-deploys the frontend. Database migrations and edge
functions are deployed separately with the Supabase CLI; see CLAUDE.md for the
commands and the pacing rule for the Management API.
BRANDING.md |
| App icon / brand asset source of truth |
CLAUDE.md | Project reference: hosting, Supabase project, env vars, current known gaps |