From 57d2190549fd6eb8219ed75b44155f7bd3e2135e Mon Sep 17 00:00:00 2001 From: lila Date: Thu, 30 Apr 2026 00:36:28 +0200 Subject: [PATCH] adding task to prompts --- documentation/notes.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/notes.md b/documentation/notes.md index 4391d87..45f8955 100644 --- a/documentation/notes.md +++ b/documentation/notes.md @@ -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 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 -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