update prompt template
This commit is contained in:
parent
ce689da99a
commit
921c1e6401
1 changed files with 4 additions and 2 deletions
|
|
@ -1,6 +1,7 @@
|
|||
# Entity Creation Prompt Template
|
||||
|
||||
Follow the existing patterns in this codebase to create a new entity called [EntityName].
|
||||
Follow the existing patterns in this codebase to:
|
||||
- create a new entity called [EntityName].
|
||||
|
||||
Requirements:
|
||||
- The entity encapsulates [one or more Entities]
|
||||
|
|
@ -25,7 +26,8 @@ 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/
|
||||
- Lines should not exceed 80 columns
|
||||
- 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
|
||||
- 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)
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue