[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-dependency-conflict-resolver":3,"mdc--2vl66m-key":36,"related-org-jetbrains-dependency-conflict-resolver":523,"related-repo-jetbrains-dependency-conflict-resolver":654},{"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},"dependency-conflict-resolver","resolve Gradle and Spring dependency conflicts","Diagnose and resolve Gradle and Spring classpath conflicts, version drift, and binary incompatibilities in Kotlin applications. Use when `NoSuchMethodError`, `ClassNotFoundException`, linkage errors, duplicate logging bindings, Jackson or Hibernate mismatches, or BOM-versus-explicit-version conflicts appear, and the fix must respect the repository's real version authorities.",{"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},"Debugging","debugging",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-17T06:04:35.967185",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\u002Fdependency-conflict-resolver","---\nname: dependency-conflict-resolver\ndescription: Diagnose and resolve Gradle and Spring classpath conflicts, version drift, and binary incompatibilities in Kotlin applications. Use when `NoSuchMethodError`, `ClassNotFoundException`, linkage errors, duplicate logging bindings, Jackson or Hibernate mismatches, or BOM-versus-explicit-version conflicts appear, and the fix must respect the repository's real version authorities.\nmetadata:\n  short-description: \"Untangle Gradle classpath conflicts\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fdependency-conflict-resolver\n---\n\n# Dependency Conflict Resolver\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-05`).\n\n## Mission\n\nFind which artifact version actually wins, why it wins, and what the narrowest safe correction is.\nTreat dependency conflict resolution as a version-authority problem, not a guessing contest.\n\n## Read First\n\n- `.\u002Fgradlew dependencies` or module-scoped dependencies output.\n- `.\u002Fgradlew dependencyInsight --dependency \u003Cartifact>` for the failing library family.\n- Root and module build files, version catalogs, imported BOMs, and plugin versions.\n- The exact runtime or compile-time error:\n  - `NoSuchMethodError`\n  - `ClassNotFoundException`\n  - `NoClassDefFoundError`\n  - `AbstractMethodError`\n  - duplicate binding warnings\n\n## Diagnose In This Order\n\n1. Identify the failing class or method owner.\n2. Identify which artifact provides that class.\n3. Identify all candidate versions on the graph.\n4. Identify the winning version and why it won:\n   - direct dependency\n   - BOM or platform\n   - version catalog alias\n   - transitive dependency\n   - conflict resolution rule\n5. Identify the true version authority that should own the family.\n\n## Advanced Classpath Traps\n\n- A compile-time green build and a runtime linkage error usually means binary incompatibility between resolved artifacts, not a missing import.\n- Jackson, Netty, SLF4J, Logback, Kotlin stdlib, and Hibernate families should usually be version-aligned as families, not patched one artifact at a time.\n- Plugin classpath and application classpath are different worlds. A plugin upgrade may not fix a runtime library conflict and vice versa.\n- Test runtime can differ from main runtime. A conflict that appears only in tests may come from test fixtures, mock libraries, or test containers support.\n- `enforcedPlatform`, `strictly`, and exclusions can fix a conflict or silently lock the graph into brittle behavior. Use them deliberately.\n- Multiple logging bindings often create confusing startup behavior long before they fail hard.\n- Shading or relocation is rarely the first answer in an ordinary Spring Boot app. Reach for it only when classpath isolation is truly required.\n\n## Gradle Resolution Nuances\n\n- Variant-aware resolution can choose artifacts by attributes such as usage, JVM version, and capabilities. A \"present\" dependency may still resolve to the wrong variant.\n- BOM import order and multiple platforms can subtly change which family wins even when the declared versions look reasonable.\n- `api` versus `implementation` leakage in shared modules can make conflicts appear only in downstream consumers.\n- Duplicate classes from repackaged or relocated jars may not surface until runtime classloading or auto-configuration scans.\n- Annotation processors, KSP, and plugin classpaths may need separate alignment from the main application runtime.\n\n## Expert Heuristics\n\n- If the symptom is runtime-only, inspect the packaged artifact or runtime classpath, not only IDE dependency trees.\n- If a library family is managed by Spring Boot, prefer returning ownership to the BOM over adding more local pins.\n- If the same conflict recurs across modules, solve it at the platform or convention level instead of patching one module at a time.\n- If a dependency looks unused, verify reflective, auto-configured, or service-loader usage before removing it.\n\n## Preferred Resolution Strategy\n\n- Prefer removing an unnecessary explicit version when the BOM already manages a compatible one.\n- Prefer aligning the entire affected dependency family.\n- Prefer a direct, documented version override over hidden exclusions if an override is truly needed.\n- Use exclusions only when a dependency is genuinely wrong for the module, not merely inconvenient.\n- Explain why the chosen layer should own the version so the conflict does not return on the next upgrade.\n\n## Output Contract\n\nReturn these sections:\n\n- `Conflict summary`: what is colliding and where the symptom appears.\n- `Winning path`: how the resolved artifact version is selected.\n- `Version authority`: which file or platform should own the fix.\n- `Minimal fix`: the smallest safe dependency or platform change.\n- `Verification`: compile-time and runtime checks that confirm the graph is healthy.\n\n## Guardrails\n\n- Do not invent version numbers without tracing the existing compatibility model.\n- Do not spray exclusions until the graph goes green.\n- Do not use `force` as the default answer.\n- Do not fix only the visibly failing artifact when the whole library family is misaligned.\n\n## Quality Bar\n\nA good run of this skill explains the conflict path and resolves it at the right authority layer.\nA bad run produces a one-off version pin that compiles today and recreates the same conflict in the next branch.\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Untangle Gradle classpath conflicts","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fdependency-conflict-resolver",{"type":42,"children":43},"root",[44,52,75,82,87,93,174,180,237,243,295,301,343,349,372,378,406,412,417,475,481,512,518],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Dependency Conflict Resolver",{"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-05",{"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},"Find which artifact version actually wins, why it wins, and what the narrowest safe correction is.\nTreat dependency conflict resolution as a version-authority problem, not a guessing contest.",{"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,109,120,125],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101,107],{"type":45,"tag":59,"props":102,"children":104},{"className":103},[],[105],{"type":50,"value":106},".\u002Fgradlew dependencies",{"type":50,"value":108}," or module-scoped dependencies output.",{"type":45,"tag":98,"props":110,"children":111},{},[112,118],{"type":45,"tag":59,"props":113,"children":115},{"className":114},[],[116],{"type":50,"value":117},".\u002Fgradlew dependencyInsight --dependency \u003Cartifact>",{"type":50,"value":119}," for the failing library family.",{"type":45,"tag":98,"props":121,"children":122},{},[123],{"type":50,"value":124},"Root and module build files, version catalogs, imported BOMs, and plugin versions.",{"type":45,"tag":98,"props":126,"children":127},{},[128,130],{"type":50,"value":129},"The exact runtime or compile-time error:\n",{"type":45,"tag":94,"props":131,"children":132},{},[133,142,151,160,169],{"type":45,"tag":98,"props":134,"children":135},{},[136],{"type":45,"tag":59,"props":137,"children":139},{"className":138},[],[140],{"type":50,"value":141},"NoSuchMethodError",{"type":45,"tag":98,"props":143,"children":144},{},[145],{"type":45,"tag":59,"props":146,"children":148},{"className":147},[],[149],{"type":50,"value":150},"ClassNotFoundException",{"type":45,"tag":98,"props":152,"children":153},{},[154],{"type":45,"tag":59,"props":155,"children":157},{"className":156},[],[158],{"type":50,"value":159},"NoClassDefFoundError",{"type":45,"tag":98,"props":161,"children":162},{},[163],{"type":45,"tag":59,"props":164,"children":166},{"className":165},[],[167],{"type":50,"value":168},"AbstractMethodError",{"type":45,"tag":98,"props":170,"children":171},{},[172],{"type":50,"value":173},"duplicate binding warnings",{"type":45,"tag":76,"props":175,"children":177},{"id":176},"diagnose-in-this-order",[178],{"type":50,"value":179},"Diagnose In This Order",{"type":45,"tag":181,"props":182,"children":183},"ol",{},[184,189,194,199,232],{"type":45,"tag":98,"props":185,"children":186},{},[187],{"type":50,"value":188},"Identify the failing class or method owner.",{"type":45,"tag":98,"props":190,"children":191},{},[192],{"type":50,"value":193},"Identify which artifact provides that class.",{"type":45,"tag":98,"props":195,"children":196},{},[197],{"type":50,"value":198},"Identify all candidate versions on the graph.",{"type":45,"tag":98,"props":200,"children":201},{},[202,204],{"type":50,"value":203},"Identify the winning version and why it won:\n",{"type":45,"tag":94,"props":205,"children":206},{},[207,212,217,222,227],{"type":45,"tag":98,"props":208,"children":209},{},[210],{"type":50,"value":211},"direct dependency",{"type":45,"tag":98,"props":213,"children":214},{},[215],{"type":50,"value":216},"BOM or platform",{"type":45,"tag":98,"props":218,"children":219},{},[220],{"type":50,"value":221},"version catalog alias",{"type":45,"tag":98,"props":223,"children":224},{},[225],{"type":50,"value":226},"transitive dependency",{"type":45,"tag":98,"props":228,"children":229},{},[230],{"type":50,"value":231},"conflict resolution rule",{"type":45,"tag":98,"props":233,"children":234},{},[235],{"type":50,"value":236},"Identify the true version authority that should own the family.",{"type":45,"tag":76,"props":238,"children":240},{"id":239},"advanced-classpath-traps",[241],{"type":50,"value":242},"Advanced Classpath Traps",{"type":45,"tag":94,"props":244,"children":245},{},[246,251,256,261,266,285,290],{"type":45,"tag":98,"props":247,"children":248},{},[249],{"type":50,"value":250},"A compile-time green build and a runtime linkage error usually means binary incompatibility between resolved artifacts, not a missing import.",{"type":45,"tag":98,"props":252,"children":253},{},[254],{"type":50,"value":255},"Jackson, Netty, SLF4J, Logback, Kotlin stdlib, and Hibernate families should usually be version-aligned as families, not patched one artifact at a time.",{"type":45,"tag":98,"props":257,"children":258},{},[259],{"type":50,"value":260},"Plugin classpath and application classpath are different worlds. A plugin upgrade may not fix a runtime library conflict and vice versa.",{"type":45,"tag":98,"props":262,"children":263},{},[264],{"type":50,"value":265},"Test runtime can differ from main runtime. A conflict that appears only in tests may come from test fixtures, mock libraries, or test containers support.",{"type":45,"tag":98,"props":267,"children":268},{},[269,275,277,283],{"type":45,"tag":59,"props":270,"children":272},{"className":271},[],[273],{"type":50,"value":274},"enforcedPlatform",{"type":50,"value":276},", ",{"type":45,"tag":59,"props":278,"children":280},{"className":279},[],[281],{"type":50,"value":282},"strictly",{"type":50,"value":284},", and exclusions can fix a conflict or silently lock the graph into brittle behavior. Use them deliberately.",{"type":45,"tag":98,"props":286,"children":287},{},[288],{"type":50,"value":289},"Multiple logging bindings often create confusing startup behavior long before they fail hard.",{"type":45,"tag":98,"props":291,"children":292},{},[293],{"type":50,"value":294},"Shading or relocation is rarely the first answer in an ordinary Spring Boot app. Reach for it only when classpath isolation is truly required.",{"type":45,"tag":76,"props":296,"children":298},{"id":297},"gradle-resolution-nuances",[299],{"type":50,"value":300},"Gradle Resolution Nuances",{"type":45,"tag":94,"props":302,"children":303},{},[304,309,314,333,338],{"type":45,"tag":98,"props":305,"children":306},{},[307],{"type":50,"value":308},"Variant-aware resolution can choose artifacts by attributes such as usage, JVM version, and capabilities. A \"present\" dependency may still resolve to the wrong variant.",{"type":45,"tag":98,"props":310,"children":311},{},[312],{"type":50,"value":313},"BOM import order and multiple platforms can subtly change which family wins even when the declared versions look reasonable.",{"type":45,"tag":98,"props":315,"children":316},{},[317,323,325,331],{"type":45,"tag":59,"props":318,"children":320},{"className":319},[],[321],{"type":50,"value":322},"api",{"type":50,"value":324}," versus ",{"type":45,"tag":59,"props":326,"children":328},{"className":327},[],[329],{"type":50,"value":330},"implementation",{"type":50,"value":332}," leakage in shared modules can make conflicts appear only in downstream consumers.",{"type":45,"tag":98,"props":334,"children":335},{},[336],{"type":50,"value":337},"Duplicate classes from repackaged or relocated jars may not surface until runtime classloading or auto-configuration scans.",{"type":45,"tag":98,"props":339,"children":340},{},[341],{"type":50,"value":342},"Annotation processors, KSP, and plugin classpaths may need separate alignment from the main application runtime.",{"type":45,"tag":76,"props":344,"children":346},{"id":345},"expert-heuristics",[347],{"type":50,"value":348},"Expert Heuristics",{"type":45,"tag":94,"props":350,"children":351},{},[352,357,362,367],{"type":45,"tag":98,"props":353,"children":354},{},[355],{"type":50,"value":356},"If the symptom is runtime-only, inspect the packaged artifact or runtime classpath, not only IDE dependency trees.",{"type":45,"tag":98,"props":358,"children":359},{},[360],{"type":50,"value":361},"If a library family is managed by Spring Boot, prefer returning ownership to the BOM over adding more local pins.",{"type":45,"tag":98,"props":363,"children":364},{},[365],{"type":50,"value":366},"If the same conflict recurs across modules, solve it at the platform or convention level instead of patching one module at a time.",{"type":45,"tag":98,"props":368,"children":369},{},[370],{"type":50,"value":371},"If a dependency looks unused, verify reflective, auto-configured, or service-loader usage before removing it.",{"type":45,"tag":76,"props":373,"children":375},{"id":374},"preferred-resolution-strategy",[376],{"type":50,"value":377},"Preferred Resolution Strategy",{"type":45,"tag":94,"props":379,"children":380},{},[381,386,391,396,401],{"type":45,"tag":98,"props":382,"children":383},{},[384],{"type":50,"value":385},"Prefer removing an unnecessary explicit version when the BOM already manages a compatible one.",{"type":45,"tag":98,"props":387,"children":388},{},[389],{"type":50,"value":390},"Prefer aligning the entire affected dependency family.",{"type":45,"tag":98,"props":392,"children":393},{},[394],{"type":50,"value":395},"Prefer a direct, documented version override over hidden exclusions if an override is truly needed.",{"type":45,"tag":98,"props":397,"children":398},{},[399],{"type":50,"value":400},"Use exclusions only when a dependency is genuinely wrong for the module, not merely inconvenient.",{"type":45,"tag":98,"props":402,"children":403},{},[404],{"type":50,"value":405},"Explain why the chosen layer should own the version so the conflict does not return on the next upgrade.",{"type":45,"tag":76,"props":407,"children":409},{"id":408},"output-contract",[410],{"type":50,"value":411},"Output Contract",{"type":45,"tag":53,"props":413,"children":414},{},[415],{"type":50,"value":416},"Return these sections:",{"type":45,"tag":94,"props":418,"children":419},{},[420,431,442,453,464],{"type":45,"tag":98,"props":421,"children":422},{},[423,429],{"type":45,"tag":59,"props":424,"children":426},{"className":425},[],[427],{"type":50,"value":428},"Conflict summary",{"type":50,"value":430},": what is colliding and where the symptom appears.",{"type":45,"tag":98,"props":432,"children":433},{},[434,440],{"type":45,"tag":59,"props":435,"children":437},{"className":436},[],[438],{"type":50,"value":439},"Winning path",{"type":50,"value":441},": how the resolved artifact version is selected.",{"type":45,"tag":98,"props":443,"children":444},{},[445,451],{"type":45,"tag":59,"props":446,"children":448},{"className":447},[],[449],{"type":50,"value":450},"Version authority",{"type":50,"value":452},": which file or platform should own the fix.",{"type":45,"tag":98,"props":454,"children":455},{},[456,462],{"type":45,"tag":59,"props":457,"children":459},{"className":458},[],[460],{"type":50,"value":461},"Minimal fix",{"type":50,"value":463},": the smallest safe dependency or platform change.",{"type":45,"tag":98,"props":465,"children":466},{},[467,473],{"type":45,"tag":59,"props":468,"children":470},{"className":469},[],[471],{"type":50,"value":472},"Verification",{"type":50,"value":474},": compile-time and runtime checks that confirm the graph is healthy.",{"type":45,"tag":76,"props":476,"children":478},{"id":477},"guardrails",[479],{"type":50,"value":480},"Guardrails",{"type":45,"tag":94,"props":482,"children":483},{},[484,489,494,507],{"type":45,"tag":98,"props":485,"children":486},{},[487],{"type":50,"value":488},"Do not invent version numbers without tracing the existing compatibility model.",{"type":45,"tag":98,"props":490,"children":491},{},[492],{"type":50,"value":493},"Do not spray exclusions until the graph goes green.",{"type":45,"tag":98,"props":495,"children":496},{},[497,499,505],{"type":50,"value":498},"Do not use ",{"type":45,"tag":59,"props":500,"children":502},{"className":501},[],[503],{"type":50,"value":504},"force",{"type":50,"value":506}," as the default answer.",{"type":45,"tag":98,"props":508,"children":509},{},[510],{"type":50,"value":511},"Do not fix only the visibly failing artifact when the whole library family is misaligned.",{"type":45,"tag":76,"props":513,"children":515},{"id":514},"quality-bar",[516],{"type":50,"value":517},"Quality Bar",{"type":45,"tag":53,"props":519,"children":520},{},[521],{"type":50,"value":522},"A good run of this skill explains the conflict path and resolves it at the right authority layer.\nA bad run produces a one-off version pin that compiles today and recreates the same conflict in the next branch.",{"items":524,"total":653},[525,543,552,561,572,582,595,604,613,623,632,643],{"slug":526,"name":526,"fn":527,"description":528,"org":529,"tags":530,"stars":540,"repoUrl":541,"updatedAt":542},"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},[531,534,537],{"name":532,"slug":533,"type":15},"Architecture","architecture",{"name":535,"slug":536,"type":15},"Configuration","configuration",{"name":538,"slug":539,"type":15},"Engineering","engineering",1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":544,"name":544,"fn":545,"description":546,"org":547,"tags":548,"stars":540,"repoUrl":541,"updatedAt":551},"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},[549,550],{"name":532,"slug":533,"type":15},{"name":538,"slug":539,"type":15},"2026-07-17T06:04:48.066901",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":540,"repoUrl":541,"updatedAt":560},"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},[558,559],{"name":532,"slug":533,"type":15},{"name":538,"slug":539,"type":15},"2026-07-13T06:45:21.757084",{"slug":562,"name":562,"fn":563,"description":564,"org":565,"tags":566,"stars":540,"repoUrl":541,"updatedAt":571},"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},[567,568],{"name":532,"slug":533,"type":15},{"name":569,"slug":570,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":573,"name":573,"fn":574,"description":575,"org":576,"tags":577,"stars":540,"repoUrl":541,"updatedAt":581},"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},[578],{"name":579,"slug":580,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":583,"name":583,"fn":584,"description":585,"org":586,"tags":587,"stars":540,"repoUrl":541,"updatedAt":594},"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},[588,591],{"name":589,"slug":590,"type":15},"Design","design",{"name":592,"slug":593,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":596,"name":596,"fn":597,"description":598,"org":599,"tags":600,"stars":540,"repoUrl":541,"updatedAt":603},"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},[601,602],{"name":538,"slug":539,"type":15},{"name":592,"slug":593,"type":15},"2026-07-23T05:41:49.666535",{"slug":605,"name":605,"fn":606,"description":607,"org":608,"tags":609,"stars":540,"repoUrl":541,"updatedAt":612},"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},[610,611],{"name":532,"slug":533,"type":15},{"name":538,"slug":539,"type":15},"2026-07-13T06:44:59.507855",{"slug":614,"name":614,"fn":615,"description":616,"org":617,"tags":618,"stars":540,"repoUrl":541,"updatedAt":622},"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},[619,620,621],{"name":532,"slug":533,"type":15},{"name":569,"slug":570,"type":15},{"name":538,"slug":539,"type":15},"2026-07-17T06:06:58.042999",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":540,"repoUrl":541,"updatedAt":631},"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},[629,630],{"name":532,"slug":533,"type":15},{"name":538,"slug":539,"type":15},"2026-07-23T05:41:48.692899",{"slug":633,"name":633,"fn":634,"description":635,"org":636,"tags":637,"stars":540,"repoUrl":541,"updatedAt":642},"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},[638,639],{"name":23,"slug":24,"type":15},{"name":640,"slug":641,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":644,"name":644,"fn":645,"description":646,"org":647,"tags":648,"stars":540,"repoUrl":541,"updatedAt":652},"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},[649],{"name":650,"slug":651,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":655,"total":769},[656,675,690,704,719,738,755],{"slug":657,"name":657,"fn":658,"description":659,"org":660,"tags":661,"stars":25,"repoUrl":26,"updatedAt":674},"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},[662,665,668,671],{"name":663,"slug":664,"type":15},"Creative","creative",{"name":666,"slug":667,"type":15},"Generative Art","generative-art",{"name":669,"slug":670,"type":15},"Graphics","graphics",{"name":672,"slug":673,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":676,"name":676,"fn":677,"description":678,"org":679,"tags":680,"stars":25,"repoUrl":26,"updatedAt":689},"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},[681,684,685,686],{"name":682,"slug":683,"type":15},"Best Practices","best-practices",{"name":538,"slug":539,"type":15},{"name":672,"slug":673,"type":15},{"name":687,"slug":688,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":25,"repoUrl":26,"updatedAt":703},"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},[696,699,700],{"name":697,"slug":698,"type":15},"Branding","branding",{"name":589,"slug":590,"type":15},{"name":701,"slug":702,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":705,"name":705,"fn":706,"description":707,"org":708,"tags":709,"stars":25,"repoUrl":26,"updatedAt":718},"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},[710,711,712,715],{"name":663,"slug":664,"type":15},{"name":589,"slug":590,"type":15},{"name":713,"slug":714,"type":15},"Images","images",{"name":716,"slug":717,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":720,"name":720,"fn":721,"description":722,"org":723,"tags":724,"stars":25,"repoUrl":26,"updatedAt":737},"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},[725,728,731,734,735,736],{"name":726,"slug":727,"type":15},"CI\u002FCD","ci-cd",{"name":729,"slug":730,"type":15},"Containers","containers",{"name":732,"slug":733,"type":15},"Deployment","deployment",{"name":538,"slug":539,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":739,"name":739,"fn":740,"description":741,"org":742,"tags":743,"stars":25,"repoUrl":26,"updatedAt":754},"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},[744,747,750,753],{"name":745,"slug":746,"type":15},"Cloudflare","cloudflare",{"name":748,"slug":749,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":751,"slug":752,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":732,"slug":733,"type":15},"2026-07-17T06:04:42.853896",{"slug":756,"name":756,"fn":757,"description":758,"org":759,"tags":760,"stars":25,"repoUrl":26,"updatedAt":768},"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},[761,764,767],{"name":762,"slug":763,"type":15},"Automation","automation",{"name":765,"slug":766,"type":15},"Desktop","desktop",{"name":592,"slug":593,"type":15},"2026-07-13T06:40:38.798626",128]