.clinerules

.clinerules

# General instructions

- log every change you make with a summary and files you have changed in a log file named cline_history.md. If it doesn't exist, then create it as well. make sure to include the datetime of your changes and make proper use of the markdown feateres (i.e. headings) to make it readable. Be consistent across the document, meaning, when there is also a certain style and formatting, stick to it. Make sure that your changes are documented sorted by date descending (meaning that latest changes are on top).

- when making commits to this repository, stick to the karma commitlint type of messages. use smaller commits and avoid big, clunky commits that are hard to revert or comprehend. amke also use of the .gitignore file, to avoid commiting sensitive or unneccessary content to repositoriy. If the .gitignore file does not exist, create it

- if you are somewhere stuck, use the brave search in order to find a solution. 

# Coding
## Progamming language
- Prefer typescript over javascript
- Prefer async / await over callbacks and then / catch syntax
- Prefer styled components, over everything else