skills.rest
TeiNam
TeiNamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rdbms-naming

Enforce consistent naming conventions for MySQL and PostgreSQL schemas.

12|4|Updated Mar 22, 2026
Search Tags:#database#postgresql#sql#naming conventions#mysql
One-click install
npx skills add https://github.com/TeiNam/kiro-with-harness --skill rdbms-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rdbms-naming
Source: https://github.com/TeiNam/kiro-with-harness/tree/main/skills/rdbms-naming
Command: npx skills add https://github.com/TeiNam/kiro-with-harness --skill rdbms-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps maintain consistent and compliant database naming conventions for MySQL and PostgreSQL databases, improving code readability and maintainability.

Core Features & Use Cases

  • Common Naming Conventions: Applies snake_case, singular, active voice, and other best practices to table/column/index names.
  • Abbreviation Dictionary: Standardizes abbreviations for commonly used terms.
  • Index Naming: Provides guidelines for creating clear and descriptive index names.
  • Data Type Selection: Offers guidance on choosing the appropriate data types based on the database engine.
  • Use Case: For a developer working on a new database schema for a PostgreSQL database, this Skill can ensure that all naming conventions are followed, which will make the schema easier to understand and maintain.

Quick Start

Use the rdbms-naming skill to generate naming guidelines for a new table in your PostgreSQL database.

Frequently Asked Questions about rdbms-naming

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

FAQPage Schema
How do I enforce consistent database naming conventions in PostgreSQL and MySQL?▼

Database naming conventions for PostgreSQL and MySQL are enforced by standardizing table, column, and index names into snake_case and singular forms. This ensures schema readability and maintainability across your relational database design and review processes.

What is the best way to standardize SQL abbreviations for database columns and tables?▼

Standardizing SQL abbreviations requires using a dedicated abbreviation dictionary to map commonly used terms. This ensures consistent column and table naming across your database schema design and maintenance activities.

How do I generate clear index naming rules for a new database schema?▼

Clear index naming rules are generated by following descriptive guidelines that identify the table and target columns. This provides structured conventions for creating clear and descriptive index names in MySQL and PostgreSQL.

Can I use this for choosing appropriate data types based on my database engine?▼

Yes, guidelines for choosing appropriate data types are provided based on the specific database engine. This assists developers in selecting optimal column data types during PostgreSQL and MySQL schema design and review.

Does this database naming approach work with both MySQL and PostgreSQL schemas?▼

Yes, the naming convention rules are designed to work with both MySQL and PostgreSQL schemas. It focuses on applying consistent snake_case formats, singular naming, and active voice across both relational database engines.

Related Skills

Explore More Software Engineering Skills→
gaoqiongxiegaoqiongxie
1

database-designer

Generate MySQL schemas with ER diagrams, DDL scripts, and Java entity code.

Community
Intermediate
tinkermonkeytinkermonkey
1

LAYER_08_DATA_STORE

Define physical database schemas with SQL DDL for PostgreSQL, MySQL, and SQLite.

Community
Intermediate
Tonybleything76Tonybleything76

Database Designer

Analyze SQL DDL and JSON schemas for normalization and constraints.

Community
Advanced
EsposterEsposter
23

drizzle

Enforce Drizzle ORM conventions for camelCase columns, pgTable usage, and v2 relations.

Official
Advanced