[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-kotlin-idiomatic-refactorer-spring-aware":3,"mdc-l0ba6n-key":36,"related-repo-jetbrains-kotlin-idiomatic-refactorer-spring-aware":513,"related-org-jetbrains-kotlin-idiomatic-refactorer-spring-aware":633},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"kotlin-idiomatic-refactorer-spring-aware","refactor Kotlin code to idiomatic design","Refactor Kotlin code toward clearer, more idiomatic design without breaking Spring behavior, serialization, persistence, or public contracts. Use when Java-flavored Kotlin needs cleanup, domain modeling should become more expressive, or boilerplate should be reduced, but the refactoring must remain safe for proxies, Jackson, JPA, configuration binding, and existing tests.",{"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],{"name":13,"slug":14,"type":15},"Kotlin","kotlin","tag",{"name":17,"slug":18,"type":15},"Spring","spring",{"name":20,"slug":21,"type":15},"Engineering","engineering",{"name":23,"slug":24,"type":15},"Code Analysis","code-analysis",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-17T06:06:46.527807",null,17,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Fkotlin-idiomatic-refactorer-spring-aware","---\nname: kotlin-idiomatic-refactorer-spring-aware\ndescription: Refactor Kotlin code toward clearer, more idiomatic design without breaking Spring behavior, serialization, persistence, or public contracts. Use when Java-flavored Kotlin needs cleanup, domain modeling should become more expressive, or boilerplate should be reduced, but the refactoring must remain safe for proxies, Jackson, JPA, configuration binding, and existing tests.\nmetadata:\n  short-description: \"Refactor Kotlin without breaking Spring\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fkotlin-idiomatic-refactorer-spring-aware\n---\n\n# Kotlin Idiomatic Refactorer Spring Aware\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-20`).\n\n## Mission\n\nImprove the codebase's Kotlin quality without trading away framework correctness.\nPrefer refactorings that increase clarity and reduce accidental complexity while preserving behavior.\n\n## Read First\n\n- The current implementation and its tests.\n- Public signatures, annotations, and serialization or persistence boundaries.\n- Build plugins and framework constraints already discovered in project context.\n- Existing code style and module-boundary conventions.\n\n## Refactor In This Order\n\n1. Characterize current behavior with tests or existing callers.\n2. Identify whether the code is transport DTO, domain logic, entity, configuration, or framework glue.\n3. Apply the smallest idiomatic improvement that materially helps readability or safety.\n4. Re-check proxy, serialization, and persistence compatibility.\n5. Keep changes incremental unless the user explicitly wants a larger rewrite.\n\n## High-Value Kotlin Moves\n\n- Prefer constructor injection and immutable dependencies.\n- Replace imperative branching with `when` when it improves exhaustive reasoning.\n- Use `sealed class` or `sealed interface` for closed result or error domains.\n- Use `data class` for pure transport or value models, not for JPA entities.\n- Use value classes for domain primitives when the surrounding framework stack can support them safely.\n- Prefer explicit null-handling over scattered `!!`.\n- Use extension functions only when they improve discoverability and do not obscure ownership or layering.\n\n## Advanced Refactoring Traps\n\n- More concise is not always clearer. Scope functions can hide control flow and receiver identity quickly.\n- A beautiful Kotlin one-liner can become unreadable when side effects, logging, or transactions are involved.\n- Value classes are excellent domain tools but may require extra care for Jackson, JPA, validation, and map keys.\n- `Sequence` and lazy pipelines are not automatically faster, especially around JPA or repeated iteration.\n- Converting mutable services to expression-heavy style must not hide exception paths or operational logging.\n- Replacing explicit classes with generic helper abstractions often harms Spring traceability and domain clarity.\n- Refactoring null handling can silently change API semantics if `null`, absent, and default were distinct before.\n\n## Kotlin Language Nuances\n\n- Public inline functions, default arguments, and generated overloads can affect binary compatibility for library modules more than teams expect.\n- A read-only Kotlin collection type does not guarantee an immutable backing collection. Refactors that assume true immutability can still leak mutation.\n- `copy()` on data classes is convenient but can weaken domain invariants when state transitions should stay explicit.\n- Exhaustive `when` over sealed hierarchies improves safety, but only if the hierarchy is truly closed in the relevant module boundary.\n- Reified generics and extension-heavy DSLs can improve ergonomics while making stack traces and Java interop worse. Use them where the tradeoff is worth it.\n\n## Expert Heuristics\n\n- Prefer refactors that make invalid states harder to represent, not only code shorter to read.\n- Keep business transitions explicit when the domain has invariants, auditing, or transactional significance.\n- If a refactor improves local beauty but obscures logs, traces, or step-by-step debugging, it is probably not worth it.\n- In shared modules, treat source compatibility and binary compatibility as separate review questions.\n\n## Spring-Aware Safety Rules\n\n- Do not refactor proxy-reliant classes in ways that remove needed openness or change bean boundaries accidentally.\n- Do not convert entities into data classes or over-lean value objects without checking persistence support.\n- Do not change constructor shapes for DTOs or config classes without checking Jackson and configuration binding.\n- Do not move logic into extension functions that cross architecture layers implicitly.\n- Do not hide important framework interactions behind clever utility abstractions.\n\n## Output Contract\n\nReturn these sections:\n\n- `Refactoring intent`: what quality problem is being solved.\n- `Safe transformations`: the concrete Kotlin improvements that are appropriate here.\n- `Framework constraints`: the Spring, Jackson, JPA, or config rules that limit the refactor.\n- `Minimal patch plan`: incremental changes in a safe order.\n- `Verification`: which tests or runtime checks protect behavior.\n\n## Guardrails\n\n- Do not refactor for aesthetics alone when risk is non-trivial.\n- Do not introduce advanced Kotlin constructs just to prove idiomatic knowledge.\n- Do not compress code until debugability suffers.\n- Do not change public contracts without calling that out explicitly.\n\n## Quality Bar\n\nA good run of this skill leaves the code more Kotlin-native and still boringly reliable in Spring.\nA bad run produces elegant Kotlin that is harder to debug, harder to evolve, or incompatible with framework behavior.\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Refactor Kotlin without breaking Spring","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fkotlin-idiomatic-refactorer-spring-aware",{"type":42,"children":43},"root",[44,52,75,82,87,93,118,124,153,159,236,242,294,300,341,347,370,376,404,410,415,473,479,502,508],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Kotlin Idiomatic Refactorer Spring Aware",{"type":45,"tag":53,"props":54,"children":55},"p",{},[56,58,65,67,73],{"type":50,"value":57},"Source mapping: Tier 2 high-value skill derived from ",{"type":45,"tag":59,"props":60,"children":62},"code",{"className":61},[],[63],{"type":50,"value":64},"Kotlin_Spring_Developer_Pipeline.md",{"type":50,"value":66}," (",{"type":45,"tag":59,"props":68,"children":70},{"className":69},[],[71],{"type":50,"value":72},"SK-20",{"type":50,"value":74},").",{"type":45,"tag":76,"props":77,"children":79},"h2",{"id":78},"mission",[80],{"type":50,"value":81},"Mission",{"type":45,"tag":53,"props":83,"children":84},{},[85],{"type":50,"value":86},"Improve the codebase's Kotlin quality without trading away framework correctness.\nPrefer refactorings that increase clarity and reduce accidental complexity while preserving behavior.",{"type":45,"tag":76,"props":88,"children":90},{"id":89},"read-first",[91],{"type":50,"value":92},"Read First",{"type":45,"tag":94,"props":95,"children":96},"ul",{},[97,103,108,113],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101],{"type":50,"value":102},"The current implementation and its tests.",{"type":45,"tag":98,"props":104,"children":105},{},[106],{"type":50,"value":107},"Public signatures, annotations, and serialization or persistence boundaries.",{"type":45,"tag":98,"props":109,"children":110},{},[111],{"type":50,"value":112},"Build plugins and framework constraints already discovered in project context.",{"type":45,"tag":98,"props":114,"children":115},{},[116],{"type":50,"value":117},"Existing code style and module-boundary conventions.",{"type":45,"tag":76,"props":119,"children":121},{"id":120},"refactor-in-this-order",[122],{"type":50,"value":123},"Refactor In This Order",{"type":45,"tag":125,"props":126,"children":127},"ol",{},[128,133,138,143,148],{"type":45,"tag":98,"props":129,"children":130},{},[131],{"type":50,"value":132},"Characterize current behavior with tests or existing callers.",{"type":45,"tag":98,"props":134,"children":135},{},[136],{"type":50,"value":137},"Identify whether the code is transport DTO, domain logic, entity, configuration, or framework glue.",{"type":45,"tag":98,"props":139,"children":140},{},[141],{"type":50,"value":142},"Apply the smallest idiomatic improvement that materially helps readability or safety.",{"type":45,"tag":98,"props":144,"children":145},{},[146],{"type":50,"value":147},"Re-check proxy, serialization, and persistence compatibility.",{"type":45,"tag":98,"props":149,"children":150},{},[151],{"type":50,"value":152},"Keep changes incremental unless the user explicitly wants a larger rewrite.",{"type":45,"tag":76,"props":154,"children":156},{"id":155},"high-value-kotlin-moves",[157],{"type":50,"value":158},"High-Value Kotlin Moves",{"type":45,"tag":94,"props":160,"children":161},{},[162,167,180,201,213,218,231],{"type":45,"tag":98,"props":163,"children":164},{},[165],{"type":50,"value":166},"Prefer constructor injection and immutable dependencies.",{"type":45,"tag":98,"props":168,"children":169},{},[170,172,178],{"type":50,"value":171},"Replace imperative branching with ",{"type":45,"tag":59,"props":173,"children":175},{"className":174},[],[176],{"type":50,"value":177},"when",{"type":50,"value":179}," when it improves exhaustive reasoning.",{"type":45,"tag":98,"props":181,"children":182},{},[183,185,191,193,199],{"type":50,"value":184},"Use ",{"type":45,"tag":59,"props":186,"children":188},{"className":187},[],[189],{"type":50,"value":190},"sealed class",{"type":50,"value":192}," or ",{"type":45,"tag":59,"props":194,"children":196},{"className":195},[],[197],{"type":50,"value":198},"sealed interface",{"type":50,"value":200}," for closed result or error domains.",{"type":45,"tag":98,"props":202,"children":203},{},[204,205,211],{"type":50,"value":184},{"type":45,"tag":59,"props":206,"children":208},{"className":207},[],[209],{"type":50,"value":210},"data class",{"type":50,"value":212}," for pure transport or value models, not for JPA entities.",{"type":45,"tag":98,"props":214,"children":215},{},[216],{"type":50,"value":217},"Use value classes for domain primitives when the surrounding framework stack can support them safely.",{"type":45,"tag":98,"props":219,"children":220},{},[221,223,229],{"type":50,"value":222},"Prefer explicit null-handling over scattered ",{"type":45,"tag":59,"props":224,"children":226},{"className":225},[],[227],{"type":50,"value":228},"!!",{"type":50,"value":230},".",{"type":45,"tag":98,"props":232,"children":233},{},[234],{"type":50,"value":235},"Use extension functions only when they improve discoverability and do not obscure ownership or layering.",{"type":45,"tag":76,"props":237,"children":239},{"id":238},"advanced-refactoring-traps",[240],{"type":50,"value":241},"Advanced Refactoring Traps",{"type":45,"tag":94,"props":243,"children":244},{},[245,250,255,260,271,276,281],{"type":45,"tag":98,"props":246,"children":247},{},[248],{"type":50,"value":249},"More concise is not always clearer. Scope functions can hide control flow and receiver identity quickly.",{"type":45,"tag":98,"props":251,"children":252},{},[253],{"type":50,"value":254},"A beautiful Kotlin one-liner can become unreadable when side effects, logging, or transactions are involved.",{"type":45,"tag":98,"props":256,"children":257},{},[258],{"type":50,"value":259},"Value classes are excellent domain tools but may require extra care for Jackson, JPA, validation, and map keys.",{"type":45,"tag":98,"props":261,"children":262},{},[263,269],{"type":45,"tag":59,"props":264,"children":266},{"className":265},[],[267],{"type":50,"value":268},"Sequence",{"type":50,"value":270}," and lazy pipelines are not automatically faster, especially around JPA or repeated iteration.",{"type":45,"tag":98,"props":272,"children":273},{},[274],{"type":50,"value":275},"Converting mutable services to expression-heavy style must not hide exception paths or operational logging.",{"type":45,"tag":98,"props":277,"children":278},{},[279],{"type":50,"value":280},"Replacing explicit classes with generic helper abstractions often harms Spring traceability and domain clarity.",{"type":45,"tag":98,"props":282,"children":283},{},[284,286,292],{"type":50,"value":285},"Refactoring null handling can silently change API semantics if ",{"type":45,"tag":59,"props":287,"children":289},{"className":288},[],[290],{"type":50,"value":291},"null",{"type":50,"value":293},", absent, and default were distinct before.",{"type":45,"tag":76,"props":295,"children":297},{"id":296},"kotlin-language-nuances",[298],{"type":50,"value":299},"Kotlin Language Nuances",{"type":45,"tag":94,"props":301,"children":302},{},[303,308,313,324,336],{"type":45,"tag":98,"props":304,"children":305},{},[306],{"type":50,"value":307},"Public inline functions, default arguments, and generated overloads can affect binary compatibility for library modules more than teams expect.",{"type":45,"tag":98,"props":309,"children":310},{},[311],{"type":50,"value":312},"A read-only Kotlin collection type does not guarantee an immutable backing collection. Refactors that assume true immutability can still leak mutation.",{"type":45,"tag":98,"props":314,"children":315},{},[316,322],{"type":45,"tag":59,"props":317,"children":319},{"className":318},[],[320],{"type":50,"value":321},"copy()",{"type":50,"value":323}," on data classes is convenient but can weaken domain invariants when state transitions should stay explicit.",{"type":45,"tag":98,"props":325,"children":326},{},[327,329,334],{"type":50,"value":328},"Exhaustive ",{"type":45,"tag":59,"props":330,"children":332},{"className":331},[],[333],{"type":50,"value":177},{"type":50,"value":335}," over sealed hierarchies improves safety, but only if the hierarchy is truly closed in the relevant module boundary.",{"type":45,"tag":98,"props":337,"children":338},{},[339],{"type":50,"value":340},"Reified generics and extension-heavy DSLs can improve ergonomics while making stack traces and Java interop worse. Use them where the tradeoff is worth it.",{"type":45,"tag":76,"props":342,"children":344},{"id":343},"expert-heuristics",[345],{"type":50,"value":346},"Expert Heuristics",{"type":45,"tag":94,"props":348,"children":349},{},[350,355,360,365],{"type":45,"tag":98,"props":351,"children":352},{},[353],{"type":50,"value":354},"Prefer refactors that make invalid states harder to represent, not only code shorter to read.",{"type":45,"tag":98,"props":356,"children":357},{},[358],{"type":50,"value":359},"Keep business transitions explicit when the domain has invariants, auditing, or transactional significance.",{"type":45,"tag":98,"props":361,"children":362},{},[363],{"type":50,"value":364},"If a refactor improves local beauty but obscures logs, traces, or step-by-step debugging, it is probably not worth it.",{"type":45,"tag":98,"props":366,"children":367},{},[368],{"type":50,"value":369},"In shared modules, treat source compatibility and binary compatibility as separate review questions.",{"type":45,"tag":76,"props":371,"children":373},{"id":372},"spring-aware-safety-rules",[374],{"type":50,"value":375},"Spring-Aware Safety Rules",{"type":45,"tag":94,"props":377,"children":378},{},[379,384,389,394,399],{"type":45,"tag":98,"props":380,"children":381},{},[382],{"type":50,"value":383},"Do not refactor proxy-reliant classes in ways that remove needed openness or change bean boundaries accidentally.",{"type":45,"tag":98,"props":385,"children":386},{},[387],{"type":50,"value":388},"Do not convert entities into data classes or over-lean value objects without checking persistence support.",{"type":45,"tag":98,"props":390,"children":391},{},[392],{"type":50,"value":393},"Do not change constructor shapes for DTOs or config classes without checking Jackson and configuration binding.",{"type":45,"tag":98,"props":395,"children":396},{},[397],{"type":50,"value":398},"Do not move logic into extension functions that cross architecture layers implicitly.",{"type":45,"tag":98,"props":400,"children":401},{},[402],{"type":50,"value":403},"Do not hide important framework interactions behind clever utility abstractions.",{"type":45,"tag":76,"props":405,"children":407},{"id":406},"output-contract",[408],{"type":50,"value":409},"Output Contract",{"type":45,"tag":53,"props":411,"children":412},{},[413],{"type":50,"value":414},"Return these sections:",{"type":45,"tag":94,"props":416,"children":417},{},[418,429,440,451,462],{"type":45,"tag":98,"props":419,"children":420},{},[421,427],{"type":45,"tag":59,"props":422,"children":424},{"className":423},[],[425],{"type":50,"value":426},"Refactoring intent",{"type":50,"value":428},": what quality problem is being solved.",{"type":45,"tag":98,"props":430,"children":431},{},[432,438],{"type":45,"tag":59,"props":433,"children":435},{"className":434},[],[436],{"type":50,"value":437},"Safe transformations",{"type":50,"value":439},": the concrete Kotlin improvements that are appropriate here.",{"type":45,"tag":98,"props":441,"children":442},{},[443,449],{"type":45,"tag":59,"props":444,"children":446},{"className":445},[],[447],{"type":50,"value":448},"Framework constraints",{"type":50,"value":450},": the Spring, Jackson, JPA, or config rules that limit the refactor.",{"type":45,"tag":98,"props":452,"children":453},{},[454,460],{"type":45,"tag":59,"props":455,"children":457},{"className":456},[],[458],{"type":50,"value":459},"Minimal patch plan",{"type":50,"value":461},": incremental changes in a safe order.",{"type":45,"tag":98,"props":463,"children":464},{},[465,471],{"type":45,"tag":59,"props":466,"children":468},{"className":467},[],[469],{"type":50,"value":470},"Verification",{"type":50,"value":472},": which tests or runtime checks protect behavior.",{"type":45,"tag":76,"props":474,"children":476},{"id":475},"guardrails",[477],{"type":50,"value":478},"Guardrails",{"type":45,"tag":94,"props":480,"children":481},{},[482,487,492,497],{"type":45,"tag":98,"props":483,"children":484},{},[485],{"type":50,"value":486},"Do not refactor for aesthetics alone when risk is non-trivial.",{"type":45,"tag":98,"props":488,"children":489},{},[490],{"type":50,"value":491},"Do not introduce advanced Kotlin constructs just to prove idiomatic knowledge.",{"type":45,"tag":98,"props":493,"children":494},{},[495],{"type":50,"value":496},"Do not compress code until debugability suffers.",{"type":45,"tag":98,"props":498,"children":499},{},[500],{"type":50,"value":501},"Do not change public contracts without calling that out explicitly.",{"type":45,"tag":76,"props":503,"children":505},{"id":504},"quality-bar",[506],{"type":50,"value":507},"Quality Bar",{"type":45,"tag":53,"props":509,"children":510},{},[511],{"type":50,"value":512},"A good run of this skill leaves the code more Kotlin-native and still boringly reliable in Spring.\nA bad run produces elegant Kotlin that is harder to debug, harder to evolve, or incompatible with framework behavior.",{"items":514,"total":632},[515,534,549,565,580,599,616],{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":25,"repoUrl":26,"updatedAt":533},"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},[521,524,527,530],{"name":522,"slug":523,"type":15},"Creative","creative",{"name":525,"slug":526,"type":15},"Generative Art","generative-art",{"name":528,"slug":529,"type":15},"Graphics","graphics",{"name":531,"slug":532,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":535,"name":535,"fn":536,"description":537,"org":538,"tags":539,"stars":25,"repoUrl":26,"updatedAt":548},"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},[540,543,544,545],{"name":541,"slug":542,"type":15},"Best Practices","best-practices",{"name":20,"slug":21,"type":15},{"name":531,"slug":532,"type":15},{"name":546,"slug":547,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":550,"name":550,"fn":551,"description":552,"org":553,"tags":554,"stars":25,"repoUrl":26,"updatedAt":564},"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},[555,558,561],{"name":556,"slug":557,"type":15},"Branding","branding",{"name":559,"slug":560,"type":15},"Design","design",{"name":562,"slug":563,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":566,"name":566,"fn":567,"description":568,"org":569,"tags":570,"stars":25,"repoUrl":26,"updatedAt":579},"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},[571,572,573,576],{"name":522,"slug":523,"type":15},{"name":559,"slug":560,"type":15},{"name":574,"slug":575,"type":15},"Images","images",{"name":577,"slug":578,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":25,"repoUrl":26,"updatedAt":598},"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},[586,589,592,595,596,597],{"name":587,"slug":588,"type":15},"CI\u002FCD","ci-cd",{"name":590,"slug":591,"type":15},"Containers","containers",{"name":593,"slug":594,"type":15},"Deployment","deployment",{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},"2026-07-13T06:41:47.83899",{"slug":600,"name":600,"fn":601,"description":602,"org":603,"tags":604,"stars":25,"repoUrl":26,"updatedAt":615},"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},[605,608,611,614],{"name":606,"slug":607,"type":15},"Cloudflare","cloudflare",{"name":609,"slug":610,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":612,"slug":613,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":593,"slug":594,"type":15},"2026-07-17T06:04:42.853896",{"slug":617,"name":617,"fn":618,"description":619,"org":620,"tags":621,"stars":25,"repoUrl":26,"updatedAt":631},"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},[622,625,628],{"name":623,"slug":624,"type":15},"Automation","automation",{"name":626,"slug":627,"type":15},"Desktop","desktop",{"name":629,"slug":630,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":634,"total":757},[635,651,660,669,678,688,697,706,715,725,734,747],{"slug":636,"name":636,"fn":637,"description":638,"org":639,"tags":640,"stars":648,"repoUrl":649,"updatedAt":650},"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},[641,644,647],{"name":642,"slug":643,"type":15},"Architecture","architecture",{"name":645,"slug":646,"type":15},"Configuration","configuration",{"name":20,"slug":21,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":652,"name":652,"fn":653,"description":654,"org":655,"tags":656,"stars":648,"repoUrl":649,"updatedAt":659},"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},[657,658],{"name":642,"slug":643,"type":15},{"name":20,"slug":21,"type":15},"2026-07-17T06:04:48.066901",{"slug":661,"name":661,"fn":662,"description":663,"org":664,"tags":665,"stars":648,"repoUrl":649,"updatedAt":668},"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},[666,667],{"name":642,"slug":643,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:45:21.757084",{"slug":670,"name":670,"fn":671,"description":672,"org":673,"tags":674,"stars":648,"repoUrl":649,"updatedAt":677},"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},[675,676],{"name":642,"slug":643,"type":15},{"name":23,"slug":24,"type":15},"2026-07-23T05:41:33.639365",{"slug":679,"name":679,"fn":680,"description":681,"org":682,"tags":683,"stars":648,"repoUrl":649,"updatedAt":687},"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},[684],{"name":685,"slug":686,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":689,"name":689,"fn":690,"description":691,"org":692,"tags":693,"stars":648,"repoUrl":649,"updatedAt":696},"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},[694,695],{"name":559,"slug":560,"type":15},{"name":629,"slug":630,"type":15},"2026-07-23T05:41:56.638151",{"slug":698,"name":698,"fn":699,"description":700,"org":701,"tags":702,"stars":648,"repoUrl":649,"updatedAt":705},"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},[703,704],{"name":20,"slug":21,"type":15},{"name":629,"slug":630,"type":15},"2026-07-23T05:41:49.666535",{"slug":707,"name":707,"fn":708,"description":709,"org":710,"tags":711,"stars":648,"repoUrl":649,"updatedAt":714},"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},[712,713],{"name":642,"slug":643,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:44:59.507855",{"slug":716,"name":716,"fn":717,"description":718,"org":719,"tags":720,"stars":648,"repoUrl":649,"updatedAt":724},"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},[721,722,723],{"name":642,"slug":643,"type":15},{"name":23,"slug":24,"type":15},{"name":20,"slug":21,"type":15},"2026-07-17T06:06:58.042999",{"slug":726,"name":726,"fn":727,"description":728,"org":729,"tags":730,"stars":648,"repoUrl":649,"updatedAt":733},"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},[731,732],{"name":642,"slug":643,"type":15},{"name":20,"slug":21,"type":15},"2026-07-23T05:41:48.692899",{"slug":735,"name":735,"fn":736,"description":737,"org":738,"tags":739,"stars":648,"repoUrl":649,"updatedAt":746},"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},[740,743],{"name":741,"slug":742,"type":15},"Debugging","debugging",{"name":744,"slug":745,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":648,"repoUrl":649,"updatedAt":756},"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},[753],{"name":754,"slug":755,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]