- `make build` or `make build-fat` - Build all "fat" binaries (includes "server" functionality)

- `make build-slim` - Build "slim" binaries

- `make test` - Run Go tests

- `make test RUN=TestFunctionName` or `go test -v ./path/to/package -run TestFunctionName` - Test single

- `make test-postgres` - Run tests with Postgres database

- `make test-race` - Run tests with Go race detector

- `make test-e2e` - Run end-to-end tests

- `make lint` - Run all linters

- `make fmt` - Format all code

- `make gen` - Generates mocks, database queries and other auto-generated files

- `pnpm build` - Build frontend

- `pnpm dev` - Run development server

- `pnpm check` - Run code checks

- `pnpm format` - Format frontend code

- `pnpm lint` - Lint frontend code

- `pnpm test` - Run frontend tests

- Follow [Effective Go](https://go.dev/doc/effective_go) and [Go's Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments)

- Use `gofumpt` for formatting

- Create packages when used during implementation

- Validate abstractions against implementations

- Use TypeScript for all frontend code

- Follow ESLint and Prettier configurations

- Components should be atomic, reusable, and free of business logic

- Modules can contain Coder-specific business logic

- Use descriptive error messages

- Wrap errors with context

- Propagate errors appropriately

- Use proper error types

- (`xerrors.Errorf("failed to X: %w", err)`)

- Use clear, descriptive names

- Abbreviate only when obvious

- Follow Go and TypeScript naming conventions

- Document exported functions, types, and non-obvious logic

- Follow JSDoc format for TypeScript

- Use godoc format for Go code

- Follow [Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/)

- Format: `type(scope): message`

- Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`

- Keep message titles concise (~70 characters)

- Use imperative, present tense in commit titles

- MUST DO! Any changes to database - adding queries, modifying queries should be done in the `coderd\database\queries\*.sql` files.

- MUST DO! Queries are grouped in files relating to context - e.g. `prebuilds.sql`, `users.sql`, `provisionerjobs.sql`.

- After making changes to any `coderd\database\queries\*.sql` files you must run `make gen` to generate respective ORM changes.

- **coderd**: Main API service connecting workspaces, provisioners, and users

- **provisionerd**: Execution context for infrastructure-modifying providers

- **Agents**: Services in remote workspaces providing features like SSH and port forwarding

- **Workspaces**: Cloud resources defined by Terraform

- Templates define infrastructure for workspaces using Terraform

- Environment variables pass context between Coder and templates

- Official modules extend development environments

- Permissions defined at site, organization, and user levels

- Object-Action model protects resources

- Built-in roles: owner, member, auditor, templateAdmin

- Permission format: `<sign>?<level>.<object>.<id>.<action>`

- PostgreSQL 13+ recommended for production

- Migrations managed with `migrate`

- Database authorization through `dbauthz` package

- React with TypeScript

- Material UI v5 for components

- TanStack Query v4 for data fetching

- Emotion for styling

- Formik with Yup for forms and validation

- `/site/` directory contains all UI code

- Components in `/site/src/components`

- Feature modules in `/site/src/modules`

- Pages in `/site/src/pages`

- React Query for API data fetching and caching

- Context-based state with providers

- React Router for navigation

- Color contrast meets WCAG AA compliance (4.5:1 ratio)

- Proper labeling for input elements

- Include descriptive text for images

- End-to-end testing with Playwright

- Integration testing with Jest and react-testing-library

- Visual testing with Storybook and Chromatic