To ensure the AI refers to the rules file each time, you can include a note within the rules file itself, instructing to always check and follow the guidelines specified in this file. Here is the updated AI rules file content:

# Fusion Quickpanel AI Rules

Every time you choose to apply a rule(s), explicitly state the rule(s) in the output. You can abbreviate the rule description to a single word or phrase. Always refer to this rules file when generating or modifying code.

## Project Context
Fusion Service Management - Raw code from Quickpanel.

## Code Style and Structure
- Write concise, technical PHP and Blade code with accurate examples.
- Use procedural programming patterns; avoid classes.
- Structure repository files as follows:
```
src/
├── controllers/       # Controllers
├── models/            # Models
├── views/             # Views
├── routes/            # Routes
```

## Tech Stack
- PHP
- Blade
- CSS
- MySQL (Database)

## Naming Conventions
- Use lowercase with dashes for directories (e.g., controllers/user-controller)
- Use PascalCase for class files (e.g., UserController.php)
- Use camelCase for function and variable names (e.g., getUserName)

## PHP Usage
- Use PHP for all backend logic; prefer functions over classes.
- Use Blade for templating.
- Avoid using global variables; use dependency injection where possible.
- Use explicit return types for all functions.

## CSS Usage
- Use class-based CSS for styling.
- Follow BEM (Block Element Modifier) methodology for naming classes.

## Error Handling
- Implement proper error handling and logging.
- Provide user-friendly error messages.
- Handle network failures gracefully.

## Testing
- Write unit tests for critical functions.
- Implement E2E tests for key user flows.
- Test across different PHP versions.

## Security
- Sanitize user inputs.
- Handle sensitive data properly.
- Follow PHP security best practices.

## Git Usage
Commit Message Prefixes:
- "fix:" for bug fixes
- "feat:" for new features
- "perf:" for performance improvements
- "docs:" for documentation changes
- "style:" for formatting changes
- "refactor:" for code refactoring
- "test:" for adding missing tests
- "chore:" for maintenance tasks

Rules:
- Use lowercase for commit messages.
- Keep the summary line concise.
- Include description for non-obvious changes.
- Reference issue numbers when applicable.

## Documentation
- Maintain clear README with setup instructions.
- Document API interactions and data flows.
- Keep code comments minimal and relevant.
- Document security practices and sensitive data handling.

## Development Workflow
- Use proper version control.
- Implement proper code review process.
- Test in multiple environments.
- Follow semantic versioning for releases.
- Maintain changelog.

Place this file in the root directory of your repository with the name `AI-RULES.md`.
