AISide Laravel Assistant

Expert assistant for developing and maintaining AISide (MagicAI v8.70), a Laravel-based AI SaaS platform with modular extensions, multiple AI provider integrations, and subscription management.

What This Skill Does

This skill provides specialized knowledge for working with the AISide codebase, including:

Instructions

When assisting with AISide development tasks, follow these guidelines:

1. Understanding the Codebase Structure

**Extension System:**

**AI Provider Integration:**

**Payment System:**

**Frontend Architecture:**

**Key Data Models:**

2. Development Workflow

**Frontend Development:**

```bash

npm install # Install dependencies

npm run dev # Start Vite dev server

npm run build # Build for production

npm run lint # Lint JavaScript

```

**Backend Development:**

```bash

composer install # Install dependencies

php artisan serve # Start dev server

php artisan migrate # Run migrations

php artisan storage:link # Link storage

```

**Testing:**

```bash

composer test # Run Pest tests (parallel)

composer test:coverage # Run with coverage

```

**Code Quality:**

```bash

composer lint # Format with Laravel Pint

composer test:lint # Check style without changes

```

**Cache Management:**

```bash

php artisan optimize:clear # Clear all caches

```

**Queues & Scheduling:**

```bash

php artisan queue:work # Process queue

php artisan schedule:run # Run scheduled tasks

```

3. Task-Specific Guidelines

**When Creating Extensions:**

1. Use existing extensions as templates

2. Create ServiceProvider in `/app/Providers/`

3. Define routes, controllers, views in extension directory

4. Create migrations for extension-specific tables

5. Register provider in `config/app.php`

**When Adding AI Features:**

1. Create service class in `/app/Services/AI/`

2. Add configuration in `/config/`

3. Update controllers to use the service

4. Implement credit consumption logic

5. Add relevant Blade views

6. Write tests for the integration

**When Working with Payments:**

1. Check `/config/payment.php` for gateway configuration

2. Use custom artisan commands to check payment statuses

3. Leverage Laravel Cashier for subscription logic

4. Consider team-based credit systems

**When Modifying Frontend:**

1. Use Blade components for reusable UI elements

2. Leverage Alpine.js for reactive behavior

3. Follow TailwindCSS utility patterns

4. Run `npm run dev` for hot module replacement

5. Build with `npm run build` before deployment

**When Writing Tests:**

1. Use Pest PHP test framework

2. Place tests in `/tests/`

3. Run parallel tests with `composer test`

4. Check coverage with `composer test:coverage`

5. Follow existing test patterns

4. Common Maintenance Tasks

**Monitor Subscriptions:**

```bash

php artisan app:check-subscription-end

```

**Check Payment Gateway Status:**

```bash

php artisan app:check-[gateway-name]

```

**Clear Expired Data:**

```bash

php artisan app:clear-*

```

5. Environment Configuration

Ensure these key variables are configured in `.env`:

6. Best Practices

Example Usage

**User Request:** "Add a new AI text generation feature using the Anthropic API"

**Your Approach:**

1. Read existing AI service implementations in `/app/Services/AI/`

2. Create a new service class following the pattern

3. Add Anthropic configuration in `/config/`

4. Update or create a controller to handle requests

5. Implement credit deduction logic

6. Create Blade views for the feature UI

7. Write Pest tests for the service

8. Run `composer test` and `composer lint`

**User Request:** "Debug why an extension isn't loading"

**Your Approach:**

1. Check the extension's ServiceProvider registration

2. Verify the provider is listed in `config/app.php`

3. Check for migration issues with `php artisan migrate:status`

4. Clear caches with `php artisan optimize:clear`

5. Check logs in `storage/logs/`

6. Verify extension routes are registered

7. Test the extension's controller and views

**User Request:** "Optimize the frontend build process"

**Your Approach:**

1. Review `vite.config.js` configuration

2. Check TailwindCSS configuration for unused styles

3. Run `npm run build` and analyze bundle size

4. Consider lazy loading for Alpine.js components

5. Optimize image assets

6. Verify production environment variables

Constraints