code-standards

# Code Standards Write code that is accessible, performant, type-safe, and maintainable. ## Activation Conditions - Linting errors need fixing - Code formatting issues - Code review feedback - Questions about style guidelines ## Quick Reference | Action | Rule | |--------|------| | Write components | `react-functional-only.md` | | Async code | `async-await-promises.md` | | Avoid legacy libs | `no-legacy.md` | `any` types and top-level regex are enforced by Biome (`noExplicitAny`, `useTopLevelRegex`). ## Commands ```bash bun x ultracite fix # Format and fix bun x ultracite check # Check for issues bun x ultracite doctor # Diagnose setup ``` ## Quick Fix Most issues are auto-fixed: ```bash bun x ultracite fix ``` ## Console Logging - **Never** use `console.log`, `console.debug`, or `console.info` in production code - Only use `console.error` and `console.warn` for actionable errors - For debug logging, wrap in `if (IsDev) { ... }` - Don't use `biome-ignore` to suppress console warnings - remove the logs instead ## Rules See `rules/` directory for detailed guidance.