you, after a meetup, into your phone:
  > "met sarah from acme at the rust meetup, she leads their edge runtime team,
     send her the github link tomorrow morning"

wingmic, instantly:
  ✓ committed to graph
    → person:    Sarah  (Lead · Edge runtime @ Acme)
    → event:     Rust meetup  (canonical, shared)
    → topics:    rust · edge runtime
    → action:    send github link · tomorrow 9:00 AM

you, three weeks later:
  > "who at acme works on rust?"

  ↪ found 1 match in 0.3s:
    • Sarah  ·  Lead · Edge runtime  ·  Acme  ·  met at Rust meetup
      "she leads their edge runtime team, send her the repo"

apps/web              ← static landing → wingmic.xyz (Cloudflare Pages)
apps/app              ← dynamic product → app.wingmic.xyz (Railway, Node.js)
packages/
  brand               ← logos, favicons, OG, manifest
  design-tokens       ← Tailwind preset + token TS exports
  db                  ← Drizzle schema + libSQL + migrations
  extractor           ← entity-detection pipeline + eval harness
  config/{tsconfig,eslint,vitest}
design/               ← canonical mocks (read-only)
docs/                 ← architecture.md, deploy.md, packages.md, superpowers/
CLAUDE.md             ← Claude Code project context
turbo.json

Set up wingmic for me on this machine. The repo is github.com/Ayaan2907/wingmic — an
open-source voice-first networking memory app.

Do this in order, stopping for me at each step:

  1. Check if Bun (>=1.3) and Node (>=20) are installed. Install Bun if missing
     via `curl -fsSL https://bun.sh/install | bash`.
  2. Clone https://github.com/Ayaan2907/wingmic.git into ./wingmic if not already.
  3. Run `bun install` from the repo root.
  4. Copy apps/app/.env.example to apps/app/.env.local.
  5. Walk me through obtaining the required secrets per docs/deploy.md § 2:
       - TURSO_DB_URL + TURSO_AUTH_TOKEN  (turso CLI)
       - BETTER_AUTH_SECRET                (openssl rand -base64 48)
       - BETTER_AUTH_URL                   (http://localhost:3211 for local dev)
       - RESEND_API_KEY                    (resend.com — domain must be verified)
       - OPENROUTER_API_KEY                (openrouter.ai — LLM + embeddings)
       - ASSEMBLYAI_API_KEY                (assemblyai.com — hosted ASR)
     Stop and ask me at each one — do NOT generate or fetch any keys yourself.
     For local dev only OPENROUTER_API_KEY and ASSEMBLYAI_API_KEY are required;
     the rest can be left blank with safe defaults.
  6. Once .env.local is filled, run `bun run db:apply` to create
     a local SQLite at apps/app/local.db.
  7. Run `bun run dev:app` from the repo root. Show me http://localhost:3211 once it's up.
  8. Tell me to sign in: visit /signin, type any email, and check the dev-server
     console — the magic link is always logged there (email sends only when RESEND_API_KEY is set).

Brand voice rule: when committing or summarizing, do NOT add "Co-Authored-By: Claude"
or any AI co-author trailer. Authorship is mine.

Help me make my first contribution to wingmic (github.com/Ayaan2907/wingmic).

  1. Read these in order — they're the maintainer contract:
       - README.md
       - CONTRIBUTING.md
       - docs/architecture.md
       - design/design-system.md (only if the work is UI / brand-voice)
  2. List open issues tagged `good first issue`:
       gh issue list --label "good first issue" --state open
  3. Ask me which issue number I want to tackle. Don't pick one for me.
  4. Read the issue body in full. Identify exact files to touch.
  5. Branch from staging: `git checkout staging && git pull && git checkout -b feat/<short-name>`
     (or fix/, docs/, chore/) per CONTRIBUTING.md branch conventions.
  6. Make the change. Add or update Vitest or Playwright tests for new behavior.
  7. Run the local CI checks before committing:
       - bun run typecheck
       - bun --filter @wingmic/web lint
       - bun run test
       - bun run build
     All must pass.
  8. Commit using Conventional Commits (e.g. `feat(capture): add text fallback`).
     Do NOT add "Co-Authored-By: Claude" or any AI trailer to the commit message.
  9. Push and open a PR with the template-required fields filled in. Reference
     the issue number with `closes #N`.
 10. Stop and let me review before pushing or merging.

Stay focused on the chosen issue. If you spot unrelated improvements, file
them as separate issues — don't pile them into the PR.