Clarity DAL Architect

Data Access Layer auditing validates that your project enforces centralized DAL patterns, including repository-based data access, canonical type imports from a single location, and correct Drizzle ORM usage. This Skill reviews modules to verify auth helpers (getUserId, verifySession), type centralization in @/lib/types, and proper repository patterns under /lib/db/repositories.

The repository pattern abstracts data access logic into dedicated modules, creating a single source of truth for queries and database interactions. It centralizes how your application accesses data, making type safety consistent, encryption handling predictable, and Drizzle ORM imports traceable across your codebase.

Yes. This Skill enforces Clarity project architecture by validating that all type imports come from @/lib/types, auth helpers (getUserId, verifySession) are used consistently, and data access flows through repository modules. It catches imports from scattered locations and ensures encryption-aware balance handling throughout.

Request an architecture audit to validate that your modules follow the repository pattern, import types from the canonical centralized location, use Drizzle ORM correctly, and leverage centralized auth helpers. The audit identifies deviations from Clarity patterns and recommends corrections.

Centralized auth helpers like getUserId and verifySession provide consistent session validation and user identification across your application. Storing these in a dedicated DAL location ensures encryption-aware handling, reduces duplication, and makes authentication logic auditable and maintainable.

This Skill audits existing Drizzle ORM projects to verify they follow Clarity architecture patterns. It validates current DAL structure, type imports, repository usage, and auth patterns, then recommends refactoring where imports are scattered, patterns are inconsistent, or Drizzle usage deviates from the standard.