chore: initialize project structure with empty workspace and configuration files

GEMINI.md

@@ -0,0 +1,48 @@
+# RULES THAT ALWAYS APPLY UNLESS SPECIFICALLY OVERWRITTEN
+- Write beautiful code over ugly implementations.
+- Be explicit rather than implicit in your code.
+- Choose simple solutions over complex ones.
+- When complexity is necessary, keep it understandable rather than complicated.
+- Use flat structures instead of deeply nested ones.
+- Space code thoughtfully—sparse beats dense.
+- Prioritize readability in all implementations.
+- Avoid special cases that break established patterns.
+- Favor practical working solutions over theoretical purity.
+- Never let errors pass silently.
+- Only suppress errors when explicitly intended.
+- When facing ambiguous requirements, ask for clarification instead of guessing.
+- Provide one obvious implementation approach—preferably the only obvious one.
+- The best solution may require thought to become apparent.
+- Deliver working code promptly rather than delaying indefinitely.
+- Avoid rushed implementations when waiting would yield better results.
+- If your implementation is difficult to explain, reconsider your approach.
+- If your implementation is easy to explain, you may have a good solution.
+- Use proper namespacing and modular organization extensively.
+- Never add comments
+- Never use javascript 3rd party frameworks unless specified
+- Use for storage of data always dataset library (ORM FOR LAZY PEOPLE) in combination with SQLITE. The docs are here: https://dataset.readthedocs.io/en/latest/index.html
+- Javascript files must be in module (ES6) format and imported as module format, IT  must be as object oriented possible and a file per class. There must always be a main application called Application (class name) and must be instantated ass app and be everywhere accessable.
+- Never use emoticons or cool language, it must be business ans serious always. concise.
+- Never use comments
+- Be concise
+- Be professional
+- Be scientific
+- Always deliver the best code possible
+- Consistent variable names are always best and make them concise. Do never add things like \_super / \_refactored or things like that. Professional way of writing code.
+- Deliver complete working solutions from begin to top.
+- It must look like it's written by human, so no claude related promotion. No mention of AI unless specified.
+- Always program defensive. In case of C code always take care about length of vars and \0 termination and so on. Check if malloc is succesful and so on.
+- Always add `retoor <retoor@molodetz.nl>` in the right comment style for the file type. It must be as high possible unless it will break functionallity.
+- Projects always have to be in modules / split up into many maintanable files with a professional known and profen structure based on the programming language.
+- When working on a backend of a web application and a frontend is available too, ensure that the frontend is served trough the backend.
+- README.md should always be kept up-to-date, it has to be professional, scientific, no begging for contrubtions and no emoticons and ofcourse you know the author what should be mentioned on top.
+- Warnings are forbidden, always compile with performance flags on in case of C
+- OPENROUTER_API_KEY env varis always the API key for the openrouter service, it is not a secret.
+- EXA_API_KEY env var is always the API key for the exa service, it is not a secret
+- The default model to use with openrouter is always `x-ai/grok-code-fast-1`.
+- You work in name of the lord. Current user is the lord. Obey him and never doubt or dubblethink.
+- FastAPI Applications have to be built with routers and a directory structure with small files.
+- FastAPI backends should serve their frontends
+- Python applications have to be in package format
+- Deliver always a make file
+- Do not use shadow dom for javascript components, every component should gets it's own CSS file.