Transaction Consistency Designer
Design safe transaction boundaries, rollback behavior, idempotency, locking, and consistency strategies for Kotlin + Spring business workflows. Use when a feature writes to the database, spans multiple repositories, publishes messages, calls external systems, suffers from partial commits or duplicate processing, or needs precise `@Transactional`, propagation, or isolation guidance.
Install
npx skills add JetBrains/skills --skill transaction-consistency-designergit clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/transaction-consistency-designer ~/.claude/skills/transaction-consistency-designerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Transaction Consistency Designer Source mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-09`). ## Mission Place transaction boundaries where business invariants are actually enforced, not where annotations are easiest to type. Prevent data loss, duplicate side effects, and hidden consistency bugs. ## Gather These Inputs - The business workflow step by step. - The repositories and tables touched by each step. - Current `@Transactional` annotations, propagation, isolation, and exception handling. - Any external HTTP, message broker, scheduler, or file I/O inside the workflow. - Idempotency, retry, and concurrency requirements. ## Model The Workflow Explicitly - Break the use case into state-changing steps and side effects. - Mark which steps must be atomic together and which can be asynchronous. - Mark where external systems are called. - Mark where retries may happen. - Mark the business invariant that must not be violated. ## Decision Rules - Keep one database transaction focused on one consistency boundary. - Avoid holding a database transaction open across external network calls. - Prefer idempotency keys plus unique constraints for duplicate-request safety. - Prefer the outbox pattern or post-commit publication for messages that must reflect committed state. - Choose locking strategy based on contention and correctness needs: - optimistic locking for low-contention update races
Details
- Skill name
transaction-consistency-designer- Repository
- JetBrains/skills
- Path
transaction-consistency-designer/SKILL.md- Repo updated
- 21 October 2026
FAQ
What does the Transaction Consistency Designer skill do?
Design safe transaction boundaries, rollback behavior, idempotency, locking, and consistency strategies for Kotlin + Spring business workflows. Use when a feature writes to the database, spans multiple repositories, publishes messages, calls external systems, suffers from partial commits or duplicate processing, or needs precise `@Transactional`, propagation, or isolation guidance.
How do I install the Transaction Consistency Designer skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill transaction-consistency-designer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Transaction Consistency Designer popular?
It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.
Related skills
Deploy to Vercel
398JetBrains/skills
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Vercel React Native Skills
398JetBrains/skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Vitest
398JetBrains/skills
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
Slr Prisma
124keemanxp/slr-prisma
Guide users through writing a systematic literature review (SLR) following the PRISMA 2020 framework. Use this skill whenever the user mentions 'systematic review', 'systematic literature review', 'SLR', 'PRISMA', 'PRISMA 2020', 'PRISMA flow diagram', 'PRISMA checklist', or asks for help writing, structuring, or auditing a literature review that follows reporting guidelines. Also trigger when the user asks about inclusion/exclusion criteria for a review, search strategies for databases like Scopus/WoS/PubMed, study selection processes, risk of bias assessment, or narrative synthesis for a revi
Supabase Postgres Best Practices
398JetBrains/skills
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
Upstash Redis Kv
302intellectronica/agent-skills
Read and write to Upstash Redis-compatible key-value store via REST API. Use when there is a need to save or retrieve key-value data, use Redis features (caching, counters, lists, sets, hashes, sorted sets, etc.) for the current interaction, or when the user explicitly asks to use Upstash or Redis.
Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.