[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-transaction-consistency-designer":3,"mdc-oge0gx-key":39,"related-repo-jetbrains-transaction-consistency-designer":571,"related-org-jetbrains-transaction-consistency-designer":691},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":34,"sourceUrl":37,"mdContent":38},"transaction-consistency-designer","design transaction consistency for Kotlin workflows","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"jetbrains","JetBrains","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fjetbrains.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"Kotlin","kotlin","tag",{"name":17,"slug":18,"type":15},"Architecture","architecture",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Database","database",{"name":26,"slug":27,"type":15},"Engineering","engineering",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:51.438023",null,17,[],{"repoUrl":29,"stars":28,"forks":32,"topics":35,"description":36},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Ftransaction-consistency-designer","---\nname: transaction-consistency-designer\ndescription: 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.\nmetadata:\n  short-description: \"Place safe transaction boundaries\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-consistency-designer\n---\n\n# Transaction Consistency Designer\n\nSource mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-09`).\n\n## Mission\n\nPlace transaction boundaries where business invariants are actually enforced, not where annotations are easiest to type.\nPrevent data loss, duplicate side effects, and hidden consistency bugs.\n\n## Gather These Inputs\n\n- The business workflow step by step.\n- The repositories and tables touched by each step.\n- Current `@Transactional` annotations, propagation, isolation, and exception handling.\n- Any external HTTP, message broker, scheduler, or file I\u002FO inside the workflow.\n- Idempotency, retry, and concurrency requirements.\n\n## Model The Workflow Explicitly\n\n- Break the use case into state-changing steps and side effects.\n- Mark which steps must be atomic together and which can be asynchronous.\n- Mark where external systems are called.\n- Mark where retries may happen.\n- Mark the business invariant that must not be violated.\n\n## Decision Rules\n\n- Keep one database transaction focused on one consistency boundary.\n- Avoid holding a database transaction open across external network calls.\n- Prefer idempotency keys plus unique constraints for duplicate-request safety.\n- Prefer the outbox pattern or post-commit publication for messages that must reflect committed state.\n- Choose locking strategy based on contention and correctness needs:\n  - optimistic locking for low-contention update races\n  - unique constraints for duplicate prevention\n  - pessimistic locking only when contention and correctness justify it\n\n## Spring-Specific Checks\n\n- Verify whether `@Transactional` is on a proxied public entry point.\n- Verify whether self-invocation bypasses the transaction boundary.\n- Verify rollback rules. By default, unchecked exceptions roll back, checked exceptions may not.\n- Verify whether `readOnly = true` is used only where appropriate.\n- Verify whether `REQUIRES_NEW` is truly required or is masking a design issue.\n- Treat `NESTED` as database- and platform-dependent, not a universal escape hatch.\n\n## Anti-Patterns To Flag\n\n- `@Transactional` on controllers by default.\n- One transaction that does database writes and then performs slow HTTP calls.\n- Catching exceptions inside the transaction and converting them to success-like flows.\n- Publishing irreversible side effects before commit.\n- Assuming retries are safe without idempotency.\n- Using a bigger propagation setting to hide unclear boundaries.\n\n## Advanced Consistency Nuances\n\n- Distinguish duplicate prevention from concurrency control. A unique constraint solves one class of race, not lost updates or write skew.\n- Remember that many integrity failures surface on flush or commit, not at the line that changed the entity. Design tests and exception handling accordingly.\n- `UnexpectedRollbackException` often means an inner operation marked the transaction rollback-only even though the outer layer tried to return success.\n- Isolation levels are database-specific in effect. The same setting on Postgres, MySQL, and SQL Server may protect different anomalies.\n- Deadlock and serialization-failure retries belong at a carefully chosen outer boundary. Retrying a half-executed workflow with external side effects is dangerous.\n- `@TransactionalEventListener` and `TransactionSynchronization` are phase-sensitive. Choose before-commit, after-commit, or after-rollback behavior deliberately.\n- If the workflow crosses service boundaries, distinguish local transaction design from saga or orchestration design. Do not pretend one local transaction can guarantee distributed consistency.\n- In reactive or coroutine transaction flows, verify which transaction manager and context propagation model is actually in use. Imperative assumptions often fail there.\n\n## Expert Heuristics\n\n- Start from the invariant, not from the annotation. Ask what must never be observably false to users or downstream systems.\n- Prefer database-enforced invariants for uniqueness and impossible states, then use application logic to make violations rare and understandable.\n- If a workflow mixes command and query steps, decide whether read-your-write guarantees are required immediately or whether eventual consistency is acceptable.\n- If the team wants `REQUIRES_NEW`, ask whether they are isolating audit logging, masking rollback behavior, or compensating for a larger design problem.\n\n## Output Contract\n\nReturn these sections:\n\n- `Consistency goal`: the business invariant being protected.\n- `Recommended boundary`: where the main transaction starts and ends.\n- `Propagation and isolation`: only the settings that matter and why.\n- `Idempotency and concurrency`: duplicate handling, locking, and retry safety.\n- `External side effects`: what must happen outside the transaction or through outbox-style patterns.\n- `Verification`: tests or scenarios that prove rollback, duplicate handling, and conflict behavior.\n\n## Guardrails\n\n- Do not put `@Transactional` on every service method by default.\n- Do not recommend distributed 2PC or XA unless the project already uses it and truly requires it.\n- Do not ignore the cost of holding database connections during external calls.\n- Do not treat duplicate prevention as an application-only concern when the database can enforce it.\n\n## Quality Bar\n\nA good run of this skill turns a vague workflow into explicit consistency boundaries and testable invariants.\nA bad run decorates methods with `@Transactional` without modeling failure paths, retries, and side effects.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":13,"source":43},"Place safe transaction boundaries","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Ftransaction-consistency-designer",{"type":45,"children":46},"root",[47,55,78,85,90,96,134,140,168,174,220,226,288,294,332,338,401,407,437,443,448,517,523,553,559],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Transaction Consistency Designer",{"type":48,"tag":56,"props":57,"children":58},"p",{},[59,61,68,70,76],{"type":53,"value":60},"Source mapping: Tier 1 critical skill derived from ",{"type":48,"tag":62,"props":63,"children":65},"code",{"className":64},[],[66],{"type":53,"value":67},"Kotlin_Spring_Developer_Pipeline.md",{"type":53,"value":69}," (",{"type":48,"tag":62,"props":71,"children":73},{"className":72},[],[74],{"type":53,"value":75},"SK-09",{"type":53,"value":77},").",{"type":48,"tag":79,"props":80,"children":82},"h2",{"id":81},"mission",[83],{"type":53,"value":84},"Mission",{"type":48,"tag":56,"props":86,"children":87},{},[88],{"type":53,"value":89},"Place transaction boundaries where business invariants are actually enforced, not where annotations are easiest to type.\nPrevent data loss, duplicate side effects, and hidden consistency bugs.",{"type":48,"tag":79,"props":91,"children":93},{"id":92},"gather-these-inputs",[94],{"type":53,"value":95},"Gather These Inputs",{"type":48,"tag":97,"props":98,"children":99},"ul",{},[100,106,111,124,129],{"type":48,"tag":101,"props":102,"children":103},"li",{},[104],{"type":53,"value":105},"The business workflow step by step.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"The repositories and tables touched by each step.",{"type":48,"tag":101,"props":112,"children":113},{},[114,116,122],{"type":53,"value":115},"Current ",{"type":48,"tag":62,"props":117,"children":119},{"className":118},[],[120],{"type":53,"value":121},"@Transactional",{"type":53,"value":123}," annotations, propagation, isolation, and exception handling.",{"type":48,"tag":101,"props":125,"children":126},{},[127],{"type":53,"value":128},"Any external HTTP, message broker, scheduler, or file I\u002FO inside the workflow.",{"type":48,"tag":101,"props":130,"children":131},{},[132],{"type":53,"value":133},"Idempotency, retry, and concurrency requirements.",{"type":48,"tag":79,"props":135,"children":137},{"id":136},"model-the-workflow-explicitly",[138],{"type":53,"value":139},"Model The Workflow Explicitly",{"type":48,"tag":97,"props":141,"children":142},{},[143,148,153,158,163],{"type":48,"tag":101,"props":144,"children":145},{},[146],{"type":53,"value":147},"Break the use case into state-changing steps and side effects.",{"type":48,"tag":101,"props":149,"children":150},{},[151],{"type":53,"value":152},"Mark which steps must be atomic together and which can be asynchronous.",{"type":48,"tag":101,"props":154,"children":155},{},[156],{"type":53,"value":157},"Mark where external systems are called.",{"type":48,"tag":101,"props":159,"children":160},{},[161],{"type":53,"value":162},"Mark where retries may happen.",{"type":48,"tag":101,"props":164,"children":165},{},[166],{"type":53,"value":167},"Mark the business invariant that must not be violated.",{"type":48,"tag":79,"props":169,"children":171},{"id":170},"decision-rules",[172],{"type":53,"value":173},"Decision Rules",{"type":48,"tag":97,"props":175,"children":176},{},[177,182,187,192,197],{"type":48,"tag":101,"props":178,"children":179},{},[180],{"type":53,"value":181},"Keep one database transaction focused on one consistency boundary.",{"type":48,"tag":101,"props":183,"children":184},{},[185],{"type":53,"value":186},"Avoid holding a database transaction open across external network calls.",{"type":48,"tag":101,"props":188,"children":189},{},[190],{"type":53,"value":191},"Prefer idempotency keys plus unique constraints for duplicate-request safety.",{"type":48,"tag":101,"props":193,"children":194},{},[195],{"type":53,"value":196},"Prefer the outbox pattern or post-commit publication for messages that must reflect committed state.",{"type":48,"tag":101,"props":198,"children":199},{},[200,202],{"type":53,"value":201},"Choose locking strategy based on contention and correctness needs:\n",{"type":48,"tag":97,"props":203,"children":204},{},[205,210,215],{"type":48,"tag":101,"props":206,"children":207},{},[208],{"type":53,"value":209},"optimistic locking for low-contention update races",{"type":48,"tag":101,"props":211,"children":212},{},[213],{"type":53,"value":214},"unique constraints for duplicate prevention",{"type":48,"tag":101,"props":216,"children":217},{},[218],{"type":53,"value":219},"pessimistic locking only when contention and correctness justify it",{"type":48,"tag":79,"props":221,"children":223},{"id":222},"spring-specific-checks",[224],{"type":53,"value":225},"Spring-Specific Checks",{"type":48,"tag":97,"props":227,"children":228},{},[229,241,246,251,263,275],{"type":48,"tag":101,"props":230,"children":231},{},[232,234,239],{"type":53,"value":233},"Verify whether ",{"type":48,"tag":62,"props":235,"children":237},{"className":236},[],[238],{"type":53,"value":121},{"type":53,"value":240}," is on a proxied public entry point.",{"type":48,"tag":101,"props":242,"children":243},{},[244],{"type":53,"value":245},"Verify whether self-invocation bypasses the transaction boundary.",{"type":48,"tag":101,"props":247,"children":248},{},[249],{"type":53,"value":250},"Verify rollback rules. By default, unchecked exceptions roll back, checked exceptions may not.",{"type":48,"tag":101,"props":252,"children":253},{},[254,255,261],{"type":53,"value":233},{"type":48,"tag":62,"props":256,"children":258},{"className":257},[],[259],{"type":53,"value":260},"readOnly = true",{"type":53,"value":262}," is used only where appropriate.",{"type":48,"tag":101,"props":264,"children":265},{},[266,267,273],{"type":53,"value":233},{"type":48,"tag":62,"props":268,"children":270},{"className":269},[],[271],{"type":53,"value":272},"REQUIRES_NEW",{"type":53,"value":274}," is truly required or is masking a design issue.",{"type":48,"tag":101,"props":276,"children":277},{},[278,280,286],{"type":53,"value":279},"Treat ",{"type":48,"tag":62,"props":281,"children":283},{"className":282},[],[284],{"type":53,"value":285},"NESTED",{"type":53,"value":287}," as database- and platform-dependent, not a universal escape hatch.",{"type":48,"tag":79,"props":289,"children":291},{"id":290},"anti-patterns-to-flag",[292],{"type":53,"value":293},"Anti-Patterns To Flag",{"type":48,"tag":97,"props":295,"children":296},{},[297,307,312,317,322,327],{"type":48,"tag":101,"props":298,"children":299},{},[300,305],{"type":48,"tag":62,"props":301,"children":303},{"className":302},[],[304],{"type":53,"value":121},{"type":53,"value":306}," on controllers by default.",{"type":48,"tag":101,"props":308,"children":309},{},[310],{"type":53,"value":311},"One transaction that does database writes and then performs slow HTTP calls.",{"type":48,"tag":101,"props":313,"children":314},{},[315],{"type":53,"value":316},"Catching exceptions inside the transaction and converting them to success-like flows.",{"type":48,"tag":101,"props":318,"children":319},{},[320],{"type":53,"value":321},"Publishing irreversible side effects before commit.",{"type":48,"tag":101,"props":323,"children":324},{},[325],{"type":53,"value":326},"Assuming retries are safe without idempotency.",{"type":48,"tag":101,"props":328,"children":329},{},[330],{"type":53,"value":331},"Using a bigger propagation setting to hide unclear boundaries.",{"type":48,"tag":79,"props":333,"children":335},{"id":334},"advanced-consistency-nuances",[336],{"type":53,"value":337},"Advanced Consistency Nuances",{"type":48,"tag":97,"props":339,"children":340},{},[341,346,351,362,367,372,391,396],{"type":48,"tag":101,"props":342,"children":343},{},[344],{"type":53,"value":345},"Distinguish duplicate prevention from concurrency control. A unique constraint solves one class of race, not lost updates or write skew.",{"type":48,"tag":101,"props":347,"children":348},{},[349],{"type":53,"value":350},"Remember that many integrity failures surface on flush or commit, not at the line that changed the entity. Design tests and exception handling accordingly.",{"type":48,"tag":101,"props":352,"children":353},{},[354,360],{"type":48,"tag":62,"props":355,"children":357},{"className":356},[],[358],{"type":53,"value":359},"UnexpectedRollbackException",{"type":53,"value":361}," often means an inner operation marked the transaction rollback-only even though the outer layer tried to return success.",{"type":48,"tag":101,"props":363,"children":364},{},[365],{"type":53,"value":366},"Isolation levels are database-specific in effect. The same setting on Postgres, MySQL, and SQL Server may protect different anomalies.",{"type":48,"tag":101,"props":368,"children":369},{},[370],{"type":53,"value":371},"Deadlock and serialization-failure retries belong at a carefully chosen outer boundary. Retrying a half-executed workflow with external side effects is dangerous.",{"type":48,"tag":101,"props":373,"children":374},{},[375,381,383,389],{"type":48,"tag":62,"props":376,"children":378},{"className":377},[],[379],{"type":53,"value":380},"@TransactionalEventListener",{"type":53,"value":382}," and ",{"type":48,"tag":62,"props":384,"children":386},{"className":385},[],[387],{"type":53,"value":388},"TransactionSynchronization",{"type":53,"value":390}," are phase-sensitive. Choose before-commit, after-commit, or after-rollback behavior deliberately.",{"type":48,"tag":101,"props":392,"children":393},{},[394],{"type":53,"value":395},"If the workflow crosses service boundaries, distinguish local transaction design from saga or orchestration design. Do not pretend one local transaction can guarantee distributed consistency.",{"type":48,"tag":101,"props":397,"children":398},{},[399],{"type":53,"value":400},"In reactive or coroutine transaction flows, verify which transaction manager and context propagation model is actually in use. Imperative assumptions often fail there.",{"type":48,"tag":79,"props":402,"children":404},{"id":403},"expert-heuristics",[405],{"type":53,"value":406},"Expert Heuristics",{"type":48,"tag":97,"props":408,"children":409},{},[410,415,420,425],{"type":48,"tag":101,"props":411,"children":412},{},[413],{"type":53,"value":414},"Start from the invariant, not from the annotation. Ask what must never be observably false to users or downstream systems.",{"type":48,"tag":101,"props":416,"children":417},{},[418],{"type":53,"value":419},"Prefer database-enforced invariants for uniqueness and impossible states, then use application logic to make violations rare and understandable.",{"type":48,"tag":101,"props":421,"children":422},{},[423],{"type":53,"value":424},"If a workflow mixes command and query steps, decide whether read-your-write guarantees are required immediately or whether eventual consistency is acceptable.",{"type":48,"tag":101,"props":426,"children":427},{},[428,430,435],{"type":53,"value":429},"If the team wants ",{"type":48,"tag":62,"props":431,"children":433},{"className":432},[],[434],{"type":53,"value":272},{"type":53,"value":436},", ask whether they are isolating audit logging, masking rollback behavior, or compensating for a larger design problem.",{"type":48,"tag":79,"props":438,"children":440},{"id":439},"output-contract",[441],{"type":53,"value":442},"Output Contract",{"type":48,"tag":56,"props":444,"children":445},{},[446],{"type":53,"value":447},"Return these sections:",{"type":48,"tag":97,"props":449,"children":450},{},[451,462,473,484,495,506],{"type":48,"tag":101,"props":452,"children":453},{},[454,460],{"type":48,"tag":62,"props":455,"children":457},{"className":456},[],[458],{"type":53,"value":459},"Consistency goal",{"type":53,"value":461},": the business invariant being protected.",{"type":48,"tag":101,"props":463,"children":464},{},[465,471],{"type":48,"tag":62,"props":466,"children":468},{"className":467},[],[469],{"type":53,"value":470},"Recommended boundary",{"type":53,"value":472},": where the main transaction starts and ends.",{"type":48,"tag":101,"props":474,"children":475},{},[476,482],{"type":48,"tag":62,"props":477,"children":479},{"className":478},[],[480],{"type":53,"value":481},"Propagation and isolation",{"type":53,"value":483},": only the settings that matter and why.",{"type":48,"tag":101,"props":485,"children":486},{},[487,493],{"type":48,"tag":62,"props":488,"children":490},{"className":489},[],[491],{"type":53,"value":492},"Idempotency and concurrency",{"type":53,"value":494},": duplicate handling, locking, and retry safety.",{"type":48,"tag":101,"props":496,"children":497},{},[498,504],{"type":48,"tag":62,"props":499,"children":501},{"className":500},[],[502],{"type":53,"value":503},"External side effects",{"type":53,"value":505},": what must happen outside the transaction or through outbox-style patterns.",{"type":48,"tag":101,"props":507,"children":508},{},[509,515],{"type":48,"tag":62,"props":510,"children":512},{"className":511},[],[513],{"type":53,"value":514},"Verification",{"type":53,"value":516},": tests or scenarios that prove rollback, duplicate handling, and conflict behavior.",{"type":48,"tag":79,"props":518,"children":520},{"id":519},"guardrails",[521],{"type":53,"value":522},"Guardrails",{"type":48,"tag":97,"props":524,"children":525},{},[526,538,543,548],{"type":48,"tag":101,"props":527,"children":528},{},[529,531,536],{"type":53,"value":530},"Do not put ",{"type":48,"tag":62,"props":532,"children":534},{"className":533},[],[535],{"type":53,"value":121},{"type":53,"value":537}," on every service method by default.",{"type":48,"tag":101,"props":539,"children":540},{},[541],{"type":53,"value":542},"Do not recommend distributed 2PC or XA unless the project already uses it and truly requires it.",{"type":48,"tag":101,"props":544,"children":545},{},[546],{"type":53,"value":547},"Do not ignore the cost of holding database connections during external calls.",{"type":48,"tag":101,"props":549,"children":550},{},[551],{"type":53,"value":552},"Do not treat duplicate prevention as an application-only concern when the database can enforce it.",{"type":48,"tag":79,"props":554,"children":556},{"id":555},"quality-bar",[557],{"type":53,"value":558},"Quality Bar",{"type":48,"tag":56,"props":560,"children":561},{},[562,564,569],{"type":53,"value":563},"A good run of this skill turns a vague workflow into explicit consistency boundaries and testable invariants.\nA bad run decorates methods with ",{"type":48,"tag":62,"props":565,"children":567},{"className":566},[],[568],{"type":53,"value":121},{"type":53,"value":570}," without modeling failure paths, retries, and side effects.",{"items":572,"total":690},[573,592,607,623,638,657,674],{"slug":574,"name":574,"fn":575,"description":576,"org":577,"tags":578,"stars":28,"repoUrl":29,"updatedAt":591},"algorithmic-art","create generative art with p5.js","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[579,582,585,588],{"name":580,"slug":581,"type":15},"Creative","creative",{"name":583,"slug":584,"type":15},"Generative Art","generative-art",{"name":586,"slug":587,"type":15},"Graphics","graphics",{"name":589,"slug":590,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":28,"repoUrl":29,"updatedAt":606},"antfu","configure JavaScript projects with Anthony Fu's tools","Anthony Fu's opinionated tooling and conventions for JavaScript\u002FTypeScript projects. Use when setting up new projects, configuring ESLint\u002FPrettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[598,601,602,603],{"name":599,"slug":600,"type":15},"Best Practices","best-practices",{"name":26,"slug":27,"type":15},{"name":589,"slug":590,"type":15},{"name":604,"slug":605,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":608,"name":608,"fn":609,"description":610,"org":611,"tags":612,"stars":28,"repoUrl":29,"updatedAt":622},"brand-guidelines","apply Anthropic brand guidelines","Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[613,616,619],{"name":614,"slug":615,"type":15},"Branding","branding",{"name":617,"slug":618,"type":15},"Design","design",{"name":620,"slug":621,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":28,"repoUrl":29,"updatedAt":637},"canvas-design","create visual art and design assets","Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[629,630,631,634],{"name":580,"slug":581,"type":15},{"name":617,"slug":618,"type":15},{"name":632,"slug":633,"type":15},"Images","images",{"name":635,"slug":636,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":28,"repoUrl":29,"updatedAt":656},"ci-cd-containerization-advisor","design CI\u002FCD pipelines for Kotlin applications","Design reproducible build, image, and deployment pipelines for Kotlin plus Spring applications, including CI verification, layered containers, rollout safety, and deployment-time migration coordination. Use when creating or improving Dockerfiles, CI workflows, image hardening, Kubernetes manifests, release gates, or deployment strategies for Spring Boot services, especially where build reproducibility and operational safety matter.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[644,647,650,653,654,655],{"name":645,"slug":646,"type":15},"CI\u002FCD","ci-cd",{"name":648,"slug":649,"type":15},"Containers","containers",{"name":651,"slug":652,"type":15},"Deployment","deployment",{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":28,"repoUrl":29,"updatedAt":673},"cloudflare-deploy","deploy applications to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[663,666,669,672],{"name":664,"slug":665,"type":15},"Cloudflare","cloudflare",{"name":667,"slug":668,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":670,"slug":671,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":651,"slug":652,"type":15},"2026-07-17T06:04:42.853896",{"slug":675,"name":675,"fn":676,"description":677,"org":678,"tags":679,"stars":28,"repoUrl":29,"updatedAt":689},"compose-ui-control","interact with Compose Desktop applications","Control a running Compose Desktop application via HTTP. Use when you need to interact with UI elements, click buttons, enter text, wait for elements to appear, or capture screenshots in a Compose Desktop app that has compose-ui-test-server enabled.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[680,683,686],{"name":681,"slug":682,"type":15},"Automation","automation",{"name":684,"slug":685,"type":15},"Desktop","desktop",{"name":687,"slug":688,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":692,"total":815},[693,707,716,725,736,746,755,764,773,783,792,805],{"slug":694,"name":694,"fn":695,"description":696,"org":697,"tags":698,"stars":704,"repoUrl":705,"updatedAt":706},"mps-aspect-accessories","configure JetBrains MPS module dependencies","Wire MPS module and model dependencies, used languages, used devkits, extended languages, runtime solutions, accessory models, and language\u002Fdependency versions. Use when adding\u002Fremoving module dependencies, importing languages or devkits into a model, declaring runtime solutions, or shipping accessory content visible to consumers without explicit import.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[699,700,703],{"name":17,"slug":18,"type":15},{"name":701,"slug":702,"type":15},"Configuration","configuration",{"name":26,"slug":27,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":708,"name":708,"fn":709,"description":710,"org":711,"tags":712,"stars":704,"repoUrl":705,"updatedAt":715},"mps-aspect-actions","define and edit MPS node factories","Use when defining or editing MPS node factories (the \"actions\" aspect) — `NodeFactories` roots, per-concept `NodeFactory` setup functions that initialize a freshly created node and optionally copy data from a replaced `sampleNode`, plus the actions aspect's `CopyPasteHandlers` and `PasteWrappers` roots. Reach for this skill when a substitution, side transform, completion replacement, or `add new initialized(...)` should preserve fields from the node it is replacing, or when defaults set in a constructor are not enough.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[713,714],{"name":17,"slug":18,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:04:48.066901",{"slug":717,"name":717,"fn":718,"description":719,"org":720,"tags":721,"stars":704,"repoUrl":705,"updatedAt":724},"mps-aspect-behavior","define and edit MPS concept behavior","Use when defining or editing MPS `ConceptBehavior` — per-concept methods (non-virtual \u002F virtual \u002F abstract \u002F static \u002F virtual static), constructors, virtual dispatch (MRO), super and interface-default calls (`super\u003CInterface>.method`), overriding methods from `lang.core.behavior` interfaces such as `ScopeProvider.getScope` \u002F `INamedConcept.getName` \u002F `BaseConcept.getPresentation`, calling sibling methods (`LocalBehaviorMethodCall`) and behavior methods from other aspects via `node.method(...)`. Reach for this skill whenever the task involves authoring or modifying `\u003Clang>\u002FlanguageModels\u002Fbehavior.mps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[722,723],{"name":17,"slug":18,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:45:21.757084",{"slug":726,"name":726,"fn":727,"description":728,"org":729,"tags":730,"stars":704,"repoUrl":705,"updatedAt":735},"mps-aspect-constraints","define JetBrains MPS language constraints","Use when defining or editing MPS language constraints — property validators \u002F setters \u002F getters, referent search scopes (imperative or inherited via `ScopeProvider.getScope`), `referentSetHandler` side effects, default-scope blocks, `canBeChild` \u002F `canBeParent` \u002F `canBeAncestor` \u002F `canBeRoot` placement rules, `defaultConcreteConcept` for abstract concepts, `set \u003Cread-only>` and `{name}` aliasing, and scope helpers (`SimpleRoleScope`, `ListScope`, `CompositeScope`, `HidingByNameScope`). Reach for this skill whenever the task involves authoring or modifying `\u003Clang>\u002FlanguageModels\u002Fconstraints.mps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[731,732],{"name":17,"slug":18,"type":15},{"name":733,"slug":734,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":737,"name":737,"fn":738,"description":739,"org":740,"tags":741,"stars":704,"repoUrl":705,"updatedAt":745},"mps-aspect-dataflow","define and debug MPS dataflow builders","Use when defining or debugging MPS dataflow builders for a concept — control\u002Fdata flow declarations that drive reachability analysis and variable-use checking. Covers DataFlowBuilderDeclaration, BuilderBlock, emit instructions (code for, jump, ifjump, label, read, write, ret, mayBeUnreachable), positions (AfterPosition, BeforePosition, LabelPosition), the jetbrains.mps.lang.dataFlow language, the NodeParameter implicit, BL+smodel usage inside builder bodies, and IBuilderMode for advanced analyses such as nullable\u002Fnon-null tracking.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[742],{"name":743,"slug":744,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":747,"name":747,"fn":748,"description":749,"org":750,"tags":751,"stars":704,"repoUrl":705,"updatedAt":754},"mps-aspect-editor","define MPS editor layouts","Use when creating or changing MPS editor definitions — the overall workflow from scaffolding a `ConceptEditorDeclaration` through componentizing reusable `EditorComponentDeclaration`s, refining cell models and cell layouts, applying style sheets and indent-layout style items, wiring smart references, leveraging inheritance via super-concepts and interfaces, inspecting (`print_node_json`, `show_node_representation`) and validating (`check_root_node_problems`). Covers `jetbrains.mps.lang.editor` cell models (`CellModel_RefNode`\u002F`CellModel_RefNodeList`\u002F`CellModel_RefCell`\u002F`CellModel_Property`\u002F`CellModel_Constant`), layout choices, and JSON blueprints for common editor shapes. For the non-layout side (action maps, keymaps, transformation\u002Fsubstitute menus) use `mps-aspect-editor-menus-and-keymaps`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[752,753],{"name":617,"slug":618,"type":15},{"name":687,"slug":688,"type":15},"2026-07-23T05:41:56.638151",{"slug":756,"name":756,"fn":757,"description":758,"org":759,"tags":760,"stars":704,"repoUrl":705,"updatedAt":763},"mps-aspect-editor-menus-and-keymaps","author MPS editor menus and keymaps","Use when authoring the **non-layout** parts of the MPS editor aspect — what happens when the user types, presses a key, triggers completion, pastes, or invokes a context action. Covers action maps (`CellActionMapDeclaration`), cell keymaps (`CellKeyMapDeclaration`), transformation menus (`TransformationMenu_Default` \u002F `_Named` \u002F `_Contribution`), substitute menus (`SubstituteMenu_Default` \u002F `SubstituteMenu` \u002F contributions), side transforms (LEFT\u002FRIGHT), legacy cell menus, paste wrappers and copy-paste handlers (in the actions language), completion styling, reference presentation, two-step deletion, and the editor selection API. Trigger terms: `actionMap`, `keyMap`, `delete_action_id`, `transformationMenu`, `substituteMenu`, `Ctrl+Space`, `Ctrl+Alt+B`, side transform, paste wrapper, completion styling, `PasteWrappers`, `CopyPasteHandlers`. For the **layout** side (cells, layouts, style sheets) use `mps-aspect-editor` instead.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[761,762],{"name":26,"slug":27,"type":15},{"name":687,"slug":688,"type":15},"2026-07-23T05:41:49.666535",{"slug":765,"name":765,"fn":766,"description":767,"org":768,"tags":769,"stars":704,"repoUrl":705,"updatedAt":772},"mps-aspect-generation-plan","modify MPS generation plans","Use when defining or modifying an MPS generation plan — explicit ordering of generators, checkpoints for cross-model reference resolution, forks for parallel branches, IncludePlan composition, conditional PlanContribution activation, ParameterEquals\u002FConceptListSelector fork selectors, and InitModelAttributes for targetFacet routing. Apply when working with @genplan models, the jetbrains.mps.lang.generator.plan language, attaching plans via DevKits or the Custom generation facet, or debugging cross-model mapping label resolution.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[770,771],{"name":17,"slug":18,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:44:59.507855",{"slug":774,"name":774,"fn":775,"description":776,"org":777,"tags":778,"stars":704,"repoUrl":705,"updatedAt":782},"mps-aspect-generator","define JetBrains MPS generator rules","Use when defining or modifying MPS generators — author a generator module, add or edit root\u002Freduction\u002Fweaving\u002Fpattern mapping rules, attach template macros ($COPY_SRC, $LOOP, $IF, $PROPERTY, $REF, $SWITCH, $MAP_SRC, $WEAVE, $INSERT, $LABEL, $TRACE, $VAR), wire mapping labels, build template switches, write pre\u002Fpost mapping scripts, navigate `genContext`, or debug \"rule didn't fire\", missing references, empty output, infinite reduction loops, and generated-Java compile failures.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[779,780,781],{"name":17,"slug":18,"type":15},{"name":733,"slug":734,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:06:58.042999",{"slug":784,"name":784,"fn":785,"description":786,"org":787,"tags":788,"stars":704,"repoUrl":705,"updatedAt":791},"mps-aspect-intentions","define and edit MPS intentions","Use when defining or editing MPS intentions (the Alt+Enter context-action aspect) — adding `IntentionDeclaration` roots, parameterized or surround-with variants, description\u002FisApplicable\u002Fexecute blocks, child-filter functions, factory-initialized AST splicing, or debugging why an intention is not offered. Lives in the language's `intentions` model and uses `jetbrains.mps.lang.intentions`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[789,790],{"name":17,"slug":18,"type":15},{"name":26,"slug":27,"type":15},"2026-07-23T05:41:48.692899",{"slug":793,"name":793,"fn":794,"description":795,"org":796,"tags":797,"stars":704,"repoUrl":705,"updatedAt":804},"mps-aspect-migrations","author and debug MPS migration scripts","Use when authoring or debugging MPS migration scripts that upgrade user models after a language definition changes — covers jetbrains.mps.lang.migration (MigrationScript class-based, PureMigrationScript declarative, MoveConcept\u002FMoveContainmentLink\u002FMoveReferenceLink\u002FMoveProperty, ordering via OrderDependency, data exchange via putData\u002FgetData, RefactoringLog, ConceptMigrationReference) and jetbrains.mps.lang.script Enhancement Scripts (MigrationScript with MigrationScriptPart_Instance, ExtractInterfaceMigration, FactoryMigrationScriptPart, CommentMigrationScriptPart) — when a model needs version-gated upgrade, concept rename or removal, link or property rename, instance-level transformation, or composition of migration steps.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[798,801],{"name":799,"slug":800,"type":15},"Debugging","debugging",{"name":802,"slug":803,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":806,"name":806,"fn":807,"description":808,"org":809,"tags":810,"stars":704,"repoUrl":705,"updatedAt":814},"mps-aspect-structure-concepts","define concepts in MPS structure aspect","Define concepts, interface concepts, enumerations, and constrained data types in an MPS language's `structure` aspect. Covers smart-reference detection, alias rules, cardinality, INamedConcept usage, bulk creation, and the full `mps_mcp_alter_structure` \u002F `mps_mcp_query_structure` reference. Use when authoring or modifying a language's structure model.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[811],{"name":812,"slug":813,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]