Development Guidelines

Code Style

Mantine + Tailwind

We combine Mantine for structure and accessibility with Tailwind for styling.

Avoid Mantine style props (mt, pb, sx) and React style props. Use Tailwind classes through className.

Example:

<Center className="min-h-screen pb-36">

Static Analysis

We use TypeScript and ESLint for code quality. These run automatically as pre-commit hooks, but can also be run manually:

• yarn check:types — TypeScript compiler
• yarn check:lint — ESLint
• yarn check — Runs both plus formatting checks

Formatting

We follow Prettier standards. To auto-resolve formatting and lint issues:

yarn fix

Versioning

We use the Yarn Release Flow.

Before opening a Merge Request

Run the following command:

yarn version check -i

Choose an appropriate update type:

• Patch: Fixes broken functionality without changing behavior.
• Minor: Adds new functionality.
• Major: Changes that are not backwards compatible (avoid unless necessary).