Fullstack Monorepo Boilerplate

• What it is: despite the folder name rentcar, this is the user's personal full-stack boilerplate (package.json name: fullstack_mono, README — "Production-ready fullstack TypeScript monorepo"). A Turborepo with 3 apps (web, admin, api) and 9 reusable packages. Includes PROMO-PLAN.md — a marketing plan to launch DevTools (10 browser-side utilities: JSON formatter, Base64, JWT, regex tester, text diff, UUID, etc.) — likely apps/web.
• Type / status / role: web-app/boilerplate (monorepo) / active / solo — all 25 commits authored by Davron Yuldashev.
• Activity period: 2025-11-10 → 2026-03-26 (~4.5 months), 25 commits.

• Languages: TypeScript (strict), Bun 1.3 runtime.
• **Monorepo (Turborepo + Bun workspaces @workspace/*):**
• apps/: web (Next.js 16 — likely the DevTools site), admin (Next.js 16 dashboard), api (Elysia 1.4 + Swagger + CORS + cookie).
• packages/: auth (Better Auth — access-control/RBAC, server/client split, auth-schema), db (Drizzle + Postgres), cache (Redis/ioredis), cli (interactive setup CLI mycli), email, entities (shared domain entities/types), ui (shadcn/ui), eslint-config, typescript-config.
• Key features (per README/code): Eden Treaty — E2E type safety frontend↔Elysia; Better Auth + RBAC (access-control.ts); interactive setup CLI (wizard: DB config, auth-secret generation, db:push, admin user creation); i18n (ru/en/uz, next-intl); shadcn/ui + glassmorphism design; Redis sessions.
• Infra/deploy: Turborepo (build/dev/lint), Prettier, .mcp.json (MCP config — development with MCP tooling), .env.example. Postgres 16 + Redis.

Solo, 25 commits. By structure/README:

• Monorepo scaffold: 3 apps + 9 packages with clear separation (auth/db/cache/email/entities/ui).
• Better Auth + RBAC layer (packages/auth: access-control, auth-schema, server/client, config).
• Elysia API wired up to shared packages (@workspace/auth|cache|db|email|entities) + Swagger.
• Interactive CLI (packages/cli: cli.ts, utils/setup.ts) — automates onboarding (env, secrets, DB schema, admin user).
• DevTools web app (per PROMO-PLAN) — browser-side dev utilities (client-side, privacy-friendly).
• Extensive documentation: README 15 KB, CLAUDE.md 20 KB, PROMO-PLAN.md.

Confirmed by manifests/structure/README.

• E2E type safety via Eden Treaty → the frontend calls the Elysia API with types inferred from the backend, no codegen. The same strong pattern as in managers/deutsch — but here as a reusable template.
• RBAC on Better Auth (packages/auth/access-control.ts, server/client split) → a role model out of the box in the starter.
• DX-first: interactive setup CLI (packages/cli/mycli) → setup wizard (DB, auth-secret, migrations, admin user) — developer experience as a first-class concern, not just "clone and edit .env."
• Clean package boundaries → auth/cache/db/email/entities/ui as separate @workspace/* — maximal reuse and good monorepo hygiene.
• Privacy-by-design DevTools → utilities run entirely in the browser (client-side), without sending data to a server (both a marketing and engineering argument in PROMO-PLAN).

• Sessions found: 0 in the local Claude Code sessions store (no match by the full path key).
• Indirect signals: .mcp.json at the root + a large CLAUDE.md (20 KB) — development with MCP/Claude tools, but the CC transcripts weren't preserved.
• AI workflow patterns: no transcripts; the presence of .mcp.json indicates a configured MCP environment.

• Solo: 3 apps + 9 packages in a single Turborepo.
• Bleeding-edge stack: Next.js 16, Elysia, Better Auth, Drizzle, Bun, shadcn — exactly the stack the user declares as his core.
• Interactive setup CLI, i18n in 3 languages, E2E types.
• Ready go-to-market plan (PROMO-PLAN: Reddit tiers, post templates).