yisroelbaum/Goal-Calibration
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update prompt template

Browse source
This commit is contained in:
Yisroel Baum 2026-04-19 22:50:05 +03:00
parent ce689da99a
commit 921c1e6401
Signed by: yisroelbaum
GPG key ID: 0FA60884F75520A9
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
ai/PROMPT_TEMPLATE.md
View file

@ -1,6 +1,7 @@
# Entity Creation Prompt Template # 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: Requirements:
- The entity encapsulates [one or more Entities] - The entity encapsulates [one or more Entities]
@ -25,7 +26,8 @@ Code patterns to follow:
- Look at tests/Fakes/ for examples - Look at tests/Fakes/ for examples
- Find/lookup methods must return a new instance of the entity, not the stored reference - Find/lookup methods must return a new instance of the entity, not the stored reference
- Tests: follow existing patterns in tests/Unit/[Entity]/UseCases/ - 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) - 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) - Variable names: use explicit, descriptive names — never single-letter or abbreviated variables (e.g., use $sponsorship not $s, $event not $e)