update prompt template with project specific examples

ai/PROMPT_TEMPLATE.md

@@ -16,7 +16,7 @@ Process (TDD - Test Driven Development):
 
 Code patterns to follow:
 - First, explore the codebase to understand existing entity patterns
-- Look at similar entities (e.g., AgendaSlot, Event, etc.) for reference
+- Look at similar entities (e.g. Node, Text, etc.) for reference
 - Entities: constructor with properties, getters
 - DTOs: simple data containers for creation
 - Repositories: interfaces that define data access
@@ -26,7 +26,7 @@ Code patterns to follow:
   - Look at tests/Fakes/ for examples
   - Find/lookup methods must return a new instance of the entity, not the stored reference
 - Tests: follow existing patterns in tests/Unit/[Entity]/UseCases/
-  - In setUp, only use fake repositories for entities under test — construct dependency objects directly with `new` (e.g., `new Event(id: 0, slug: 'test')`) instead of creating them through their fake repositories
+  - In setUp, only use fake repositories for entities under test — construct dependency objects directly with `new` (e.g., `new Text(....)`) instead of creating them through their fake repositories
 - Lines should not exceed 80 columns, but should use up to 80 columns when possible — do not split lines unnecessarily
 - Imports: always put use statements at the top of the file, never use inline imports (e.g., \App\Foo\Bar::class)
 - Variable names: use explicit, descriptive names — never single-letter or abbreviated variables (e.g., use $sponsorship not $s, $event not $e)