How tsukutteasobo/asobo works
Project Type and Purpose
• This is a Monorepo offering a Nuxt 3 + Nuxt UI application template.
• It includes:
• A front-end SSR/UI project (src/app)
• A server/API module (src/server)
• Shared TypeScript types (src/shared)
• Scaffolding tooling via scaffdog in .config/.scaffdog
• Workspace management with pnpm
Main Components to Reflect
1. Developer / CLI Layer
• Runs commands: pnpm ui dev, pnpm gen:cm, nr gen:api
• Invokes pnpm / antfu/ni, scaffdog
2. Code-Generation Engine
• .config/.scaffdog reads templates, outputs new components/pages/api files under src/app/components, src/app/pages, or src/server
3. Monorepo Packages (pnpm Workspace)
• app
• Nuxt 3 application (src/app/nuxt.config.ts, app.vue, app.config.ts)
• UI layer: components/ui, feature components: components/feature
• Routing/pages: pages
• Layouts & assets
• server
• TypeScript API endpoints, business logic (under src/server)
• shared
• Shared TypeScript types (under src/shared/types)
4. Framework & Build Tools
• Nuxt 3 (SSR + Vite under the hood)
• Nuxt UI component library
• Vite bundler/dev server
• Vitest, ESLint for testing & linting
5. Browser / User
• Receives rendered pages from Nuxt SSR or CSR of Vue UI
Relationships & Data Flows
• Developer → CLI → Scaffdog → Code artifacts in Monorepo
• Developer → CLI → pnpm workspace scripts → Nuxt/Vite →
a) Builds front-end bundle → Browser
b) Serves API routes → Server module
• app ↔ server call via internal HTTP calls or Nuxt server routes
• app & server both consume types from shared
Architectural Patterns & Principles
• Monorepo Separation of Concerns: packages for UI, server, shared
• Server-Side Rendering with Nuxt + optional CSR
• Code Generation via scaffdog for consistency & rapid prototyping
• Workspace Tooling ensures single lockfile & cross-package linking