kotlin-exposed-patterns

Automates JetBrains Exposed data access with transactions, pooling, and migrations for Kotlin.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/GGEdu/claude-god-mode-template --skill kotlin-exposed-patterns-ggedu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-exposed-patterns
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/kotlin-exposed-patterns
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill kotlin-exposed-patterns-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides production-ready data access patterns for Kotlin apps using JetBrains Exposed, reducing boilerplate and ensuring scalable database interactions.

Core Features & Use Cases

  • DSL and DAO patterns for entity queries and lifecycle management
  • Transactional safety with coroutine support via newSuspendedTransaction
  • HikariCP integration for reliable connection pooling
  • Flyway migrations for versioned schema evolution
  • Repository pattern for decoupled data access
  • Use Case: Build scalable back-end services with PostgreSQL

Quick Start

Set up a Kotlin project with Exposed, HikariCP, and Flyway migrations to implement the patterns described.

Frequently Asked Questions about kotlin-exposed-patterns

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

FAQPage Schema
How do I manage coroutine-safe transactions with Kotlin Exposed?

Manage coroutine-safe transactions with Kotlin Exposed by using newSuspendedTransaction. This pattern ensures reliable ORM-based data access by executing transaction blocks within coroutine contexts without blocking threads.

What is the best way to structure repository-based data access in Kotlin?

Structure repository-based data access in Kotlin by decoupling entity queries from business logic using the Repository pattern. This approach manages lifecycle operations via DSL and DAO patterns for maintainable data access architecture.

Does Kotlin Exposed work with HikariCP and Flyway migrations for PostgreSQL backends?

Kotlin Exposed works with HikariCP and Flyway for PostgreSQL backends. HikariCP provides reliable connection pooling, while Flyway handles versioned schema evolution to build scalable database interactions.

How do I reduce boilerplate when implementing DSL and DAO patterns in Kotlin Exposed?

Reduce boilerplate implementing DSL and DAO patterns in Kotlin Exposed by applying production-ready data access templates. These patterns automate entity queries and lifecycle management for scalable backend services.

What are the limitations of using Kotlin Exposed for ORM-based data access?

Limitations of Kotlin Exposed for ORM-based data access include the need for manual transaction scoping and architectural boilerplate. Without standardized repository patterns, maintaining complex entity lifecycles and migrations can become error-prone.