Database Engineer

Plans and versions database migrations while validating schemas and API standards.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tannergolden/repository --skill database-engineer-tannergolden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Database Engineer
Source: https://github.com/tannergolden/repository/tree/main/.agent/storage/skills/database
Command: npx skills add https://github.com/tannergolden/repository --skill database-engineer-tannergolden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design, migrations, data integrity, and API design governance are essential to build scalable, reliable data platforms. This skill provides a structured approach to modeling data, migration planning, and enforcing API design standards across services.

Core Features & Use Cases

  • Schema design and modeling for relational and non-relational data stores.
  • Migration planning, versioning, and rollback strategies.
  • Data integrity enforcement and API design governance across services.

Quick Start

Define a core database schema for your application, create a migration plan, and align API interfaces with your team's standards.

Frequently Asked Questions about Database Engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a database schema for scalable data-intensive applications?

Database schema design for scalable systems involves modeling relational and non-relational data stores while enforcing data integrity. It ensures schemas are validated and structured to support data-intensive applications.

What is the best way to plan database migrations and rollbacks?

Planning database migrations requires version-controlled scripts with defined rollback strategies. This ensures schema evolution is tracked, validated, and safely reversible for your data platform.

How do I enforce API design standards across multiple services?

Enforcing API design standards across services requires aligning API interfaces with standardized contracts. This governance ensures your team adheres to consistent API design rules throughout the system.

Does this database design approach work for both relational and non-relational data stores?

Yes, this database design approach supports both relational and non-relational data stores. It applies structured data modeling and migration planning to diverse data platforms requiring schema evolution.

How do I maintain data integrity during schema evolution and migrations?

Maintaining data integrity during migrations involves validating schemas and enforcing integrity rules within version-controlled changes. This prevents data corruption when updating database structures across services.

When do I need version-controlled database migrations?

You need version-controlled database migrations when building scalable, data-intensive applications that require schema evolution. It ensures structured tracking and safe rollbacks during database changes.