Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 1.71 KB

File metadata and controls

32 lines (19 loc) · 1.71 KB
applyTo **

Provide project context and coding guidelines that AI should follow when generating code, answering questions, or reviewing changes.

Whenever you want to build the packages to test if they work you should run pnpm run build from the root of the repository.

If you want to check if the examples work you need to go to examples/<example-name> and run pnpm run dev.

When writing code, please follow these guidelines:

  • Use TypeScript for all new code.
  • Ensure all new code is covered by tests.
  • Do not use any type; prefer specific types or generics.
  • Follow existing code style and conventions.

If you get an error "address already in use :::42069 you should kill the process using that port.

If we add a new functionality add a section about it in the docs/ folder explaining how to use it and update the README.md file to mention it.

Write tests for any new functionality.

When defining new types, first check if the types exist somewhere and re-use them, do not create new types that are similar to existing ones.

When modifying existing functionality, ensure backward compatibility unless there's a strong reason to introduce breaking changes. If breaking changes are necessary, document them clearly in the relevant documentation files.

Under no circumstances should casting as any be used in the codebase. Always strive to find or create the appropriate type definitions. Avoid casting unless absolutely neccessary, and even then, prefer using satisfies for type assertions to maintain type safety.

Do not add Select-Object -Last X at the end of PowerShell commands in the CI scripts. This can hide important error messages and make debugging more difficult and it also makes the process hang