Database Architect

This is your go-to when you're actually designing a database from scratch or rearchitecting an existing one, not just tuning queries. It covers the full stack of decisions: picking between SQL, NoSQL, time-series, graph, or NewSQL based on your access patterns, then designing schemas with the right normalization trade-offs, indexing strategies, and partitioning schemes. The skill explicitly separates greenfield design from migrations and includes practical stuff like sharding key selection, multi-tenancy patterns, and zero-downtime migration approaches. It's opinionated about getting the data layer right from day one to avoid costly rewrites later. Best for architecture decisions, not for tweaking an existing setup you can't change.