notepad-new-database-table

Create and validate database table schemas against a standardized checklist.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill notepad-new-database-table
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notepad-new-database-table
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.claude/skills/notepad-new-database-table
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill notepad-new-database-table

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This notepad provides a standardized reference for adding a new database table/model, ensuring consistent naming, migrations, and documentation across the codebase.

Core Features & Use Cases

  • Standardized Table Model: Enforces singular table names, UUID primary keys, and back_populates relationships.
  • Naming & Migration Guidelines: Provides conventions for names, migrations with API schema, and soft-delete patterns.
  • Use Case: When introducing a new entity like "Product" or "Order", apply the checklist to ensure proper schema, relationships, and migrations are defined.

Quick Start

Review the New Database Table Checklist and apply it to your new entity model.

Frequently Asked Questions about notepad-new-database-table

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

FAQPage Schema
What naming conventions should I follow when creating a new database table?

Standard database table naming conventions require singular table names, UUID primary keys, and back_populates for relationship setup. This ensures consistent schema definition and standardizes model creation across your backend data store.

How do I scaffold a new database table schema with migrations?

To scaffold a new database table schema, define your model with UUID primary keys and singular names, then generate migration stubs with API schema integration. This automates schema creation and validation according to standardized backend data store checklists.

Does this database table scaffolding process work with Python backend projects?

Yes, this database table scaffolding process is designed for backend data stores in Python projects. It applies during model definition, migrations, and relationship setup to ensure schema usage follows API standards.

What's the best way to implement soft deletes in a database migration?

The best way to implement soft deletes in a database migration is to apply a standardized soft-delete pattern during model definition. This ensures your schema retains records safely while maintaining consistent naming and migration guidelines.

Why do my database table relationships fail without back_populates?

Database table relationships fail without back_populates because the standardized schema requires explicit bidirectional relationship setup. Defining back_populates ensures proper linkage between models and maintains data integrity across your backend data store.