PixelPilot: Instructions file for GitHub Copilot

UI/UX Database Migration Rules

Safe schema change patterns for production databases. Never delete migrations. Always create new ones.

---

GOLDEN RULES

1. NEVER delete an existing migration file
2. NEVER modify a migration that has been run in production
3. Always create NEW migrations for changes
4. Test migrations on a copy of production data
5. Have a rollback plan for every migration

---

OVERVIEW

This skill covers safe migration patterns for:

• Adding columns
• Removing columns
• Renaming columns
• Changing column types
• Adding/removing indexes
• Data migrations

---

LARAVEL MIGRATIONS

Add a New Column

// database/migrations/2026_01_15_100000_add_phone_to_users_table.php
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::table('users', function (Blueprint $table) {
            $table->string('phone')->nullable()->after('email');
        });
    }

    public function down(): void
    {
        Schema::table('users', function (Blueprint $table) {
            $table->dropColumn('phone');
        });
    }
};

Remove a Column (Safe Way)

// database/migrations/2026_01_16_100000_remove_legacy_field_from_users_table.php
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::table('users', function (Blueprint $table) {
            $table->dropColumn('legacy_field');
        });
    }

    public function down(): void
    {
        Schema::table('users', function (Blueprint $table) {
            // Restore column with nullable to prevent data loss issues
            $table->string('legacy_field')->nullable()->after('email');
        });
    }
};

Rename a Column

// database/migrations/2026_01_17_100000_rename_name_to_full_name_in_users_table.php
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

return new class extends Migration
{
    public function up(): void
    {
        Schema::table('users', function (Blueprint $table) {
            $table->renameColumn('name', 'full_name');
        });
    }

    public function down(): void
    {
        Schema::table('users', function (Blueprint $table) {
            $table->renameColumn('full_name', 'name');
        });
    }
};