[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-upgrade-breaking-change-navigator":3,"mdc-dqh7oq-key":36,"related-org-jetbrains-upgrade-breaking-change-navigator":490,"related-repo-jetbrains-upgrade-breaking-change-navigator":621},{"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},"upgrade-breaking-change-navigator","execute major dependency and framework upgrades","Plan and execute risky Spring Boot, Spring Framework, Kotlin, Gradle, JDK, and major dependency upgrades with explicit compatibility checkpoints and rollback thinking. Use when preparing or diagnosing a major version jump, navigating `javax` to `jakarta`, K2 adoption, plugin compatibility, auto-configuration drift, behavior changes in Hibernate or Security, or project-specific upgrade sequencing.",{"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},"Gradle","gradle",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Migration","migration",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:42:13.736008",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\u002Fupgrade-breaking-change-navigator","---\nname: upgrade-breaking-change-navigator\ndescription: Plan and execute risky Spring Boot, Spring Framework, Kotlin, Gradle, JDK, and major dependency upgrades with explicit compatibility checkpoints and rollback thinking. Use when preparing or diagnosing a major version jump, navigating `javax` to `jakarta`, K2 adoption, plugin compatibility, auto-configuration drift, behavior changes in Hibernate or Security, or project-specific upgrade sequencing.\nmetadata:\n  short-description: \"Plan risky platform upgrades safely\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fupgrade-breaking-change-navigator\n---\n\n# Upgrade Breaking Change Navigator\n\nSource mapping: Tier 3 specialized skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-22`).\n\n## Mission\n\nTurn a risky platform upgrade into a controlled sequence of small, verifiable moves.\nOptimize for incremental confidence, not for a single giant leap that hides the source of breakage.\n\n## Read First\n\n- Current Gradle wrapper, Kotlin plugin, Spring Boot plugin, JDK, and key dependency versions.\n- Version catalogs, convention plugins, and BOM ownership.\n- Build failures, test failures, runtime startup failures, and deprecation reports.\n- The actual libraries and features in use: Security, Data JPA, WebFlux, AOT\u002Fnative, messaging, serialization, cloud config.\n- Official upgrade notes when available.\n\n## Upgrade Strategy\n\n1. Identify the target version and the last known good current version.\n2. Identify mandatory intermediate steps. Do not skip major lines casually.\n3. Separate upgrade layers:\n   - JDK\n   - Gradle wrapper\n   - Kotlin plugin and compiler\n   - Spring Boot and Spring Framework\n   - ecosystem libraries\n4. Upgrade one authority at a time whenever possible.\n5. After each step, verify:\n   - dependency resolution\n   - compile\n   - tests\n   - startup smoke\n6. Record breakages by layer so the root cause stays attributable.\n\n## Advanced Upgrade Hotspots\n\n- `javax.*` to `jakarta.*` is both source migration and dependency compatibility migration.\n- Spring Security DSL and filter-chain defaults change across major lines. \"Compiles\" does not mean \"same auth behavior.\"\n- Hibernate upgrades can change SQL generation, lazy-loading behavior, sequence handling, and schema expectations.\n- Kotlin compiler upgrades can affect KAPT, KSP, compiler plugins, nullability inference, and generated bytecode shape.\n- Boot upgrades can change auto-configuration defaults, logging behavior, observability integration, and actuator exposure.\n- Native image or AOT support raises a different class of breakages around reflection, proxies, and configuration hints.\n- Testcontainers, MockK, bytecode instrumentation, and coverage tooling often lag core platform upgrades.\n- JSpecify or other nullability enhancements in upstream libraries may force new Kotlin compile warnings or source changes.\n\n## Runtime And Tooling Nuances\n\n- JDK upgrades can tighten module encapsulation, change TLS defaults, alter DNS or timezone behavior, and surface illegal reflective access only in production-like environments.\n- Path-matching, error rendering, and Problem Details defaults can shift behavior at the web boundary even when controller code remains unchanged.\n- Observability migrations can change metric names, trace propagation, or log correlation behavior, breaking dashboards before the app \"breaks.\"\n- Security upgrades frequently change defaults toward stricter behavior. A newly failing request may indicate a safer default, not a broken framework.\n- Gradle upgrades can invalidate custom build logic, remote cache assumptions, and plugin internals long before the application code notices.\n- Native-image or AOT-capable builds often need separate verification gates because JVM startup passing does not imply native correctness.\n\n## Expert Heuristics\n\n- Upgrade the path that gives the highest diagnostic signal first, not merely the path that feels most foundational.\n- Upgrade the toolchain that constrains others first only when compatibility docs support that order; otherwise preserve the currently supported matrix as long as possible.\n- Let the platform BOM regain control of library families before trying to patch every individual dependency.\n- Treat deprecation warnings as migration guidance, not cosmetic noise, when they are in code paths touched by the upgrade.\n- If dashboards, alerts, or client contracts are version-sensitive, treat them as part of the upgrade scope, not post-upgrade cleanup.\n- If a library is not upgrade-ready, decide whether to pin temporarily, replace it, or postpone the platform target. Do not pretend all paths are equal.\n- Maintain a migration log per step: version change, observed failures, compensating fixes, and remaining known risks. This prevents rediscovery loops.\n- Prefer canary or staged deployment for behavior-changing upgrades even when compile and test phases are green.\n- Preserve a rollback path for deployable upgrades. A technically correct upgrade without operational reversibility is incomplete.\n\n## Output Contract\n\nReturn these sections:\n\n- `Current state`: the versions and high-risk features in use.\n- `Upgrade path`: the ordered sequence of upgrades.\n- `Breaking-change hotspots`: which parts of the codebase are most likely to fail and why.\n- `Verification gates`: what must pass after each step.\n- `Temporary mitigations`: acceptable short-lived pins or compatibility shims.\n- `Rollback note`: how to retreat safely if a step fails in a deployed environment.\n\n## Guardrails\n\n- Do not skip major versions without a strong, project-specific reason.\n- Do not mix many unrelated upgrade axes into one untraceable patch if avoidable.\n- Do not assume compile success equals runtime safety.\n- Do not remove compatibility shims without proving callers no longer need them.\n\n## Quality Bar\n\nA good run of this skill gives the team an upgrade path with clear checkpoints and known failure hotspots.\nA bad run is a giant version-bump patch followed by generic advice to \"fix whatever breaks.\"\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Plan risky platform upgrades safely","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fupgrade-breaking-change-navigator",{"type":42,"children":43},"root",[44,52,75,82,87,93,123,129,214,220,277,283,316,322,370,376,381,450,456,479,485],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Upgrade Breaking Change Navigator",{"type":45,"tag":53,"props":54,"children":55},"p",{},[56,58,65,67,73],{"type":50,"value":57},"Source mapping: Tier 3 specialized 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-22",{"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},"Turn a risky platform upgrade into a controlled sequence of small, verifiable moves.\nOptimize for incremental confidence, not for a single giant leap that hides the source of breakage.",{"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,118],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101],{"type":50,"value":102},"Current Gradle wrapper, Kotlin plugin, Spring Boot plugin, JDK, and key dependency versions.",{"type":45,"tag":98,"props":104,"children":105},{},[106],{"type":50,"value":107},"Version catalogs, convention plugins, and BOM ownership.",{"type":45,"tag":98,"props":109,"children":110},{},[111],{"type":50,"value":112},"Build failures, test failures, runtime startup failures, and deprecation reports.",{"type":45,"tag":98,"props":114,"children":115},{},[116],{"type":50,"value":117},"The actual libraries and features in use: Security, Data JPA, WebFlux, AOT\u002Fnative, messaging, serialization, cloud config.",{"type":45,"tag":98,"props":119,"children":120},{},[121],{"type":50,"value":122},"Official upgrade notes when available.",{"type":45,"tag":76,"props":124,"children":126},{"id":125},"upgrade-strategy",[127],{"type":50,"value":128},"Upgrade Strategy",{"type":45,"tag":130,"props":131,"children":132},"ol",{},[133,138,143,176,181,209],{"type":45,"tag":98,"props":134,"children":135},{},[136],{"type":50,"value":137},"Identify the target version and the last known good current version.",{"type":45,"tag":98,"props":139,"children":140},{},[141],{"type":50,"value":142},"Identify mandatory intermediate steps. Do not skip major lines casually.",{"type":45,"tag":98,"props":144,"children":145},{},[146,148],{"type":50,"value":147},"Separate upgrade layers:\n",{"type":45,"tag":94,"props":149,"children":150},{},[151,156,161,166,171],{"type":45,"tag":98,"props":152,"children":153},{},[154],{"type":50,"value":155},"JDK",{"type":45,"tag":98,"props":157,"children":158},{},[159],{"type":50,"value":160},"Gradle wrapper",{"type":45,"tag":98,"props":162,"children":163},{},[164],{"type":50,"value":165},"Kotlin plugin and compiler",{"type":45,"tag":98,"props":167,"children":168},{},[169],{"type":50,"value":170},"Spring Boot and Spring Framework",{"type":45,"tag":98,"props":172,"children":173},{},[174],{"type":50,"value":175},"ecosystem libraries",{"type":45,"tag":98,"props":177,"children":178},{},[179],{"type":50,"value":180},"Upgrade one authority at a time whenever possible.",{"type":45,"tag":98,"props":182,"children":183},{},[184,186],{"type":50,"value":185},"After each step, verify:\n",{"type":45,"tag":94,"props":187,"children":188},{},[189,194,199,204],{"type":45,"tag":98,"props":190,"children":191},{},[192],{"type":50,"value":193},"dependency resolution",{"type":45,"tag":98,"props":195,"children":196},{},[197],{"type":50,"value":198},"compile",{"type":45,"tag":98,"props":200,"children":201},{},[202],{"type":50,"value":203},"tests",{"type":45,"tag":98,"props":205,"children":206},{},[207],{"type":50,"value":208},"startup smoke",{"type":45,"tag":98,"props":210,"children":211},{},[212],{"type":50,"value":213},"Record breakages by layer so the root cause stays attributable.",{"type":45,"tag":76,"props":215,"children":217},{"id":216},"advanced-upgrade-hotspots",[218],{"type":50,"value":219},"Advanced Upgrade Hotspots",{"type":45,"tag":94,"props":221,"children":222},{},[223,242,247,252,257,262,267,272],{"type":45,"tag":98,"props":224,"children":225},{},[226,232,234,240],{"type":45,"tag":59,"props":227,"children":229},{"className":228},[],[230],{"type":50,"value":231},"javax.*",{"type":50,"value":233}," to ",{"type":45,"tag":59,"props":235,"children":237},{"className":236},[],[238],{"type":50,"value":239},"jakarta.*",{"type":50,"value":241}," is both source migration and dependency compatibility migration.",{"type":45,"tag":98,"props":243,"children":244},{},[245],{"type":50,"value":246},"Spring Security DSL and filter-chain defaults change across major lines. \"Compiles\" does not mean \"same auth behavior.\"",{"type":45,"tag":98,"props":248,"children":249},{},[250],{"type":50,"value":251},"Hibernate upgrades can change SQL generation, lazy-loading behavior, sequence handling, and schema expectations.",{"type":45,"tag":98,"props":253,"children":254},{},[255],{"type":50,"value":256},"Kotlin compiler upgrades can affect KAPT, KSP, compiler plugins, nullability inference, and generated bytecode shape.",{"type":45,"tag":98,"props":258,"children":259},{},[260],{"type":50,"value":261},"Boot upgrades can change auto-configuration defaults, logging behavior, observability integration, and actuator exposure.",{"type":45,"tag":98,"props":263,"children":264},{},[265],{"type":50,"value":266},"Native image or AOT support raises a different class of breakages around reflection, proxies, and configuration hints.",{"type":45,"tag":98,"props":268,"children":269},{},[270],{"type":50,"value":271},"Testcontainers, MockK, bytecode instrumentation, and coverage tooling often lag core platform upgrades.",{"type":45,"tag":98,"props":273,"children":274},{},[275],{"type":50,"value":276},"JSpecify or other nullability enhancements in upstream libraries may force new Kotlin compile warnings or source changes.",{"type":45,"tag":76,"props":278,"children":280},{"id":279},"runtime-and-tooling-nuances",[281],{"type":50,"value":282},"Runtime And Tooling Nuances",{"type":45,"tag":94,"props":284,"children":285},{},[286,291,296,301,306,311],{"type":45,"tag":98,"props":287,"children":288},{},[289],{"type":50,"value":290},"JDK upgrades can tighten module encapsulation, change TLS defaults, alter DNS or timezone behavior, and surface illegal reflective access only in production-like environments.",{"type":45,"tag":98,"props":292,"children":293},{},[294],{"type":50,"value":295},"Path-matching, error rendering, and Problem Details defaults can shift behavior at the web boundary even when controller code remains unchanged.",{"type":45,"tag":98,"props":297,"children":298},{},[299],{"type":50,"value":300},"Observability migrations can change metric names, trace propagation, or log correlation behavior, breaking dashboards before the app \"breaks.\"",{"type":45,"tag":98,"props":302,"children":303},{},[304],{"type":50,"value":305},"Security upgrades frequently change defaults toward stricter behavior. A newly failing request may indicate a safer default, not a broken framework.",{"type":45,"tag":98,"props":307,"children":308},{},[309],{"type":50,"value":310},"Gradle upgrades can invalidate custom build logic, remote cache assumptions, and plugin internals long before the application code notices.",{"type":45,"tag":98,"props":312,"children":313},{},[314],{"type":50,"value":315},"Native-image or AOT-capable builds often need separate verification gates because JVM startup passing does not imply native correctness.",{"type":45,"tag":76,"props":317,"children":319},{"id":318},"expert-heuristics",[320],{"type":50,"value":321},"Expert Heuristics",{"type":45,"tag":94,"props":323,"children":324},{},[325,330,335,340,345,350,355,360,365],{"type":45,"tag":98,"props":326,"children":327},{},[328],{"type":50,"value":329},"Upgrade the path that gives the highest diagnostic signal first, not merely the path that feels most foundational.",{"type":45,"tag":98,"props":331,"children":332},{},[333],{"type":50,"value":334},"Upgrade the toolchain that constrains others first only when compatibility docs support that order; otherwise preserve the currently supported matrix as long as possible.",{"type":45,"tag":98,"props":336,"children":337},{},[338],{"type":50,"value":339},"Let the platform BOM regain control of library families before trying to patch every individual dependency.",{"type":45,"tag":98,"props":341,"children":342},{},[343],{"type":50,"value":344},"Treat deprecation warnings as migration guidance, not cosmetic noise, when they are in code paths touched by the upgrade.",{"type":45,"tag":98,"props":346,"children":347},{},[348],{"type":50,"value":349},"If dashboards, alerts, or client contracts are version-sensitive, treat them as part of the upgrade scope, not post-upgrade cleanup.",{"type":45,"tag":98,"props":351,"children":352},{},[353],{"type":50,"value":354},"If a library is not upgrade-ready, decide whether to pin temporarily, replace it, or postpone the platform target. Do not pretend all paths are equal.",{"type":45,"tag":98,"props":356,"children":357},{},[358],{"type":50,"value":359},"Maintain a migration log per step: version change, observed failures, compensating fixes, and remaining known risks. This prevents rediscovery loops.",{"type":45,"tag":98,"props":361,"children":362},{},[363],{"type":50,"value":364},"Prefer canary or staged deployment for behavior-changing upgrades even when compile and test phases are green.",{"type":45,"tag":98,"props":366,"children":367},{},[368],{"type":50,"value":369},"Preserve a rollback path for deployable upgrades. A technically correct upgrade without operational reversibility is incomplete.",{"type":45,"tag":76,"props":371,"children":373},{"id":372},"output-contract",[374],{"type":50,"value":375},"Output Contract",{"type":45,"tag":53,"props":377,"children":378},{},[379],{"type":50,"value":380},"Return these sections:",{"type":45,"tag":94,"props":382,"children":383},{},[384,395,406,417,428,439],{"type":45,"tag":98,"props":385,"children":386},{},[387,393],{"type":45,"tag":59,"props":388,"children":390},{"className":389},[],[391],{"type":50,"value":392},"Current state",{"type":50,"value":394},": the versions and high-risk features in use.",{"type":45,"tag":98,"props":396,"children":397},{},[398,404],{"type":45,"tag":59,"props":399,"children":401},{"className":400},[],[402],{"type":50,"value":403},"Upgrade path",{"type":50,"value":405},": the ordered sequence of upgrades.",{"type":45,"tag":98,"props":407,"children":408},{},[409,415],{"type":45,"tag":59,"props":410,"children":412},{"className":411},[],[413],{"type":50,"value":414},"Breaking-change hotspots",{"type":50,"value":416},": which parts of the codebase are most likely to fail and why.",{"type":45,"tag":98,"props":418,"children":419},{},[420,426],{"type":45,"tag":59,"props":421,"children":423},{"className":422},[],[424],{"type":50,"value":425},"Verification gates",{"type":50,"value":427},": what must pass after each step.",{"type":45,"tag":98,"props":429,"children":430},{},[431,437],{"type":45,"tag":59,"props":432,"children":434},{"className":433},[],[435],{"type":50,"value":436},"Temporary mitigations",{"type":50,"value":438},": acceptable short-lived pins or compatibility shims.",{"type":45,"tag":98,"props":440,"children":441},{},[442,448],{"type":45,"tag":59,"props":443,"children":445},{"className":444},[],[446],{"type":50,"value":447},"Rollback note",{"type":50,"value":449},": how to retreat safely if a step fails in a deployed environment.",{"type":45,"tag":76,"props":451,"children":453},{"id":452},"guardrails",[454],{"type":50,"value":455},"Guardrails",{"type":45,"tag":94,"props":457,"children":458},{},[459,464,469,474],{"type":45,"tag":98,"props":460,"children":461},{},[462],{"type":50,"value":463},"Do not skip major versions without a strong, project-specific reason.",{"type":45,"tag":98,"props":465,"children":466},{},[467],{"type":50,"value":468},"Do not mix many unrelated upgrade axes into one untraceable patch if avoidable.",{"type":45,"tag":98,"props":470,"children":471},{},[472],{"type":50,"value":473},"Do not assume compile success equals runtime safety.",{"type":45,"tag":98,"props":475,"children":476},{},[477],{"type":50,"value":478},"Do not remove compatibility shims without proving callers no longer need them.",{"type":45,"tag":76,"props":480,"children":482},{"id":481},"quality-bar",[483],{"type":50,"value":484},"Quality Bar",{"type":45,"tag":53,"props":486,"children":487},{},[488],{"type":50,"value":489},"A good run of this skill gives the team an upgrade path with clear checkpoints and known failure hotspots.\nA bad run is a giant version-bump patch followed by generic advice to \"fix whatever breaks.\"",{"items":491,"total":620},[492,510,519,528,539,549,562,571,580,590,599,610],{"slug":493,"name":493,"fn":494,"description":495,"org":496,"tags":497,"stars":507,"repoUrl":508,"updatedAt":509},"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},[498,501,504],{"name":499,"slug":500,"type":15},"Architecture","architecture",{"name":502,"slug":503,"type":15},"Configuration","configuration",{"name":505,"slug":506,"type":15},"Engineering","engineering",1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":511,"name":511,"fn":512,"description":513,"org":514,"tags":515,"stars":507,"repoUrl":508,"updatedAt":518},"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},[516,517],{"name":499,"slug":500,"type":15},{"name":505,"slug":506,"type":15},"2026-07-17T06:04:48.066901",{"slug":520,"name":520,"fn":521,"description":522,"org":523,"tags":524,"stars":507,"repoUrl":508,"updatedAt":527},"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},[525,526],{"name":499,"slug":500,"type":15},{"name":505,"slug":506,"type":15},"2026-07-13T06:45:21.757084",{"slug":529,"name":529,"fn":530,"description":531,"org":532,"tags":533,"stars":507,"repoUrl":508,"updatedAt":538},"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},[534,535],{"name":499,"slug":500,"type":15},{"name":536,"slug":537,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":540,"name":540,"fn":541,"description":542,"org":543,"tags":544,"stars":507,"repoUrl":508,"updatedAt":548},"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},[545],{"name":546,"slug":547,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":550,"name":550,"fn":551,"description":552,"org":553,"tags":554,"stars":507,"repoUrl":508,"updatedAt":561},"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},[555,558],{"name":556,"slug":557,"type":15},"Design","design",{"name":559,"slug":560,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":563,"name":563,"fn":564,"description":565,"org":566,"tags":567,"stars":507,"repoUrl":508,"updatedAt":570},"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},[568,569],{"name":505,"slug":506,"type":15},{"name":559,"slug":560,"type":15},"2026-07-23T05:41:49.666535",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":507,"repoUrl":508,"updatedAt":579},"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},[577,578],{"name":499,"slug":500,"type":15},{"name":505,"slug":506,"type":15},"2026-07-13T06:44:59.507855",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":507,"repoUrl":508,"updatedAt":589},"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},[586,587,588],{"name":499,"slug":500,"type":15},{"name":536,"slug":537,"type":15},{"name":505,"slug":506,"type":15},"2026-07-17T06:06:58.042999",{"slug":591,"name":591,"fn":592,"description":593,"org":594,"tags":595,"stars":507,"repoUrl":508,"updatedAt":598},"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},[596,597],{"name":499,"slug":500,"type":15},{"name":505,"slug":506,"type":15},"2026-07-23T05:41:48.692899",{"slug":600,"name":600,"fn":601,"description":602,"org":603,"tags":604,"stars":507,"repoUrl":508,"updatedAt":609},"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},[605,608],{"name":606,"slug":607,"type":15},"Debugging","debugging",{"name":23,"slug":24,"type":15},"2026-07-13T06:45:20.372122",{"slug":611,"name":611,"fn":612,"description":613,"org":614,"tags":615,"stars":507,"repoUrl":508,"updatedAt":619},"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},[616],{"name":617,"slug":618,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":622,"total":736},[623,642,657,671,686,705,722],{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":25,"repoUrl":26,"updatedAt":641},"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},[629,632,635,638],{"name":630,"slug":631,"type":15},"Creative","creative",{"name":633,"slug":634,"type":15},"Generative Art","generative-art",{"name":636,"slug":637,"type":15},"Graphics","graphics",{"name":639,"slug":640,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":643,"name":643,"fn":644,"description":645,"org":646,"tags":647,"stars":25,"repoUrl":26,"updatedAt":656},"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},[648,651,652,653],{"name":649,"slug":650,"type":15},"Best Practices","best-practices",{"name":505,"slug":506,"type":15},{"name":639,"slug":640,"type":15},{"name":654,"slug":655,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":25,"repoUrl":26,"updatedAt":670},"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},[663,666,667],{"name":664,"slug":665,"type":15},"Branding","branding",{"name":556,"slug":557,"type":15},{"name":668,"slug":669,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":672,"name":672,"fn":673,"description":674,"org":675,"tags":676,"stars":25,"repoUrl":26,"updatedAt":685},"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},[677,678,679,682],{"name":630,"slug":631,"type":15},{"name":556,"slug":557,"type":15},{"name":680,"slug":681,"type":15},"Images","images",{"name":683,"slug":684,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":687,"name":687,"fn":688,"description":689,"org":690,"tags":691,"stars":25,"repoUrl":26,"updatedAt":704},"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},[692,695,698,701,702,703],{"name":693,"slug":694,"type":15},"CI\u002FCD","ci-cd",{"name":696,"slug":697,"type":15},"Containers","containers",{"name":699,"slug":700,"type":15},"Deployment","deployment",{"name":505,"slug":506,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":706,"name":706,"fn":707,"description":708,"org":709,"tags":710,"stars":25,"repoUrl":26,"updatedAt":721},"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},[711,714,717,720],{"name":712,"slug":713,"type":15},"Cloudflare","cloudflare",{"name":715,"slug":716,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":718,"slug":719,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":699,"slug":700,"type":15},"2026-07-17T06:04:42.853896",{"slug":723,"name":723,"fn":724,"description":725,"org":726,"tags":727,"stars":25,"repoUrl":26,"updatedAt":735},"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},[728,731,734],{"name":729,"slug":730,"type":15},"Automation","automation",{"name":732,"slug":733,"type":15},"Desktop","desktop",{"name":559,"slug":560,"type":15},"2026-07-13T06:40:38.798626",128]