ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證a supportive, calm, and highly intelligent academic tutor app
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
A supportive, calm, and highly intelligent academic tutor app built for students.
Phase 0 — Foundation Hardening: Closed (2026-05-06)
See docs/phases/foundation-hardening-phase-0.md
CI fails the PR if any gate is violated. Raise floors, never lower.
Run locally: python -m pytest backend/tests/ -v --cov=backend --cov-report=term --cov-fail-under=25檢視完整 README ↗A supportive, calm, and highly intelligent academic tutor app built for students.
Phase 0 — Foundation Hardening: Closed (2026-05-06)
See docs/phases/foundation-hardening-phase-0.md
Live status: CURRENT_STATE.md (single source of truth for where the project stands).
| Layer | Technology |
|---|---|
| Frontend | React 19 + CRA (Craco) + Tailwind CSS |
| UI | shadcn/ui (New York) + Radix UI |
| Auth | Clerk (sole identity provider) |
| Backend | FastAPI (Python) |
| Database | Supabase Postgres (schema-as-code in supabase/migrations/) |
| Payments | Stripe |
| Hosting | Vercel (frontend) + Render (API, render.yaml) |
# 1. Clone the repo
git clone https://github.com/jeremiahvanwagner-droid/Your-Student-Companion-main.git
cd Your-Student-Companion-main
# 2. Install dependencies (--legacy-peer-deps required for React 19)
npm install --legacy-peer-deps
# 3. Copy environment template and fill in your keys
cp .env.example .env.local
# 4. Start the dev server
npm start
| Command | Description |
|---|---|
npm start | Start dev server (port 3000) |
npm run build | Production build → build/ |
npm test | Run tests in watch mode |
npm run test:coverage | Run tests + enforce coverage thresholds |
CI fails the PR if any gate is violated. Raise floors, never lower.
| Metric | Floor |
|---|---|
| Statements | 10% |
| Branches | 15% |
| Functions | 10% |
| Lines | 10% |
Run locally: npm run test:coverage
| Metric | Floor |
|---|---|
| Lines | 25% |
Run locally: python -m pytest backend/tests/ -v --cov=backend --cov-report=term --cov-fail-under=25
db-migrate CI job)Every PR also rebuilds the database from scratch on an ephemeral local Supabase
stack (supabase start → supabase db reset), runs
backend/scripts/audit_supabase_schema.py --expect-project-ref local, lints the
migrations and asserts the RLS/grant posture (zero policies in public;
anon has no table privileges; service_role does). See
docs/runbooks/database.md.
The schema is code: supabase/migrations/ is the only place DDL lives, and
the only way DDL reaches any Supabase project is supabase db push from a merged
PR. Seeds (catalog, subscription plans, feature flags, the NY Regents Algebra I
reference exam) are idempotent migration files in the same folder;
supabase/seed.sql is local-only.
apply_migration tool and the
dashboard SQL Editor are banned for schema changes. The project that preceded
this rule was deleted in July 2026 with MCP-applied, never-committed schema in
it (see CURRENT_STATE.md S-INCIDENT-DB-001); nothing in the repo could
rebuild it.auth.users FK, Supabase Auth sign-ups disabled,
RLS enabled on every table with no policies (deny-all for anon /
authenticated); the backend talks to Postgres with the service-role key and
enforces ownership by user_id filters.backend/migrations/ (the pre-rebuild SQL files) is archived under
docs/archive/legacy-migrations/ for history only — never apply those files.├── src/ # React frontend
│ ├── components/ # UI components (shadcn/ui, layout, features)
│ ├── pages/ # Route pages
│ ├── lib/ # Utilities, API clients, age gate, analytics, onboarding
│ ├── hooks/ # Custom React hooks
│ ├── context/ # React context providers
│ └── utils/ # Pure utility functions
├── backend/ # FastAPI Python backend (routes/, lib/, scripts/, tests/)
├── supabase/ # Supabase CLI config + migrations/ (the schema) + seed.sql
├── docs/ # Runbooks, strategy, phases, scope, archived legacy migrations
├── public/ # Static assets and PWA manifest
├── render.yaml # Render Blueprint for the API + weekly cron
└── .github/workflows/ # CI (build, backend-test, db-migrate) + nightly db-backup
See .env.example for the full list of required variables.
Private — all rights reserved.