olafjanssen lateralspark .cursorrules file for JavaScript

You are expert in writing clear, concise, and simple code. 
You can create quick prototypes in Python, Javascript, and FastAPI.

Key Principles:
- Use best practices for setting up the folder structure of the project.
- Try to use the least amount of external libraries and dependencies.
- Write as much in vanilla Python and JavaScript as possible.
- Use simple programming patterns and avoid complex patterns.
- Avoid unnecessary try-except blocks, focus on forcing happy paths by designing the code to avoid errors.
- Implement a clear separation of concerns (routes, business logic, data access).
- Use environment variables for configuration management.

Project:
- Use lowercase with underscores for directories and files (e.g., blueprints/user_routes.py).
- Always keep the README.md file updated with the latest information about the project and instructions for running all aspects of the project.

Python:
- Use functional, declarative programming; avoid classes where possible.
- Prefer iteration and modularization over code duplication.
- Use descriptive variable names with auxiliary verbs (e.g., is_active, has_permission).
- Use concise, one-line syntax for simple conditional statements (e.g., if condition: do_something()).
- Follow PEP 8  style guidelines for Python code.
- Use Docstrings for all functions and classes.

Front-end:
- Use vanilla JavaScript and HTML.
- Use Bootstrap CSS for styling.
- Use dedicated pages for each route, instead of single-page applications.

Database:
- Try to use simple file-based database like JSON or CSV.
- Consider using Markdown files with YAML front matter for the database when possible.

LLMs:
- Use Langchain and LangGraph for LLM workflows.
- Connect to local LLMs like Ollama when possible.
- Use Langchain's tool calling and agent functionality to create structured outputs.

Testing
- Instead of unit tests, create example scripts for each module that demonstrate how to use the module.

Markdown:
- When working with markdown files, do not wrap the beginning and end of your answers inside backticks. Instead, output the markdown content as free text. You may use backticks for code snippets within the markdown content.
- When proposing an edit to a markdown file, first decide if there will be code snippets in the markdown file.
- If there are no code snippets, wrap the beginning and end of your answer in backticks and markdown as the language.
- If there are code snippets, indent the code snippets with two spaces and the correct language for proper rendering. Indentations level 0 and 4 is not allowed.
- If a markdown code block is indented with any value other than 2 spaces, automatically fix it


---

You are an expert at writing code in C# for Godot 4.3 and Game Design and Development.

## C#
- Document your classes, methods, and properties.
- Do not over-engineer your code with unnecessary abstractions.
- Use Godot's built-in types and methods whenever possible.

## Godot 4.3
- Add to scripts: `using Godot;` to get access to all Godot types (Node, Resource, Control, etc.)
- Add to scripts: `using System;` for basic .NET types
- Use Godot's collections types (Array, Dictionary, etc.) instead of C# collections (List, Dictionary, etc.)
- Use Godot.HttpClient instead of System.Net.Http.HttpClient


## Documentation
- Use the README.md file to describe the whole Game Design and update it continuously based on your progress and implemented features.