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)

API Client and Types

Avoid contract drift between frontend and backend.

Recommended approach

Generate a typed API client from backend OpenAPI schema.

Backend: generate OpenAPI (for example with NestJS Swagger)
Frontend: generate client/types (for example with swagger-typescript-api)

This keeps request/response contracts synchronized and discoverable.

Alternatives and when to choose them

tRPC/oRPC/RPC-style shared contract when both sides can share runtime contracts directly.

Implementation checklist

Add generate:client script and CI check for generated diffs.
Version APIs with deprecation policy.
Keep transport concerns separate from domain mapping.

Common pitfalls

Editing generated files manually.
Using backend DTOs directly in UI instead of view models where needed.

Related pages

API Design (REST + OpenAPI)
Data Loading and Cache

Data Loading and Cache

Load API data predictably, avoid flicker, and keep cache behavior explicit.

Forms and Validation

Build robust forms with clear validation behavior and minimal duplication.

On this page

Recommended approach Alternatives and when to choose them Implementation checklist Common pitfalls Related pages