database-patterns

Standardize database schemas, migrations, and Exposed ORM repositories in Kotlin backends.

96|9|Updated Mar 21, 2026

Search Tags:#database #migrations #repository #kotlin #design-patterns #soft-delete #exposed-orm

Ready to run

npx skills add https://github.com/c0x12c/ai-toolkit --skill database-patterns-c0x12c

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: database-patterns
Source: https://github.com/c0x12c/ai-toolkit/tree/main/.codex/skills/database-patterns
Command: npx skills add https://github.com/c0x12c/ai-toolkit --skill database-patterns-c0x12c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database design and data access are often inconsistent across projects, leading to fragile schemas, manual migrations, and hard-to-maintain repositories.

Core Features & Use Cases

Standardized schema design templates, migrations, and soft-delete conventions.
Exposed ORM integration guidance and repository-pattern implementation for Kotlin projects.
Use Case: Reusable patterns across teams to enforce consistency and reduce duplication in data access layers.

Quick Start

Apply these database patterns to design schemas, migrations, and repositories in your Kotlin projects.

Frequently Asked Questions about database-patterns

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

FAQPage Schema

How do I standardize database schema design and migrations across Kotlin projects?▼

Standardize database schema design by applying proven templates for migrations, table objects, and repository patterns in Kotlin projects. This enforces consistent naming, indexing, and soft-delete behavior across teams to reduce data access duplication.

What is the best way to implement soft deletes using the Exposed ORM in Kotlin?▼

Implement soft deletes in the Exposed ORM by following standardized repository-pattern conventions that define soft-delete behavior for your entities. This ensures consistent data access and deletion handling across your Kotlin backend.

Does the repository pattern work well with Kotlin Exposed ORM for data access layers?▼

The repository pattern works with Kotlin Exposed ORM by wrapping table objects and entity data classes into standardized data access layers. This approach separates persistence logic from business logic, reducing duplication and improving maintainability.

How do I structure database migrations and entity data classes in Kotlin to avoid fragile schemas?▼

Structure database migrations and entity data classes using standardized migration templates and naming conventions. Applying these design patterns ensures consistent schema evolution, preventing fragile schemas and manual migration errors.

Can I use these database design patterns for any Kotlin backend, or do I need specific dependencies?▼

These database design patterns apply to Kotlin-based backends using the Exposed ORM without requiring additional dependencies. They provide guidance on table objects, repository patterns, and indexing to fit general backend data access needs.