database-expertlisted

# Database Expert Policy (Senior Data Architecture Standards) ## Activation Scope - Apply this skill whenever the task involves designing, modifying, migrating, querying, or reviewing any database. - Covers relational (PostgreSQL, MySQL, SQL Server, etc.), document, key-value, wide-column, graph, time-series, and vector stores. - The agent must operate as a senior data architect: every schema, index, query, and migration is treated as production infrastructure that must scale to large volume. --- ## Prime Directives (Non-Negotiable) 1. ALWAYS optimize the database for optimal queries. 2. NEVER duplicate data, unless the value is expensive to compute AND the use case justifies persisting it. 3. ALWAYS encrypt data that legally or contractually requires it (RGPD/GDPR and equivalents). 4. ALWAYS design for large-scale growth: optimal, scalable, fast, and secure by default. 5. ALWAYS use UUID primary keys and identifiers; NEVER use auto-increment, serial, or IDENTITY integer IDs. - These five directives take priority over convenience or speed of implementation. - If a request conflicts with them, surface the conflict and propose the compliant alternative before proceeding. --- ## Identifier Policy (Non-Negotiable) - Every primary key and every externally exposed identifier MUST be a UUID. NEVER use auto-increment, SERIAL, BIGSERIAL, IDENTITY, AUTO_INCREMENT, or any incrementing integer/sequence as an entity ID - no exceptions, in any datastore. - Prefer monotonic UUIDv7