Kotlin Exposed Patterns

This gives you production-ready patterns for JetBrains Exposed ORM with all the setup details you actually need. It covers both query styles (DSL for SQL-like expressions, DAO for entity lifecycle), HikariCP connection pooling with proper isolation levels, Flyway migrations, and a repository pattern that keeps your business logic decoupled from the data layer. The examples show real things like JSONB columns, composite primary keys, joins with aggregations, and how to wrap everything in `newSuspendedTransaction` blocks for coroutine safety. If you're building a Kotlin backend and want to avoid reinventing database plumbing, this handles the boring infrastructure parts so you can focus on queries.

skills.sh installs: 5.4K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill kotlin-exposed-patterns --agent claude-code

Installs into .claude/skills of the current project.

Files

Kotlin Exposed Patterns

Comprehensive patterns for database access with JetBrains Exposed ORM, including DSL queries, DAO, transactions, and production-ready configuration.

When to Use

Setting up database access with Exposed
Writing SQL queries using Exposed DSL or DAO
Configuring connection pooling with HikariCP
Creating database migrations with Flyway
Implementing the repository pattern with Exposed
Handling JSON columns and complex queries

How It Works

Exposed provides two query styles: DSL for direct SQL-like expressions and DAO for entity lifecycle management. HikariCP manages a pool of reusable database connections configured via HikariConfig. Flyway runs versioned SQL migration scripts at startup to keep the schema in sync. All database operations run inside newSuspendedTransaction blocks for coroutine safety and atomicity. The repository pattern wraps Exposed queries behind an interface so business logic stays decoupled from the data layer and tests can use an in-memory H2 database.