database-designer-skill

Define data storage strategies and schema models from backend architecture artifacts.

Updated Jan 20, 2026

Search Tags:#data-modeling #schema-design #database-design #sql-nosql-decision #architecture-artifacts #data-lifecycle

Ready to run

npx skills add https://github.com/Galharel/my-codex-skills --skill database-designer-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-designer-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/database-designer-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill database-designer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design data storage strategies and schema models aligned with architecture and backend artifacts to guide technology choices.

Core Features & Use Cases

Evaluate SQL vs NoSQL based on access patterns, scalability, and NFRs.
Define schemas/collections, indexes, migrations, and data lifecycle policies.
Provide architecture-aligned recommendations with trade-offs and alternatives for backend systems.

Quick Start

Given the architecture artifacts, propose a data storage strategy including the database type, schema definitions, index design, and data lifecycle policies.

Frequently Asked Questions about database-designer-skill

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

FAQPage Schema

How do I decide between SQL and NoSQL for my backend data storage?▼

SQL vs NoSQL decisions are evaluated based on access patterns, scalability needs, and non-functional requirements. The Skill aligns the database type selection with your architecture artifacts to present up to three options with pros and cons.

How do I design database schemas and indexes from architecture artifacts?▼

Database schema design is defined by mapping architecture and backend artifacts to schema models, collections, and indexes. The Skill asks clarifying questions when requirements are incomplete to ensure the proposed data storage strategy fits your workloads.

What is the best way to establish data lifecycle policies for backend systems?▼

Data lifecycle policies are established by defining data storage strategies aligned with your architecture artifacts. The Skill provides recommendations for typical backend workloads, including migrations and lifecycle management.

Can I use this to get database platform recommendations with trade-offs?▼

You can get database platform recommendations with explicit trade-offs and alternatives. The Skill evaluates your backend requirements and presents up to three architecture-aligned options for user selection.

Why does database schema design require clarifying questions?▼

Database schema design requires clarifying questions when requirements are incomplete to accurately define the data storage strategy. This ensures the proposed schema models, indexes, and platform choices match your specific backend workloads.

When should I not use a NoSQL database for my data storage strategy?▼

A NoSQL database might not suit your data storage strategy if your access patterns require strict relational consistency or complex transactions. The Skill evaluates these constraints against your non-functional requirements to recommend the appropriate platform.