schema-design

Design BenchSight database schemas with naming conventions and migration templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill schema-design-ronniepinnell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schema-design
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/schema-design
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill schema-design-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and document comprehensive database schemas for BenchSight, ensuring consistency as new tables are added or existing ones evolve.

Core Features & Use Cases

  • Establish naming conventions for dimensions, facts, views, and staging tables.
  • Provide SQL templates and migration patterns to guide schema evolution.
  • Generate and maintain documentation outputs (e.g., docs/data/schema) for versioned reference.

Quick Start

Create or modify a table schema following the project conventions and generate the corresponding docs in docs/data/schema.

Frequently Asked Questions about schema-design

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

FAQPage Schema
How do I design and document database schemas for large scale applications?▼

Database schema design for large scale applications is managed by enforcing standardized naming conventions for dimensions, facts, and staging tables, generating SQL migration templates, and outputting versioned documentation to a dedicated docs directory.

What are the best naming conventions for SQL data modeling across hundreds of tables?▼

Standardized naming conventions for SQL data modeling across hundreds of tables differentiate dimensions, facts, views, and staging tables, ensuring consistency and clarity as the database schema evolves and new tables are added.

How do I generate database migrations when modifying existing table schemas?▼

Generating database migrations when modifying existing schemas uses provided SQL migration templates and patterns, guiding schema evolution safely while maintaining versioned reference documentation for every table change.

Does this schema design approach work for databases with over 100 existing tables?▼

Yes, this schema design approach explicitly handles databases with 139 total tables, providing structured migration pathways and standardized conventions to manage modifications across a large, existing relational data model.

When do I need to use standardized SQL templates for database migrations?▼

Standardized SQL templates for database migrations are needed whenever adding new tables or modifying existing schema, ensuring that structural changes follow established data modeling patterns and generate appropriate documentation.