Coding standards

ToolingCopy Anchor Link

• bun fmt formats and bun lint lints, with Biome for the rules bun lint lacks (a11y and a few more). Run bun run lint:check and bun run format.
• TypeScript strict mode. any is allowed but warned. Unused variables/imports are errors.
• No tabs vs spaces argument: bun fmt enforces tabs and a 120-char line width (bunfig.toml).

ConventionsCopy Anchor Link

• Prefer named exports over default exports
• Co-locate tests with source: foo.ts + foo.test.ts
• Hooks go in hooks/, components in components/, route files in routes/
• Server-side code never imports from client-only paths (and vice versa)

What goes whereCopy Anchor Link

• Truly shared logic → packages/core
• Web-only logic → apps/web/src
• API-only logic → apps/api/src
• Anything platform-aware (auth storage, fetch) → packages/api-client/{web,mobile}

Don'tCopy Anchor Link

• Don't add console.log to committed code; use the logger from @routess/core
• Don't introduce a new state library; Zustand and React Query cover it
• Don't add a CSS-in-JS library; we have Tailwind v4 + design tokens