Database Designer logo

Database Designer

Community
borghei
database-designer

Database design with schema analysis, index optimization, and migration generation for PostgreSQL, MySQL, MongoDB, and DynamoDB. Use when designing schemas, optimizing queries, planning migrations, or analyzing database performance.

Overview

Publisherborghei
RepositoryClaude-Skills
Skill namedatabase-designer
Stars
856
Forks
154
Bundled files
14
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Database Designer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/borghei/Claude-Skills/tree/main/engineering/database-designer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills/engineering/database-designer .claude/skills/database-designer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Database Designer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Database Designer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Database Designer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Database Designer

The agent analyzes SQL schemas for normalization compliance, recommends optimal indexes based on query patterns, and generates safe migration scripts with rollback procedures. It produces Mermaid ERDs, detects redundant indexes, and implements zero-downtime expand-contract migration patterns for PostgreSQL and MySQL.

Core Capabilities

  • Schema analysis — detect normalization violations (1NF-BCNF), missing constraints, naming issues, and data-type problems from DDL or JSON.
  • ERD generation — produce valid Mermaid entity-relationship diagrams from declared relationships.
  • Index optimization — recommend indexes from query patterns, order composite columns by selectivity, detect redundant/overlapping indexes, and find covering-index opportunities.
  • Migration generation — forward + rollback SQL between schema versions, with validation queries.
  • Zero-downtime migrations — expand-contract pattern with safe backfill for tables with 10M+ rows.
  • Database selection guidance — match workload requirements to PostgreSQL, MySQL, MongoDB, or DynamoDB.

When to Use

  • Designing or reviewing a new schema for normalization and constraints.
  • Optimizing queries by recommending or pruning indexes.
  • Planning a safe (optionally zero-downtime) migration between schema versions.
  • Analyzing database performance and relationship structure (ERD).
  • Choosing the right database technology for a workload.

Clarify First

Before designing or migrating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Task — schema analysis/ERD, index optimization, or migration generation (selects schema_analyzer.py vs index_optimizer.py vs migration_generator.py)
  • Engine — PostgreSQL, MySQL, MongoDB, or DynamoDB (drives the DDL dialect and selection guidance)
  • Schema input & query patterns — the DDL/JSON schema and the queries to optimize for (the input the tools analyze; index recommendations depend on the query patterns)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/workflows-and-tools.md — the Quick Start, three core workflows (analyze/optimize, safe migration, index optimization), and the full CLI reference (flags, usage, output formats) for schema_analyzer.py, index_optimizer.py, and migration_generator.py. Read when running the tools end-to-end.
  • references/patterns-and-troubleshooting.md — index-type selection table, anti-patterns, the troubleshooting table for tool output, and the success-criteria quality bar. Read when picking an index type, avoiding mistakes, debugging output, or checking your work.
  • references/database_selection_decision_tree.md — systematic database-technology selection based on requirements, data patterns, and operational constraints. Read when choosing between SQL and NoSQL engines.
  • references/index_strategy_patterns.md — proven patterns for index design, optimization strategies, and pitfalls to avoid. Read when designing an indexing strategy in depth.
  • references/normalization_guide.md — normal forms (1NF-BCNF), decomposition to eliminate anomalies, and integrity trade-offs. Read when normalizing or deliberately denormalizing a schema.

Scope & Limitations

Covers:

  • Schema design analysis for SQL databases (PostgreSQL, MySQL) including normalization, constraints, naming, and data types
  • Index optimization with selectivity estimation, composite index ordering, covering indexes, and redundancy detection
  • Migration generation with forward/rollback scripts, zero-downtime patterns, and validation queries
  • ERD generation in Mermaid format from DDL or JSON schema definitions

Does NOT cover:

  • Runtime query performance monitoring or live database profiling (see performance-profiler skill)
  • NoSQL-specific schema design for MongoDB, DynamoDB, or Cassandra (conceptual guidance only in the reference sections)
  • Database administration tasks such as backup/restore, replication setup, or user/role management
  • Application-level ORM configuration, connection pool tuning, or driver-specific optimizations (see database-schema-designer for ORM-adjacent patterns)

Integration Points

SkillIntegrationData Flow
migration-architectMigration strategy and execution planning for large-scale schema changesDatabase Designer generates migration SQL; Migration Architect orchestrates multi-service deployment order and rollback coordination
database-schema-designerComplementary schema design with focus on application-layer patternsDatabase Designer provides normalization analysis; Schema Designer applies ORM mapping and application modeling conventions
performance-profilerRuntime validation of index and schema optimization recommendationsDatabase Designer outputs recommended indexes; Performance Profiler measures actual query plan improvements via EXPLAIN ANALYZE
api-design-reviewerAlignment between database schema and API resource contractsDatabase Designer defines table structures; API Design Reviewer validates that endpoint schemas match underlying data models
ci-cd-pipeline-builderAutomated migration execution in deployment pipelinesDatabase Designer generates migration scripts; CI/CD Pipeline Builder integrates them into deployment stages with validation gates
observability-designerDatabase performance monitoring and alerting post-optimizationDatabase Designer identifies query patterns; Observability Designer configures slow query alerts and index usage dashboards

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Database Designer AI skill do?

Database design with schema analysis, index optimization, and migration generation for PostgreSQL, MySQL, MongoDB, and DynamoDB. Use when designing schemas, optimizing queries, planning migrations, or analyzing database performance.

Why use Database Designer on TypingMind?

Because you install it once and use it with any model. Database Designer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Database Designer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/Claude-Skills/tree/main/engineering/database-designer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Database Designer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Database Designer?

As many as you like. As long as a model supports skills, you can use Database Designer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Database Designer AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇