kotlin-exposed-patterns

Generate type-safe Exposed ORM database access patterns for Kotlin backends.

Updated Jun 25, 2026

Search Tags:#kotlin #flyway #repository-pattern #database-access #exposed-orm #hikaricp #kotlin-backend

Ready to run

npx skills add https://github.com/sumeetonline90/fitup_all --skill kotlin-exposed-patterns-sumeetonline90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kotlin-exposed-patterns
Source: https://github.com/sumeetonline90/fitup_all/tree/main/.cursor/skills/kotlin-exposed-patterns
Command: npx skills add https://github.com/sumeetonline90/fitup_all --skill kotlin-exposed-patterns-sumeetonline90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need to write repetitive, error-prone boilerplate code for database access in Kotlin applications, ensuring type-safe, maintainable data layer implementations that follow industry best practices.

Core Features & Use Cases

Type-safe Query Patterns: Use Exposed DSL for SQL-like queries or DAO entities for lifecycle-managed CRUD operations without writing raw string SQL.
Production-ready Infrastructure: Configure HikariCP connection pooling, Flyway versioned migrations, and coroutine-safe transaction handling for production deployments.
Use Case: A Kotlin backend service building user and order management functionality can use this Skill to implement a fully tested repository layer with in-memory H2 database support for unit tests.

Quick Start

Use the kotlin-exposed-patterns skill to implement a paginated user search repository with JSONB metadata support for your Kotlin backend service.

Frequently Asked Questions about kotlin-exposed-patterns

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

FAQPage Schema

How do I implement a repository pattern with Kotlin Exposed ORM?▼

To implement a repository pattern with Kotlin Exposed ORM, use standardized, production-ready templates for type-safe SQL query construction and entity lifecycle management, eliminating repetitive boilerplate code for your data layer.

Can I use Kotlin Exposed for coroutine-safe transaction handling?▼

Yes, Kotlin Exposed supports coroutine-safe transaction handling. This allows your backend service to manage database transactions safely within asynchronous workflows using production-ready patterns.

How do I configure HikariCP connection pooling and Flyway migrations in a Kotlin backend?▼

Configuring HikariCP connection pooling and Flyway versioned database migrations in a Kotlin backend involves applying infrastructure patterns that ensure reliable connection management and schema versioning for production deployments.

Does the Exposed ORM support JSONB columns and paginated search queries?▼

Yes, the Exposed ORM supports JSONB column metadata and paginated search queries. You can build paginated user search repositories with input sanitization for pattern matching queries to ensure safe data retrieval.

What is the best way to unit test a Kotlin Exposed data layer?▼

The best way to unit test a Kotlin Exposed data layer is using in-memory H2 database support. This approach provides a testable data layer design that validates CRUD operations without requiring a full PostgreSQL production environment.

Do I need raw SQL for batch CRUD operations using JetBrains Exposed?▼

No, you do not need raw SQL for batch CRUD operations using JetBrains Exposed. You can use the Exposed DSL for SQL-like queries or DAO entities for lifecycle-managed CRUD operations without writing error-prone string SQL.