@famgia/omnify-laravel 0.0.110 → 0.0.112

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@famgia/omnify-laravel",
-  "version": "0.0.110",
+  "version": "0.0.112",
   "description": "Laravel migration and TypeScript type generator for omnify-schema",
   "type": "module",
   "main": "./dist/index.js",
@@ -25,9 +25,9 @@
     "README.md"
   ],
   "dependencies": {
-    "@famgia/omnify-types": "0.0.99",
-    "@famgia/omnify-core": "0.0.101",
-    "@famgia/omnify-atlas": "0.0.95"
+    "@famgia/omnify-types": "0.0.101",
+    "@famgia/omnify-atlas": "0.0.97",
+    "@famgia/omnify-core": "0.0.103"
   },
   "scripts": {
     "build": "tsup",

package/stubs/ai-guides/cursor/laravel.mdc.stub

@@ -7,7 +7,7 @@ alwaysApply: false
 # Laravel Rules
 
 > **Documentation:** `.claude/guides/laravel/`
-> **Specific Rules:** See also `laravel-controller.mdc`, `laravel-resource.mdc`, `laravel-request.mdc`, `laravel-testing.mdc`, `omnify-migrations.mdc`
+> **Specific Rules:** See also `laravel-controller.mdc`, `laravel-resource.mdc`, `laravel-request.mdc`, `laravel-testing.mdc`, `migrations-workflow.mdc`, `omnify-migrations.mdc`
 
 ## ⛔ CRITICAL: DO NOT EDIT
 
@@ -25,7 +25,7 @@ alwaysApply: false
 ## Critical Rules
 
 1. **Thin Controller** - Validate → Delegate → Respond (see `laravel-controller.mdc`)
-2. **Schema-First** - Use Omnify schemas, don't create migrations manually
+2. **🚨 Schema-First** - **NEVER** run `php artisan make:migration`! Use Omnify schemas instead (see `migrations-workflow.mdc`)
 3. **Security** - Always use `$request->validated()`, never `$request->all()`
 4. **Performance** - Use `with()` for relations, `paginate()` for lists
 5. **Dates** - Store UTC, return `->toISOString()`
@@ -33,6 +33,21 @@ alwaysApply: false
 7. **Imports** - Always `use` and short class names, never FQCN inline
 8. **OpenAPI Paths** - NO `/api` prefix! `api.php` already has it (see `laravel-controller.mdc`)
 
+## ⛔ FORBIDDEN: Manual Migrations
+
+```bash
+# ❌ NEVER DO THIS
+php artisan make:migration create_xxx_table
+php artisan make:migration add_xxx_to_xxx_table
+
+# ✅ ALWAYS DO THIS
+# 1. Edit/Create YAML schema in schemas/
+# 2. Run: npx omnify generate
+# 3. Run: php artisan migrate
+```
+
+See `migrations-workflow.mdc` for complete guide.
+
 ## File-Specific Rules
 
 | File Type  | Rule File               | Key Focus                    |

package/stubs/ai-guides/cursor/migrations-workflow.mdc.stub

@@ -0,0 +1,224 @@
+---
+description: "CRITICAL: Use Omnify Schema for migrations - DO NOT create migrations manually"
+globs: ["{{LARAVEL_BASE}}/database/migrations/**"]
+alwaysApply: true
+---
+
+# ⛔ STOP: DO NOT CREATE MIGRATIONS MANUALLY
+
+## You MUST use Omnify Schema to create database changes
+
+When you need to modify the database structure, **NEVER** run:
+
+```bash
+# ❌ FORBIDDEN
+php artisan make:migration create_xxx_table
+php artisan make:migration add_xxx_to_xxx_table
+php artisan make:migration modify_xxx_column
+```
+
+---
+
+## ✅ CORRECT WORKFLOW
+
+### Step 1: Create or Edit Schema YAML
+
+```yaml
+# schemas/your-module/YourModel.yaml
+displayName:
+  ja: モデル名
+  en: Model Name
+
+properties:
+  field_name:
+    type: String
+    length: 255
+    displayName:
+      ja: フィールド名
+      en: Field Name
+```
+
+### Step 2: Generate Migrations
+
+```bash
+npx omnify generate
+```
+
+### Step 3: Run Migrations
+
+```bash
+php artisan migrate
+```
+
+---
+
+## Why This Rule Exists
+
+| Manual Migration | Omnify Schema |
+|------------------|---------------|
+| ❌ No TypeScript types | ✅ Auto-generated types |
+| ❌ No i18n labels | ✅ Auto-generated i18n |
+| ❌ No Zod validation | ✅ Auto-generated validation |
+| ❌ No API resources | ✅ Auto-generated API |
+| ❌ Inconsistent naming | ✅ Consistent naming |
+| ❌ Manual model updates | ✅ Auto-updated models |
+
+---
+
+## Schema-First Development Flow
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    SCHEMA YAML (Source of Truth)            │
+│               schemas/module/ModelName.yaml                  │
+└─────────────────────┬───────────────────────────────────────┘
+                      │
+                      ▼ npx omnify generate
+         ┌────────────┴────────────┬─────────────────┐
+         ▼                         ▼                 ▼
+┌─────────────────┐    ┌─────────────────┐   ┌─────────────────┐
+│   Migrations    │    │   Laravel       │   │   TypeScript    │
+│   (PHP)         │    │   Models        │   │   Types/Zod     │
+└─────────────────┘    └─────────────────┘   └─────────────────┘
+         │                         │                 │
+         ▼                         ▼                 ▼
+    php artisan              Ready to use        Frontend ready
+      migrate
+```
+
+---
+
+## 🚨 BEFORE Creating Any Migration
+
+### Ask yourself:
+
+1. **Can this be done with Omnify Schema?**
+   - New table? → Create new YAML schema
+   - New column? → Add property to YAML
+   - New index? → Add `index: true` to property
+   - Foreign key? → Add association to YAML
+
+2. **Is this schema-related?**
+   - YES → Edit YAML, run `npx omnify generate`
+   - NO → Only then consider manual migration
+
+---
+
+## When Manual Migrations ARE Allowed
+
+Only for operations **NOT supported** by Omnify:
+
+```bash
+# ✅ ALLOWED: Data migrations (not schema changes)
+php artisan make:migration migrate_old_data_to_new_format
+
+# ✅ ALLOWED: Complex SQL operations
+php artisan make:migration add_full_text_search_index
+
+# ✅ ALLOWED: Third-party package migrations
+php artisan vendor:publish --tag=package-migrations
+```
+
+**BUT NEVER for standard CRUD tables/columns!**
+
+---
+
+## Quick Reference: Schema vs Manual
+
+| Change Type | Use Omnify Schema | Manual OK |
+|-------------|:-----------------:|:---------:|
+| Create table | ✅ | ❌ |
+| Add column | ✅ | ❌ |
+| Modify column | ✅ | ❌ |
+| Add foreign key | ✅ | ❌ |
+| Add simple index | ✅ | ❌ |
+| Add pivot table | ✅ | ❌ |
+| Add enum column | ✅ | ❌ |
+| Data migration | ❌ | ✅ |
+| Full-text index | ❌ | ✅ |
+| Raw SQL changes | ❌ | ✅ |
+
+---
+
+## How to Add Common Schema Changes
+
+### New Table
+
+```yaml
+# schemas/shop/Product.yaml
+displayName:
+  ja: 商品
+  en: Product
+
+properties:
+  name:
+    type: String
+    length: 255
+  price:
+    type: Decimal
+    precision: 10
+    scale: 2
+```
+
+### New Column to Existing Table
+
+```yaml
+# Edit existing schemas/shop/Product.yaml
+properties:
+  # ... existing properties ...
+  
+  # Add new property
+  sku:
+    type: String
+    length: 50
+    unique: true
+```
+
+### Add Relationship
+
+```yaml
+# schemas/shop/Product.yaml
+associations:
+  category:
+    type: ManyToOne
+    target: Category
+    foreignKey: category_id
+```
+
+### Add Index
+
+```yaml
+properties:
+  email:
+    type: String
+    index: true  # Simple index
+    
+  # Or composite index
+indexes:
+  - columns: [first_name, last_name]
+    unique: true
+```
+
+---
+
+## Remember
+
+> **Schema YAML = Single Source of Truth**
+> 
+> All database structure changes should originate from YAML schemas.
+> The migration files are just **generated output**, not the source.
+
+---
+
+## If You're Unsure
+
+Read the schema guide:
+
+```bash
+cat .cursor/rules/omnify/schema-create.mdc
+# or
+cat schemas/README.md
+```
+
+Or ask:
+> "How do I add [field/table/relationship] using Omnify schema?"