create-velox-app 0.7.4 → 0.7.6

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # create-velox-app
 
+## 0.7.6
+
+### Patch Changes
+
+- feat(router): custom access levels for the Resource API + advanced Architectural Patterns
+
+## 0.7.5
+
+### Patch Changes
+
+- fix(cli): address sync command review findings
+
 ## 0.7.4
 
 ### Patch Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-velox-app",
-  "version": "0.7.4",
+  "version": "0.7.6",
   "description": "Project scaffolder for VeloxTS framework",
   "type": "module",
   "main": "dist/index.js",

package/src/templates/source/api/procedures/profiles.auth.ts

@@ -5,7 +5,7 @@
  * - Public: GET /api/profiles/:id → { id, name }
  *     Uses handler-level projection: resource(data, Schema.public)
  * - Authenticated: GET /api/profiles/:id/full → { id, name, email }
- *     Uses procedure-level auto-projection: .resource(Schema.authenticated)
+ *     Uses procedure-level auto-projection: .expose(Schema.authenticated)
  */
 
 import {
@@ -37,7 +37,7 @@ export const profileProcedures = procedures('profiles', {
   // Handler-level projection: resource(data, Schema.public) returns projected data directly
   getProfile: procedure()
     .input(z.object({ id: z.string().uuid() }))
-    .resource(UserProfileSchema.public)
+    .expose(UserProfileSchema.public)
     .query(async ({ input, ctx }) => {
       const user = await ctx.db.user.findUnique({ where: { id: input.id } });
       if (!user) throw new NotFoundError(`User '${input.id}' not found`);
@@ -45,12 +45,12 @@ export const profileProcedures = procedures('profiles', {
     }),
 
   // Authenticated: GET /api/profiles/:id/full → { id, name, email }
-  // Procedure-level auto-projection: .resource(Schema.authenticated) auto-projects the return value
+  // Procedure-level auto-projection: .expose(Schema.authenticated) auto-projects the return value
   getFullProfile: procedure()
     .rest({ method: 'GET', path: '/profiles/:id/full' })
     .guardNarrow(authenticatedNarrow)
     .input(z.object({ id: z.string().uuid() }))
-    .resource(UserProfileSchema.authenticated)
+    .expose(UserProfileSchema.authenticated)
     .query(async ({ input, ctx }) => {
       const user = await ctx.db.user.findUnique({ where: { id: input.id } });
       if (!user) throw new NotFoundError(`User '${input.id}' not found`);

package/src/templates/source/root/.claude/skills/veloxts/GENERATORS.md

@@ -2,45 +2,49 @@
 
 ## AI Agent Recommended Workflow
 
-When creating new entities, the **recommended approach** is:
+### Multiple Models: `velox sync` (Recommended)
+
+When you have several Prisma models and want schemas + procedures for all of them:
+
+1. **Design all Prisma models** in `prisma/schema.prisma`
+2. **Run `velox sync`** to generate everything interactively
+
+```bash
+# Push schema to database, then sync all models
+pnpm db:push
+velox sync              # Interactive: choose output strategy + CRUD per model
+velox sync --force      # Non-interactive: generate all with defaults
+velox sync --dry-run    # Preview what would be generated
+```
+
+This generates Zod schemas, CRUD procedures, and router registrations for every model in one shot.
+
+### Single Model: `velox make namespace`
+
+When adding a single new model to an existing project:
 
 1. **Design and add the Prisma model** directly to `prisma/schema.prisma`
 2. **Run `velox make namespace EntityName`** to generate procedures
 
-This ensures complete, production-ready code because the AI can design the full schema based on requirements.
-
 ```bash
-# Example: Creating a Post entity
-
-# Step 1: AI adds model to prisma/schema.prisma
-model Post {
-  id        String   @id @default(uuid())
-  title     String
-  content   String
-  published Boolean  @default(false)
-  authorId  String
-  author    User     @relation(fields: [authorId], references: [id])
-  createdAt DateTime @default(now())
-  updatedAt DateTime @updatedAt
-  @@map("posts")
-}
-
-# Step 2: Generate procedures for the existing model
+# Example: Adding a Post entity to an existing project
 velox make namespace Post --example
 ```
 
 ## Decision Tree: Which Generator?
 
 ```
-Do you need a new database entity?
-├── YES (AI workflow) → 1. Design Prisma model in schema.prisma
-│                       2. velox make namespace EntityName --example
-│                       Creates: Schema + Procedures for existing model
+Do you need schemas + procedures for your Prisma models?
+├── MULTIPLE MODELS → velox sync
+│                     Generates all models interactively (or --force for defaults)
+│
+├── SINGLE MODEL (existing) → velox make namespace EntityName --example
+│                              Creates: Schema + Procedures for one model
 │
-├── YES (Interactive) → velox make resource EntityName -i
-│                       Prompts for fields, creates everything
+├── SINGLE MODEL (new) → velox make resource EntityName -i
+│                         Prompts for fields, creates everything
 │
-└── NO → What do you need?
+└── NOT A MODEL → What do you need?
          ├── Single API endpoint → velox make procedure
          ├── Validation schema only → velox make schema
          ├── Database model only → velox make model
@@ -58,16 +62,17 @@ Do you need a new database entity?
 
 | Generator | Creates | Use When |
 |-----------|---------|----------|
-| `namespace` | Schema + Procedures + Tests | **AI agents** or existing Prisma model |
+| `sync` | Schema + Procedures for **all** models | **Recommended** for multi-model projects |
+| `namespace` | Schema + Procedures + Tests | Single existing Prisma model |
 | `resource -i` | Prisma + Schema + Procedures + Tests | **Human interactive** field definition |
 | `resource` | Scaffolds with TODOs | Quick start (fields needed manually) |
 | `procedure` | Procedures (inline schemas) | Single endpoint, quick prototype |
 | `schema` | Zod schema file | Standalone validation |
 | `model` | Prisma model | Database-only change |
 
-## Namespace Generator [AI RECOMMENDED]
+## Namespace Generator (Single Model)
 
-Best choice for AI agents. Works with models you've already defined.
+Best choice when adding a single model to an existing project. Works with models you've already defined.
 
 ```bash
 # After adding model to schema.prisma:
@@ -260,35 +265,27 @@ velox make task SendDailyDigest --cron="0 9 * * *"
 
 ## Common Workflows
 
-### New Feature: Blog Posts (AI Agent)
+### Sync All Models (Recommended for New Projects)
 
 ```bash
-# 1. Design Prisma model directly in schema.prisma
-model Post {
-  id        String   @id @default(uuid())
-  title     String
-  slug      String   @unique
-  content   String
-  excerpt   String?
-  published Boolean  @default(false)
-  authorId  String
-  author    User     @relation(fields: [authorId], references: [id])
-  createdAt DateTime @default(now())
-  updatedAt DateTime @updatedAt
-  @@map("posts")
-}
-
-# 2. Generate procedures for the model
-velox make namespace Post --example
-
-# 3. Push database changes
+# 1. Design all Prisma models in schema.prisma
+# 2. Push schema to database
 pnpm db:push
 
-# 4. (Optional) Seed sample data
-velox make seeder PostSeeder
+# 3. Generate schemas + procedures for all models
+velox sync
+```
+
+### New Feature: Single Model (AI Agent)
+
+```bash
+# 1. Design Prisma model directly in schema.prisma
+# 2. Push schema and generate for that one model
+pnpm db:push
+velox make namespace Post --example
 ```
 
-### New Feature: Blog Posts (Human Interactive)
+### New Feature: Single Model (Human Interactive)
 
 ```bash
 # 1. Interactive field definition

package/src/templates/source/root/.claude/skills/veloxts/SKILL.md

@@ -16,23 +16,23 @@ I help you build type-safe full-stack applications with VeloxTS. Ask me about:
 
 ## Quick Decision: Which Generator?
 
-**"I want to create a new database entity"**
+**"I have multiple Prisma models and want schemas + procedures for all of them"**
 ```bash
-velox make resource Post        # RECOMMENDED - creates everything
+velox sync                      # RECOMMENDED - interactive, all models at once
+velox sync --force              # Skip prompts, generate everything with defaults
 ```
-Creates: Prisma model + Zod schema + Procedures + Tests + Auto-registers
+Generates: Zod schemas + CRUD procedures + router registration for every model
 
-**"I have an existing Prisma model"**
+**"I want to add a single new entity"**
 ```bash
-velox make namespace Order      # For existing models
+velox make resource Post        # Creates everything from scratch
+velox make namespace Order      # For existing Prisma models only
 ```
-Creates: Zod schema + Procedures (no Prisma injection)
 
 **"I need a single endpoint"**
 ```bash
 velox make procedure health     # Quick single procedure
 ```
-Creates: Procedure file with inline schemas
 
 See [GENERATORS.md](GENERATORS.md) for detailed guidance.
 
@@ -209,8 +209,9 @@ pnpm db:studio              # Open Prisma Studio
 pnpm velox migrate status   # Check migration status
 
 # Code Generation
-pnpm velox make resource Post --crud      # Full resource
-pnpm velox make namespace Order           # Namespace + schema
+pnpm velox sync                           # All models at once (recommended)
+pnpm velox make resource Post --crud      # Full resource (single model)
+pnpm velox make namespace Order           # Existing model (single)
 pnpm velox make procedure health          # Single procedure
 
 # Seeding

package/src/templates/source/root/CLAUDE.auth.md

@@ -154,9 +154,9 @@ export const userProcedures = procedures('users', {
 });
 ```
 
-**When to use `.output()` vs `.resource()`:**
+**When to use `.output()` vs `.expose()`:**
 - `.output(zodSchema)` - Same fields for all users
-- `resourceSchema()` + `resource()` - Different fields per role
+- `.expose(resourceSchema)` - Different fields per role (resource projection)
 
 ## Prisma 7 Configuration
 

package/src/templates/source/root/CLAUDE.default.md

@@ -144,9 +144,9 @@ export const userProcedures = procedures('users', {
 });
 ```
 
-**When to use `.output()` vs `.resource()`:**
+**When to use `.output()` vs `.expose()`:**
 - `.output(zodSchema)` - Same fields for all users
-- `resourceSchema()` + `resource()` - Different fields per role
+- `.expose(resourceSchema)` - Different fields per role (resource projection)
 
 ## Prisma 7 Configuration
 

package/src/templates/source/root/CLAUDE.trpc.md

@@ -165,9 +165,9 @@ export const userProcedures = procedures('users', {
 });
 ```
 
-**When to use `.output()` vs `.resource()`:**
+**When to use `.output()` vs `.expose()`:**
 - `.output(zodSchema)` - Same fields for all users
-- `resourceSchema()` + `resource()` - Different fields per role
+- `.expose(resourceSchema)` - Different fields per role (resource projection)
 
 ## Prisma 7 Configuration
 

package/src/templates/source/rsc-auth/src/api/procedures/profiles.ts

@@ -5,7 +5,7 @@
  * - Public: GET /api/profiles/:id → { id, name }
  *     Uses handler-level projection: resource(data, Schema.public)
  * - Authenticated: GET /api/profiles/:id/full → { id, name, email }
- *     Uses procedure-level auto-projection: .resource(Schema.authenticated)
+ *     Uses procedure-level auto-projection: .expose(Schema.authenticated)
  */
 
 import { authenticatedNarrow } from '@veloxts/auth';
@@ -33,7 +33,7 @@ export const profileProcedures = procedures('profiles', {
   // Handler-level projection: resource(data, Schema.public) returns projected data directly
   getProfile: procedure()
     .input(z.object({ id: z.string().uuid() }))
-    .resource(UserProfileSchema.public)
+    .expose(UserProfileSchema.public)
     .query(async ({ input }) => {
       const user = await db.user.findUnique({ where: { id: input.id } });
       if (!user) {
@@ -43,12 +43,12 @@ export const profileProcedures = procedures('profiles', {
     }),
 
   // Authenticated: GET /api/profiles/:id/full → { id, name, email }
-  // Procedure-level auto-projection: .resource(Schema.authenticated) auto-projects the return value
+  // Procedure-level auto-projection: .expose(Schema.authenticated) auto-projects the return value
   getFullProfile: procedure()
     .rest({ method: 'GET', path: '/profiles/:id/full' })
     .guardNarrow(authenticatedNarrow)
     .input(z.object({ id: z.string().uuid() }))
-    .resource(UserProfileSchema.authenticated)
+    .expose(UserProfileSchema.authenticated)
     .query(async ({ input }) => {
       const user = await db.user.findUnique({ where: { id: input.id } });
       if (!user) {