Database Architect
CheckedDesigns, optimizes, and troubleshoots relational databases, ensuring performance, scalability, and data integrity for rmyndharis applications.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add rmyndharis/antigravity-skills --skill database-architect -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
rmyndharis
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned rmyndharis/antigravity-skills at 3eff4af253.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 3eff4af253
- Scanned
- 1 file, 269 lines
About this skill
What it does
This skill enables an AI agent to act as a database architect specializing in designing scalable, performant, and maintainable data layers. It assists with selecting appropriate database technologies, designing schemas and replication strategies, planning migrations, and building performance-first architectures that can scale alongside application growth. The skill covers both new (greenfield) architecture projects and re-architecting existing systems.
When to use it
- When choosing a database technology or storage pattern for a project.
- During the design of schemas, partitions, or replication strategies.
- To plan migrations or re-architecture of an existing data layer.
Key capabilities
- Technology Selection & Evaluation: Expertise in relational (PostgreSQL, MySQL, etc.), NoSQL (MongoDB, DynamoDB, etc.), time-series (TimescaleDB, InfluxDB), NewSQL (CockroachDB, TiDB), graph (Neo4j, Amazon Neptune) and other database technologies. Includes understanding consistency vs availability trade-offs and CAP theorem implications.
- Data Modeling & Schema Design: Conceptual, logical, and physical data modeling including normalization/denormalization strategies, relational design, and NoSQL design patterns.
- Hybrid Architectures: Designing polyglot persistence solutions and multi-database strategies with data synchronization.
Example prompts
- "We need to choose a database for our new application that handles high volumes of time-series data. What are my options?"
- "Can you design a schema for storing user profiles, including relationships between users and their posts?"
- "We're migrating from MySQL to PostgreSQL. Can you help me plan the migration strategy?"
Tips & gotchas
- This skill is not intended for simple query tuning or application-level feature design.
- It requires the ability to modify data models and infrastructure.
- Always validate migration plans in a staging environment before applying them to production, and ensure backups and rollbacks are available.