Architect

#Configuration File

Edit config/architect.php to customize the plugin behavior, namespaces, and output paths:

<?php

return [
    /*
    |--------------------------------------------------------------------------
    | Bootstrap Architect Plugin
    |--------------------------------------------------------------------------
    |
    | Whether to show the Architect plugin. Defaults to false in production.
    | Set this to true if you want to enable code generation in production,
    | though it's recommended to keep this disabled for security reasons.
    |
    | Environment Variable: ARCHITECT_SHOW
    |
    */
    'show' => env('ARCHITECT_SHOW', false),

    /*
    |--------------------------------------------------------------------------
    | Default Generation Options
    |--------------------------------------------------------------------------
    |
    | Configure which files should be generated by default when creating a new
    | resource through the Architect wizard. These defaults can be overridden
    | per-resource in the wizard interface.
    |
    | Note: Migrations are always generated as they are core to the plugin.
    |
    | - generate_factory: Create model factory for testing and seeding
    | - generate_seeder: Create database seeder class
    | - generate_resource: Create complete Filament resource with CRUD pages
    |
    */
    'generate_factory' => env('ARCHITECT_GENERATE_FACTORY', true),
    'generate_seeder' => env('ARCHITECT_GENERATE_SEEDER', true),
    'generate_resource' => env('ARCHITECT_GENERATE_RESOURCE', true),

    /*
    |--------------------------------------------------------------------------
    | Models Namespace
    |--------------------------------------------------------------------------
    |
    | The default namespace for generated Eloquent models. This determines
    | where your model classes will be created when using the Architect wizard.
    |
    */
    'namespace' => 'App\\Models',

    /*
    |--------------------------------------------------------------------------
    | Factories Namespace
    |--------------------------------------------------------------------------
    |
    | The default namespace for generated model factories. This determines
    | where your factory classes will be created for testing and seeding.
    |
    */
    'factories_namespace' => 'Database\\Factories',

    /*
    |--------------------------------------------------------------------------
    | Seeders Namespace
    |--------------------------------------------------------------------------
    |
    | The default namespace for generated database seeders. This determines
    | where your seeder classes will be created for populating test data.
    |
    */
    'seeders_namespace' => 'Database\\Seeders',

    /*
    |--------------------------------------------------------------------------
    | Filament Resources Namespace
    |--------------------------------------------------------------------------
    |
    | The default namespace for generated Filament resources. This determines
    | where your resource classes (including pages and actions) will be created.
    |
    */
    'resources_namespace' => 'App\\Filament\\Resources',
];

#Development

#Running Tests

To run the test suite:

composer test

#Code Quality

Format code using Pint:

composer format

Check code style with Pint:

composer lint

#Architecture

The plugin is organized into several key components:

#Generators

Located in src/Generators/, each generator handles creating specific files:

• ModelGenerator - Generates Eloquent models
• MigrationGenerator - Creates database migrations
• FactoryGenerator - Generates model factories
• SeederGenerator - Creates database seeders
• FilamentResourceGenerator - Generates Filament resources with all pages

#Livewire Components

• ArchitectWizard - Main wizard component with form handling
• BlueprintsTable - Table for managing existing blueprints

#Value Objects

• BlueprintData - Type-safe blueprint configuration
• ColumnDefinition - Type-safe column configuration

#Support

• SchemaValidator - Validates blueprint schemas before generation

#Advanced Usage

#Programmatic Generation

You can generate resources programmatically without using the wizard, for example:

use Lartisan\Architect\ValueObjects\BlueprintData;
use Lartisan\Architect\Generators\ModelGenerator;

$blueprintData = BlueprintData::fromArray([
    'table_name' => 'posts',
    'model_name' => 'Post',
    'primary_key_type' => 'id',
    'columns' => [
        ['name' => 'title', 'type' => 'string'],
        ['name' => 'content', 'type' => 'text'],
    ],
    'soft_deletes' => false,
    'gen_factory' => true,
    'gen_seeder' => true,
    'gen_resource' => true,
]);

// Generate individual components
$modelGenerator = new ModelGenerator();
$modelGenerator->generate($blueprintData);

#Custom Stubs

Customize the generated files by publishing stubs:

php artisan vendor:publish --tag=architect-stubs

Edit the stubs in stubs/ to match your project's conventions.

#Troubleshooting

#Migration not running

Ensure the architect_blueprints table has been created:

php artisan migrate

#Files not generating

• Check that the output directories exist and are writable
• Verify the configured namespaces match your project structure
• Check Laravel logs for detailed error messages

#Permission errors

Ensure your Laravel application has write permissions to the app/, database/, and app/Filament/Resources/ directories.

#Performance Considerations

• Blueprint data is cached in the database for quick access
• Generation happens synchronously during wizard submission
• For large projects, consider running expensive operations in queued jobs

#Roadmap

#Planned Features

• Update existing schemas
• Regenerate files without losing configuration
• More configurable render hooks
• Edit and regenerate any blueprint
• Relationship management (belongsTo, hasMany, belongsToMany)
• Custom field types and validation rules
• Import/export blueprints
• Batch generation
• Artisan command support
• API-based generation
• Integration with existing models

#Security Considerations

• Production Safety: The plugin is automatically disabled in production environments by default (configurable via ARCHITECT_SHOW environment variable)
• Always validate user input from the wizard
• The plugin generates code based on user-defined specifications
• Review generated migrations before running them in production
• Use the plugin only in development environments or with proper authorization
• Consider restricting access to the plugin using Filament's built-in authorization features

#Contributing

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

Please ensure:

• Tests pass: composer test
• Code is formatted: composer format
• Code quality is maintained: composer lint

#Support

For issues, questions, or feature requests, please open an issue on GitHub.

For Filament-specific questions, visit the Filament Discord Community.

#Changelog

See CHANGELOG.md for all notable changes.

#License

The MIT License (MIT). Please see LICENSE.md for more information.

#Credits

Filament Architect is developed and maintained by lartisan.

Special thanks to:

• Filament for the amazing admin panel framework
• Laravel for the excellent PHP framework
• The Laravel and Filament communities for their feedback and contributions

#Made with ❤️ for the Laravel/Filament Community