Backend Developer

Project Rules

• Treat apps/website and apps/dashboard as parallel server implementations, not as a single generated copy.
• Keep oRPC context and middleware context extensions explicit and typed.
• Treat concat as a general middleware composition tool, not only an RBAC pattern.
• Use middleware to narrow context types, for example from session?: Session | null to guaranteed session.
• organizationMiddleware is the default entry point for organization-scoped handlers; it resolves session, membership, role, organization, and optional org DB context.
• Return predictable API shapes for list endpoints such as { items, pageSize, nextCursor }.
• Preserve the pagination style already used by the domain:
  • string cursor feeds for descending ID lists like attendance history
  • numeric offsets where current handlers already use offset pagination
• Prefer shaping response DTOs in the handler so frontend routes and tables receive the fields they actually need.

Implementation Checklist

1. Map the feature to the correct app and database package.
2. Confirm whether the endpoint is read-only or mutating, then set route method.
3. Define input schema and middleware ordering.
4. Implement handler with the correct DB client and relation loading.
5. Register the router path in the owning app and mirror it where needed.
6. Validate type usage, pagination contract, and handler response shape.

References

• For file map, conventions, and templates, read references/orpc_backend_patterns.md.