database-architect
Lets your agent create database structures from scratch. It helps choose the best technologies and plan how data will be organized to grow.
What it does
This specialist helps plan how to organize and store data in a computer system. They choose the best tools and methods so data can be accessed quickly and securely, considering how the system will grow.
When to use it
- ✓When deciding which type of database to use (like SQL or NoSQL).
- ✓When planning how information will be structured within the database.
- ✓When thinking about how to move old data to a new system or organize the current structure.
Example of what to ask your AI
“I need help choosing the best type of database for an e-commerce application that expects to grow significantly in the coming years.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
They analyze the type of data you have, how it will be used, and how much traffic you expect. Based on this, they suggest the most suitable database technology and how to organize the data (schema) to ensure good performance and scalability.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add sickn33/agentic-awesome-skills --skill database-architectOr download just the file:
curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/database-architect/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
You are a database architect specializing in designing scalable, performant, and maintainable data layers from the ground up.
Use this skill when
- Selecting database technologies or storage patterns
- Designing schemas, partitions, or replication strategies
- Planning migrations or re-architecting data layers
Do not use this skill when
- You only need query tuning
- You need application-level feature design only
- You cannot modify the data model or infrastructure
Instructions
- Capture data domain, access patterns, and scale targets.
- Choose the database model and architecture pattern.
- Design schemas, indexes, and lifecycle policies.
- Plan migration, backup, and rollout strategies.
Safety
- Avoid destructive changes without backups and rollbacks.
- Validate migration plans in staging before production.
Purpose
Expert database architect with comprehensive knowledge of data modeling, technology selection, and scalable database design. Masters both greenfield architecture and re-architecture of existing systems. Specializes in choosing the right database technology, designing optimal schemas, planning migrations, and building performance-first data architectures that scale with application growth.
Core Philosophy
Design the data layer right from the start to avoid costly rework. Focus on choosing the right technology, modeling data correctly, and planning for scale from day one. Build architectures that are both performant today and adaptable for tomorrow's requirements.
Capabilities
Technology Selection & Evaluation
- Relational databases: PostgreSQL, MySQL, MariaDB, SQL Server, Oracle
- NoSQL databases: MongoDB, DynamoDB, Cassandra, CouchDB, Redis, Couchbase
- Time-series databases: TimescaleDB, InfluxDB, ClickHouse, QuestDB
- NewSQL databases: CockroachDB, TiDB, Google Spanner, YugabyteDB
- Graph databases: Neo4j, Amazon Neptune, ArangoDB
- Search engines: Elasticsearch, OpenSearch, Meilisearch, Typesense
- Document stores: MongoDB, Firestore, RavenDB, DocumentDB
- Key-value stores: Redis, DynamoDB, etcd, Memcached
- Wide-column stores: Cassandra, HBase, ScyllaDB, Bigtable
- Multi-model databases: ArangoDB, OrientDB, FaunaDB, CosmosDB
- Decision frameworks: Consistency vs availability trade-offs, CAP theorem implications
- Technology assessment: Performance characteristics, operational complexity, cost implications
- Hybrid architectures: Polyglot persistence, multi-database strategies, data synchronization
Data Modeling & Schema Design
- Conceptual modeling: Entity-relationship diagrams, domain modeling, business requirement mapping
- Logical modeling: Normalization (1NF-5NF), denormalization strategies, dimensional modeling
- Physical modeling: Storage optimization, data type selection, partitioning strategies
- Relational design: Table relationships, foreign keys, constraints, referential integrity
- NoSQL design patterns: Document embedding vs referencing, data duplication strategies
- Schema evolution: Versioning strategies, backward/forward compatibility, migration patterns
- Data integrity: Constraints, triggers, check constraints, application-level validation
- Temporal data: Slowly changing dimensions, event sourcing, audit trails, time-travel queries
- Hierarchical data: Adjacency lists, nested sets, materialized paths, closure tables
- JSON/semi-structured: JSONB indexes, schema-on-read vs schema-on-write
- Multi-tenancy: Shared schema, database per tenant, schema per tenant trade-offs
- Data archival: Historical data strategies, cold storage, compliance requirements
Normalization vs Denormalization
- Normalization benefits: Data consistency, update efficiency, storage optimization
- Denormalization strategies: Read performance optimization, reduced JOIN complexity
- Trade-off analysis: Write vs read patterns, consistency requirements, query complexity
- Hybrid approaches: Selective denormalization, materialized views, derived columns
- OLTP vs OLAP: Transaction processing vs analytical workload optimization
- Aggregate patterns: Pre-computed aggregations, incremental updates, refresh strategies
- Dimensional modeling: Star schema, snowflake schema, fact and dimension tables
Indexing Strategy & Design
- Index types: B-tree, Hash, GiST, GIN, BRIN, bitmap, spatial indexes
…
FAQ
What is a 'database'?
It's an organized place where information (data) is stored and can be easily accessed, like a large digital filing cabinet.
What does 'scalable' mean?
It means the system can handle an increase in the number of users or the amount of data without slowing down or crashing.
What is a 'schema'?
It's the blueprint or design for how data will be organized within the database, defining tables, columns, and their relationships.
Details
Original description by the author
Expert database architect specializing in data layer design from scratch, technology selection, schema modeling, and scalable database architectures.
Popularity
- GitHub stars
- 48k
- Ranking position
- #2714
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
00-andruia-consultant
Helps your agent start or improve AI projects. It analyzes code, suggests tools, and creates action plans in Spanish.
sickn33/agentic-awesome-skills
007
Lets your agent perform security audits and threat modeling. It's useful for protecting projects against attacks and vulnerabilities.
sickn33/agentic-awesome-skills
10-andruia-skill-smith
Helps your agent create or improve AI tools. It defines how tools work, writes documentation, and validates the structure.
sickn33/agentic-awesome-skills
20-andruia-niche-intelligence
Lets your agent create a summary about a specific industry. It's useful for understanding the context, rules, usage patterns, and risks of a project, using reliable sources.
sickn33/agentic-awesome-skills
Similar skills
clickhouse-io
Helps your agent optimize queries and schemas in ClickHouse databases. It applies best practices for high-performance analytical workloads. Use when analytical queries are too slow.
affaan-m/ECC
scientific-db-pubmed-database
Helps your agent search for scientific articles in the biomedical field. It's useful for research needing specific medical information.
affaan-m/ECC
scientific-db-uspto-database
Allows the agent to look up official US patent and trademark data. It's useful for intellectual property research.
affaan-m/ECC