Copilot Instructions

Common Instructions

Look in the problems tab for any errors or warnings in the code
Follow the existing code style and conventions used in the project
Write clear and concise comments where necessary to explain complex logic
Ensure code is modular and reusable where possible
Write unit tests for new functionality and ensure existing tests pass, but only if there is a configured testing framework
Avoid introducing new dependencies unless absolutely necessary, but ask the user if there is a specific library they want to use
If you are unsure about any requirements or details, ask the user for clarification before proceeding
Respect a11y and localization best practices if applicable, optimize for WCAG AA standards

See .env in root for project specific environment variables
See Makefile for starting up the development environment with Docker
If development environment is running, access the website at: https://${PROJECT_NAME}.code.testversion.online/ or ask the user for the correct URL
You can also use Browser MCP, so ask user to connect if needed
Esbuild is used, watching for changes in files to rebuild automatically
To force a restart of the frontend build and dev-server run: make restart-frontend
Backend is tibi-server configured in /api/ folder and also restarted if changes are detected in this folder
To show last X lines of docker logs run: make docker-logs-X where X is the number of lines you want to see
For a11y testing use the MCP a11y tools if available