Skip to content

chore(dev): lvh.me dev origins, db:types script, generated Supabase types, sync impeccable skill tooling - #340

Merged
guillermoscript merged 1 commit into
masterfrom
chore/dev-tooling-and-generated-types
Jul 2, 2026
Merged

chore(dev): lvh.me dev origins, db:types script, generated Supabase types, sync impeccable skill tooling#340
guillermoscript merged 1 commit into
masterfrom
chore/dev-tooling-and-generated-types

Conversation

@guillermoscript

Copy link
Copy Markdown
Owner

What & why

Unrelated dev-environment/tooling changes that accumulated alongside the product/course creation wizard work (PR #339) — split out so that PR stays scoped to the wizard feature.

Changes

  • next.config.tsallowedDevOrigins: ['lvh.me', '*.lvh.me'] so Next 16 dev doesn't reject the local multi-tenant subdomains (*.lvh.me) as untrusted cross-origin requests
  • package.json — new db:types script (supabase gen types typescript --linked --schema public > lib/database.types.ts)
  • lib/database.types.ts — generated Supabase database types (previously no generated types existed in this repo)
  • .gitignore — exclude local Solana devnet wallet keypairs (scripts/.devnet-*.json); these contain raw private keys and were never meant to be committed
  • Sync the impeccable design-review skill + hooks across .claude/, .codex/, .github/skills/, .opencode/ agent config dirs

Testing

  • npx tsc --noEmit passes
  • npm run build

…cable skill tooling

- next.config.ts: allowedDevOrigins for lvh.me subdomains so Next 16 dev
  doesn't reject multi-tenant subdomain requests as cross-origin
- package.json: add db:types script + generated lib/database.types.ts
  (Supabase typed client)
- sync the impeccable design-review skill/hooks across .claude, .codex,
  .github, .opencode agent config dirs
- .gitignore: exclude local Solana devnet wallet keypairs (private keys)

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@guillermoscript
guillermoscript merged commit 9dd4c75 into master Jul 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant