jonathands · September 28, 2025 21:51 · Sep 28, 2025 · Sep 28, 2025
diff --git a/personal_claude.MD b/personal_claude.MD
@@ -2,7 +2,7 @@
 
 We will be developing a big range of projects, please only follow the rules if the projects fit especifically the Type described, follow the rules unless specified otherwise by the prompt or the projects CLAUDE.md
 
-#GENERAL
+# GENERAL
 * AVOID USING EMOJI
 * When working with GitHub repositories from the user jonathands, always use the alias 'githubmy' for the remote (e.g., git@githubmy:jonathands/repo-name.git)
 * Do NOT add any mention of Claude, Claude Code, or co-authoring attribution to PRs, Issues, or Commits

diff --git a/personal_claude.MD b/personal_claude.MD
@@ -0,0 +1,36 @@
+## Guidelines
+
+We will be developing a big range of projects, please only follow the rules if the projects fit especifically the Type described, follow the rules unless specified otherwise by the prompt or the projects CLAUDE.md
+
+#GENERAL
+* AVOID USING EMOJI
+* When working with GitHub repositories from the user jonathands, always use the alias 'githubmy' for the remote (e.g., git@githubmy:jonathands/repo-name.git)
+* Do NOT add any mention of Claude, Claude Code, or co-authoring attribution to PRs, Issues, or Commits
+* Don't add long code sessions to documentation, unless asked to provide examples
+
+### Type: Frontend Web Development
+* When using Images, if the user has not specified a source, try using Pexels.
+* When generating code with Icons, please avoid using SVGs directly, attempt to use LucideIcons or HeroIcons
+* Never use BASE64 images
+* Never add HASHEs to javascript or css includes
+
+### Type: Mobile Development
+* When using Images, if the user has not specified a source, try using Pexels.
+* When genrating code with Icons, please avoid using SVGs directly, try to use LucideIcons or HeroIcons
+* Unless specified otherwise, Mobile Projects are built with Expo
+
+### Type: Qt5 and Qt6 with Python
+* Avoid creating large screens with too much components, try separating in sub components
+* Try separating UI logic from Business Logic
+
+### Type: PHP with laravel
+* If we are using fillament code, always use Version 4
+
+### Type: GOLANG
+* use Zerolog for logging
+
+# important-instruction-reminders
+Do what has been asked; nothing more, nothing less.
+NEVER create files unless they're absolutely necessary for achieving your goal.
+ALWAYS prefer editing an existing file to creating a new one.
+NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
diff --git a/spatie.MD b/spatie.MD
@@ -0,0 +1,245 @@
+# Laravel & PHP Guidelines for AI Code Assistants
+
+This file contains Laravel and PHP coding standards optimized for AI code assistants like Claude Code, GitHub Copilot, and Cursor. These guidelines are derived from Spatie's comprehensive Laravel & PHP standards.
+
+## Core Laravel Principle
+
+**Follow Laravel conventions first.** If Laravel has a documented way to do something, use it. Only deviate when you have a clear justification.
+
+## PHP Standards
+
+- Follow PSR-1, PSR-2, and PSR-12
+- Use camelCase for non-public-facing strings
+- Use short nullable notation: `?string` not `string|null`
+- Always specify `void` return types when methods return nothing
+
+## Class Structure
+- Use typed properties, not docblocks:
+- Constructor property promotion when all properties can be promoted:
+- One trait per line:
+
+## Type Declarations & Docblocks
+- Use typed properties over docblocks
+- Specify return types including `void`
+- Use short nullable syntax: `?Type` not `Type|null`
+- Document iterables with generics:
+  ```php
+  /** @return Collection<int, User> */
+  public function getUsers(): Collection
+  ```
+
+### Docblock Rules
+- Don't use docblocks for fully type-hinted methods (unless description needed)
+- **Always import classnames in docblocks** - never use fully qualified names:
+  ```php
+  use \Spatie\Url\Url;
+  /** @return Url */
+  ```
+- Use one-line docblocks when possible: `/** @var string */`
+- Most common type should be first in multi-type docblocks:
+  ```php
+  /** @var Collection|SomeWeirdVendor\Collection */
+  ```
+- If one parameter needs docblock, add docblocks for all parameters
+- For iterables, always specify key and value types:
+  ```php
+  /**
+   * @param array<int, MyObject> $myArray
+   * @param int $typedArgument
+   */
+  function someFunction(array $myArray, int $typedArgument) {}
+  ```
+- Use array shape notation for fixed keys, put each key on it's own line:
+  ```php
+  /** @return array{
+     first: SomeClass,
+     second: SomeClass
+  } */
+  ```
+
+## Control Flow
+- **Happy path last**: Handle error conditions first, success case last
+- **Avoid else**: Use early returns instead of nested conditions
+- **Separate conditions**: Prefer multiple if statements over compound conditions
+- **Always use curly brackets** even for single statements
+- **Ternary operators**: Each part on own line unless very short
+
+```php
+// Happy path last
+if (! $user) {
+    return null;
+}
+
+if (! $user->isActive()) {
+    return null;
+}
+
+// Process active user...
+
+// Short ternary
+$name = $isFoo ? 'foo' : 'bar';
+
+// Multi-line ternary
+$result = $object instanceof Model ?
+    $object->name :
+    'A default value';
+
+// Ternary instead of else
+$condition
+    ? $this->doSomething()
+    : $this->doSomethingElse();
+```
+
+## Laravel Conventions
+
+### Routes
+- URLs: kebab-case (`/open-source`)
+- Route names: camelCase (`->name('openSource')`)
+- Parameters: camelCase (`{userId}`)
+- Use tuple notation: `[Controller::class, 'method']`
+
+### Controllers
+- Plural resource names (`PostsController`)
+- Stick to CRUD methods (`index`, `create`, `store`, `show`, `edit`, `update`, `destroy`)
+- Extract new controllers for non-CRUD actions
+
+### Configuration
+- Files: kebab-case (`pdf-generator.php`)
+- Keys: snake_case (`chrome_path`)
+- Add service configs to `config/services.php`, don't create new files
+- Use `config()` helper, avoid `env()` outside config files
+
+### Artisan Commands
+- Names: kebab-case (`delete-old-records`)
+- Always provide feedback (`$this->comment('All ok!')`)
+- Show progress for loops, summary at end
+- Put output BEFORE processing item (easier debugging):
+  ```php
+  $items->each(function(Item $item) {
+      $this->info("Processing item id `{$item->id}`...");
+      $this->processItem($item);
+  });
+
+  $this->comment("Processed {$items->count()} items.");
+  ```
+
+## Strings & Formatting
+
+- **String interpolation** over concatenation:
+
+## Enums
+
+- Use PascalCase for enum values:
+
+## Comments
+
+- **Avoid comments** - write expressive code instead
+- When needed, use proper formatting:
+  ```php
+  // Single line with space after //
+
+  /*
+   * Multi-line blocks start with single *
+   */
+  ```
+- Refactor comments into descriptive function names
+
+## Whitespace
+
+- Add blank lines between statements for readability
+- Exception: sequences of equivalent single-line operations
+- No extra empty lines between `{}` brackets
+- Let code "breathe" - avoid cramped formatting
+
+## Validation
+
+- Use array notation for multiple rules (easier for custom rule classes):
+  ```php
+  public function rules() {
+      return [
+          'email' => ['required', 'email'],
+      ];
+  }
+  ```
+- Custom validation rules use snake_case:
+  ```php
+  Validator::extend('organisation_type', function ($attribute, $value) {
+      return OrganisationType::isValid($value);
+  });
+  ```
+
+## Blade Templates
+
+- Indent with 4 spaces
+- No spaces after control structures:
+  ```blade
+  @if($condition)
+      Something
+  @endif
+  ```
+
+## Authorization
+
+- Policies use camelCase: `Gate::define('editPost', ...)`
+- Use CRUD words, but `view` instead of `show`
+
+## Translations
+
+- Use `__()` function over `@lang`:
+
+## API Routing
+
+- Use plural resource names: `/errors`
+- Use kebab-case: `/error-occurrences`
+- Limit deep nesting for simplicity:
+  ```
+  /error-occurrences/1
+  /errors/1/occurrences
+  ```
+
+## Testing
+
+- Keep test classes in same file when possible
+- Use descriptive test method names
+- Follow the arrange-act-assert pattern
+
+## Quick Reference
+
+### Naming Conventions
+- **Classes**: PascalCase (`UserController`, `OrderStatus`)
+- **Methods/Variables**: camelCase (`getUserName`, `$firstName`)
+- **Routes**: kebab-case (`/open-source`, `/user-profile`)
+- **Config files**: kebab-case (`pdf-generator.php`)
+- **Config keys**: snake_case (`chrome_path`)
+- **Artisan commands**: kebab-case (`php artisan delete-old-records`)
+
+### File Structure
+- Controllers: plural resource name + `Controller` (`PostsController`)
+- Views: camelCase (`openSource.blade.php`)
+- Jobs: action-based (`CreateUser`, `SendEmailNotification`)
+- Events: tense-based (`UserRegistering`, `UserRegistered`)
+- Listeners: action + `Listener` suffix (`SendInvitationMailListener`)
+- Commands: action + `Command` suffix (`PublishScheduledPostsCommand`)
+- Mailables: purpose + `Mail` suffix (`AccountActivatedMail`)
+- Resources/Transformers: plural + `Resource`/`Transformer` (`UsersResource`)
+- Enums: descriptive name, no prefix (`OrderStatus`, `BookingType`)
+
+### Migrations
+- do not write down methods in migrations, only up methods
+
+### Code Quality Reminders
+
+#### PHP
+- Use typed properties over docblocks
+- Prefer early returns over nested if/else
+- Use constructor property promotion when all properties can be promoted
+- Avoid `else` statements when possible
+- Use string interpolation over concatenation
+- Always use curly braces for control structures
+
+---
+
+*These guidelines are maintained by [Spatie](https://spatie.be/guidelines) and optimized for AI code assistants.*
+
+
+(source)[https://spatie.be/laravel-php-ai-guidelines.md]
No results found