forgejo-lila/lila
1
0
Fork 0
Code Issues 50 Pull requests Projects 1 Releases Packages Wiki Activity Actions

adding task to prompts

Browse source
This commit is contained in:
lila 2026-04-30 00:36:28 +02:00
parent fd9667c1fd
commit 57d2190549
1 changed files with 2 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
documentation/notes.md
View file

@ -12,7 +12,8 @@ task description.
4. if we go through a file, we'll do it slowly section by section, no matter how many sections 4. if we go through a file, we'll do it slowly section by section, no matter how many sections
5. how to name the current feature branch? also tell me when its time to git commit and provide a commit message 5. how to name the current feature branch? also tell me when its time to git commit and provide a commit message
6. if we have multiple options to do something, also always provide options that reflect current industry standards and best practices 6. if we have multiple options to do something, also always provide options that reflect current industry standards and best practices
7. For every completed task, produce a ticket file in documentation/tickets/. Use ADR format (adr-) for decisions between options with long-term consequences. Use feat-/fix-/chore- for routine tasks. Always include a setup guide or summary of what was done. Suggest the filename. 7. never assume anything! always ask for clarification!
8. For every completed task, produce a ticket file in documentation/tickets/. Use ADR format (adr-) for decisions between options with long-term consequences. Use feat-/fix-/chore- for routine tasks. Always include a setup guide or summary of what was done. Suggest the filename.
## tasks ## tasks