ことのあめ（旧 PolyLinga）

例文の雨を浴びて、使える言葉へ。同じかたちの文が音声付きで雨のように降ってきて、共通しているところに自分で気づき、 自分でも言ってみて AI に直してもらい、忘れてもまた降ってくる中で出会い直す学習アプリ。思想は CONCEPT.md。

Setup

npm install
cp .env.example .env.local   # fill in the values
node --env-file=.env.local scripts/migrate.mjs supabase/migrations/20261003000000_polylinga_core.sql
node --env-file=.env.local scripts/migrate.mjs supabase/migrations/20261008000000_polylinga_v2.sql
node --env-file=.env.local scripts/migrate.mjs supabase/migrations/20261008010000_library_review.sql
node --env-file=.env.local scripts/migrate.mjs supabase/migrations/20261009000000_shower.sql
node --env-file=.env.local scripts/seed.mjs
npm run dev

Growing the shower

1. scripts/draft-library.mjs drafts new functions from scripts/library/functions.json; scripts/expand-library.mjs adds more chat-style sentences to existing ones. Both create drafts.
2. scripts/review-library.mjs adds an AI second opinion ("要確認" notes with suggested fixes).
3. scripts/publish-reviewed.mjs publishes what passed. Flagged items wait in /admin/library (your address must be in ADMIN_EMAILS) for a person to fix or reject.
4. scripts/generate-audio.mjs pre-generates audio for newly published sentences.

Sign-in (the Supabase project is shared with the old app)

The project's auth emails, templates, Site URL (https://polylinga.app) and redirect list belong to the old app, and its Confirm email is off. So this app does its own:

• Sign-up and a forgotten password (src/app/login/actions.ts): the server makes the account unconfirmed (generateLink), and Resend (src/lib/email.ts, RESEND_API_KEY, the old app's verified polylinga.app domain) sends ことのあめ's mail with a link straight to /auth/confirm?token_hash=…. It works when opened in another browser, and no redirect list is involved. Counted as emails in pl_daily_usage (5 per address, 80 a day in all).
• Google: ことのあめ's own OAuth client (NEXT_PUBLIC_GOOGLE_CLIENT_ID, in a Google Cloud project whose consent screen says ことのあめ), Google Identity Services, then signInWithIdToken. Its client ID must be added in Supabase → Authentication → Sign In / Providers → Google → Client IDs, after the old app's (which stays first). Without it the button falls back to the shared redirect sign-in, which only comes back to addresses in the redirect list.
• Anyone can still create a confirmed account through the Supabase API itself (Confirm email is off for the old app); the global daily limits in src/lib/metering.ts are the brake.
• Anonymous sign-ins off. The app never uses them (and ignores anonymous users).
• Sisters for Korean speakers (글씨앗, 말씨앗; lang: "ko" in src/lib/sisters.ts): on the way to them, the login, sign-up, confirmation mail, name, つなぐ and forgotten-password pages and mails are in Korean (src/lib/i18n/sign-in.ts, chosen from the /connect in next by connectLang). Everything else stays Japanese.

Replacing the old app on polylinga.app

• Stop the old deployment first. Its weekly cron empties the tts-audio bucket; this app uses pl-audio, but nothing should keep running against the shared project.
• public/sw.js unregisters the old app's service worker for returning visitors, and old URLs redirect (next.config.ts, src/app/app/[...rest]).
• Google sign-in does not work inside the old iOS (Capacitor) WebView; email and password does.

polylinga

polylinga