Software Development

General

Tech Stack Overview Recommended Libraries Development Workflow Architecture Decision Records Tech Radar

Frontend

Rendering Strategies Routing, Layouts, and Modules State Management Data Loading and Cache API Client and Types Forms and Validation Styling and Design System Auth on Frontend i18n and Localization Accessibility (A11y)Error Handling Patterns Frontend Testing

Backend

Backend Overview Architecture and Module Boundaries API Design (REST + OpenAPI)Auth and Permissions Database Schema and Migrations Transactions and Idempotency Background Jobs and Scheduling Payments System Mailing System Webhooks and Event Processing File Handling and Storage Realtime Features (WebSockets and SSE)Caching Strategies Error Handling Patterns Backend Testing Logging, Monitoring, and Alerting

Dev Environment & Tooling

Runtime (Node and Bun)Package Managers (pnpm and Bun)Monorepo Workspaces Local HTTPS Proxy and Certs Local Infra with Docker Compose External Services in Dev Debugging and Troubleshooting

Quality & Security

Coding Standards and Review Security Baseline for Web Apps Rate Limiting and Abuse Protection Dependency and Secret Management Release Readiness Checklist

Boilerplate

Overview Architecture Map Start a New Project Upgrade and Maintenance

Engineering Guides

Software Development Cloud Engineering AI Engineering (soon)

i18n and Localization

Prepare UI for multiple languages, locale formats, and translation workflows.

Recommended approach

Use react-i18next as the default i18n library.
Keep translation keys domain-scoped by module.
Externalize date/number/currency formatting.
Treat localization as part of definition of done for user-facing features.

Implementation checklist

Add locale detection and override strategy.
Define translation ownership and review process.
Include RTL support checks if required markets need it.
Add guidance in AGENTS.md that the app supports multiple languages and all UI work must support all configured languages.

Common pitfalls

Hard-coded UI strings inside components.
Locale-specific formatting bugs in pricing and date displays.

Related pages

Forms and Validation

Auth on Frontend

Implement authentication UX and routing boundaries safely on the client.

Accessibility (A11y)

Ensure UI is operable and understandable for users with assistive technologies.

On this page

Recommended approach Implementation checklist Common pitfalls Related pages