[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-performance-concurrency-advisor":3,"mdc-3io8m8-key":39,"related-org-jetbrains-performance-concurrency-advisor":456,"related-repo-jetbrains-performance-concurrency-advisor":587},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":34,"sourceUrl":37,"mdContent":38},"performance-concurrency-advisor","optimize performance for Kotlin Spring services","Analyze and improve performance, throughput, latency, and concurrency behavior in Kotlin plus Spring services using real evidence from metrics, traces, SQL, thread or heap signals, and code paths. Use when endpoints are slow, pools saturate, coroutines or reactive flows block unexpectedly, N+1 or contention appears, or caching and parallelism decisions need precise, non-generic guidance.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"jetbrains","JetBrains","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fjetbrains.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":18,"type":15},"Performance","performance",{"name":20,"slug":21,"type":15},"Kotlin","kotlin",{"name":23,"slug":24,"type":15},"Spring","spring",{"name":26,"slug":27,"type":15},"Engineering","engineering",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:42:11.439995",null,17,[],{"repoUrl":29,"stars":28,"forks":32,"topics":35,"description":36},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Fperformance-concurrency-advisor","---\nname: performance-concurrency-advisor\ndescription: Analyze and improve performance, throughput, latency, and concurrency behavior in Kotlin plus Spring services using real evidence from metrics, traces, SQL, thread or heap signals, and code paths. Use when endpoints are slow, pools saturate, coroutines or reactive flows block unexpectedly, N+1 or contention appears, or caching and parallelism decisions need precise, non-generic guidance.\nmetadata:\n  short-description: \"Diagnose bottlenecks with real signals\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fperformance-concurrency-advisor\n---\n\n# Performance Concurrency Advisor\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-18`).\n\n## Mission\n\nFind the bottleneck that actually limits the system, then recommend the smallest high-leverage change.\nTreat performance work as evidence-driven systems analysis, not as a bag of folklore.\n\n## Read Evidence First\n\n- Latency metrics, percentile breakdowns, throughput, and error rate.\n- Traces for slow flows.\n- SQL count or explain plans when persistence is involved.\n- Hikari, thread pool, event loop, or queue metrics when available.\n- Thread dumps, heap or GC signals, and recent code changes when the issue is severe.\n\n## Diagnose By Layer\n\nCheck these layers explicitly:\n\n- database query count and query latency\n- connection pool contention\n- downstream HTTP or messaging latency\n- thread pool starvation or scheduler misuse\n- event-loop blocking in reactive flows\n- serialization or large payload overhead\n- lock contention or transactional scope\n- cache misses or invalidation churn\n- CPU-bound work and allocation pressure\n\n## Advanced Performance Heuristics\n\n- N+1 is both a latency bug and a load amplifier. Fixing it often helps pool pressure and downstream CPU together.\n- Bigger pools are not a universal fix. If the database is slow, increasing concurrency often worsens tail latency.\n- Hikari tuning should follow database capacity and workload pattern, not only CPU count.\n- Blocking calls inside WebFlux or coroutine event loops are catastrophic even when average latency looks acceptable.\n- `Dispatchers.IO` is not a free performance button. It moves blocking but can also hide architectural mismatch and increase context switching.\n- Parallelizing downstream calls can reduce mean latency while worsening saturation and timeouts under load.\n- Caches need invalidation, warm-up, and cardinality discipline. A bad cache can improve benchmarks and hurt production correctness.\n- Large object graphs, verbose JSON, and repeated mapping can dominate latency once the database is already optimized.\n- Lock contention and long transactions often look like random latency spikes until you correlate them with pool saturation and retries.\n- GC tuning is downstream of allocation patterns. Do not jump to JVM flags before understanding object churn.\n\n## Measurement Nuances\n\n- Average latency hides tail pain. Prefer percentiles and saturation correlation when user pain is bursty.\n- Coordinated omission can make a load test look healthier than production. Treat benchmark tooling assumptions as part of the evidence.\n- Container CPU limits, memory limits, and JDK container-awareness can dominate runtime behavior even when local profiling looks clean.\n- Warm-up state, JIT compilation, cache fill, and connection pool priming matter. Separate cold-start behavior from steady-state behavior.\n- If queueing exists anywhere in the path, small utilization increases can create nonlinear latency growth. Think in queueing terms, not only in raw CPU percentages.\n\n## Expert Heuristics\n\n- Prefer eliminating unnecessary work before parallelizing existing work.\n- If one optimization helps throughput but worsens tail latency or operator clarity, call that tradeoff out explicitly.\n- When reactive or coroutine code is slower than blocking code, first verify hidden blocking boundaries and context switches before blaming the paradigm.\n- If the service is already SLO-bound by a dependency, optimize isolation and graceful degradation before micro-optimizing local code.\n\n## Concurrency Rules\n\n- Distinguish I\u002FO-bound work from CPU-bound work before recommending async or parallel execution.\n- Keep transaction scopes short when locks or connection usage are involved.\n- Treat shared mutable in-memory state as a design smell in horizontally scaled services.\n- For coroutine or reactive flows, verify context propagation for transactions, security, and MDC if debugging or tracing is part of the issue.\n- Use backpressure, bulkheads, or bounded queues before unbounded parallelism.\n\n## Output Contract\n\nReturn these sections:\n\n- `Observed bottleneck`: the most likely limiting resource or contention point.\n- `Evidence`: metrics, traces, code path, or SQL evidence supporting that conclusion.\n- `Recommended change`: the smallest high-impact optimization.\n- `Tradeoffs`: what gets better and what new risk appears.\n- `Verification`: the benchmark, metric, or load-test signal that should improve.\n\n## Guardrails\n\n- Do not optimize without measurement.\n- Do not recommend caching, async, or bigger pools as reflexes.\n- Do not confuse throughput optimization with latency optimization; sometimes they move in opposite directions.\n- Do not trust local benchmarks alone for highly concurrent or I\u002FO-heavy paths.\n\n## Quality Bar\n\nA good run of this skill identifies the true constraint and gives a measurable improvement plan.\nA bad run suggests generic tuning knobs with no evidence, no tradeoffs, and no way to confirm success.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":20,"source":43},"Diagnose bottlenecks with real signals","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fperformance-concurrency-advisor",{"type":45,"children":46},"root",[47,55,78,85,90,96,126,132,137,185,191,250,256,284,290,313,319,347,353,358,416,422,445,451],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Performance Concurrency Advisor",{"type":48,"tag":56,"props":57,"children":58},"p",{},[59,61,68,70,76],{"type":53,"value":60},"Source mapping: Tier 2 high-value skill derived from ",{"type":48,"tag":62,"props":63,"children":65},"code",{"className":64},[],[66],{"type":53,"value":67},"Kotlin_Spring_Developer_Pipeline.md",{"type":53,"value":69}," (",{"type":48,"tag":62,"props":71,"children":73},{"className":72},[],[74],{"type":53,"value":75},"SK-18",{"type":53,"value":77},").",{"type":48,"tag":79,"props":80,"children":82},"h2",{"id":81},"mission",[83],{"type":53,"value":84},"Mission",{"type":48,"tag":56,"props":86,"children":87},{},[88],{"type":53,"value":89},"Find the bottleneck that actually limits the system, then recommend the smallest high-leverage change.\nTreat performance work as evidence-driven systems analysis, not as a bag of folklore.",{"type":48,"tag":79,"props":91,"children":93},{"id":92},"read-evidence-first",[94],{"type":53,"value":95},"Read Evidence First",{"type":48,"tag":97,"props":98,"children":99},"ul",{},[100,106,111,116,121],{"type":48,"tag":101,"props":102,"children":103},"li",{},[104],{"type":53,"value":105},"Latency metrics, percentile breakdowns, throughput, and error rate.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"Traces for slow flows.",{"type":48,"tag":101,"props":112,"children":113},{},[114],{"type":53,"value":115},"SQL count or explain plans when persistence is involved.",{"type":48,"tag":101,"props":117,"children":118},{},[119],{"type":53,"value":120},"Hikari, thread pool, event loop, or queue metrics when available.",{"type":48,"tag":101,"props":122,"children":123},{},[124],{"type":53,"value":125},"Thread dumps, heap or GC signals, and recent code changes when the issue is severe.",{"type":48,"tag":79,"props":127,"children":129},{"id":128},"diagnose-by-layer",[130],{"type":53,"value":131},"Diagnose By Layer",{"type":48,"tag":56,"props":133,"children":134},{},[135],{"type":53,"value":136},"Check these layers explicitly:",{"type":48,"tag":97,"props":138,"children":139},{},[140,145,150,155,160,165,170,175,180],{"type":48,"tag":101,"props":141,"children":142},{},[143],{"type":53,"value":144},"database query count and query latency",{"type":48,"tag":101,"props":146,"children":147},{},[148],{"type":53,"value":149},"connection pool contention",{"type":48,"tag":101,"props":151,"children":152},{},[153],{"type":53,"value":154},"downstream HTTP or messaging latency",{"type":48,"tag":101,"props":156,"children":157},{},[158],{"type":53,"value":159},"thread pool starvation or scheduler misuse",{"type":48,"tag":101,"props":161,"children":162},{},[163],{"type":53,"value":164},"event-loop blocking in reactive flows",{"type":48,"tag":101,"props":166,"children":167},{},[168],{"type":53,"value":169},"serialization or large payload overhead",{"type":48,"tag":101,"props":171,"children":172},{},[173],{"type":53,"value":174},"lock contention or transactional scope",{"type":48,"tag":101,"props":176,"children":177},{},[178],{"type":53,"value":179},"cache misses or invalidation churn",{"type":48,"tag":101,"props":181,"children":182},{},[183],{"type":53,"value":184},"CPU-bound work and allocation pressure",{"type":48,"tag":79,"props":186,"children":188},{"id":187},"advanced-performance-heuristics",[189],{"type":53,"value":190},"Advanced Performance Heuristics",{"type":48,"tag":97,"props":192,"children":193},{},[194,199,204,209,214,225,230,235,240,245],{"type":48,"tag":101,"props":195,"children":196},{},[197],{"type":53,"value":198},"N+1 is both a latency bug and a load amplifier. Fixing it often helps pool pressure and downstream CPU together.",{"type":48,"tag":101,"props":200,"children":201},{},[202],{"type":53,"value":203},"Bigger pools are not a universal fix. If the database is slow, increasing concurrency often worsens tail latency.",{"type":48,"tag":101,"props":205,"children":206},{},[207],{"type":53,"value":208},"Hikari tuning should follow database capacity and workload pattern, not only CPU count.",{"type":48,"tag":101,"props":210,"children":211},{},[212],{"type":53,"value":213},"Blocking calls inside WebFlux or coroutine event loops are catastrophic even when average latency looks acceptable.",{"type":48,"tag":101,"props":215,"children":216},{},[217,223],{"type":48,"tag":62,"props":218,"children":220},{"className":219},[],[221],{"type":53,"value":222},"Dispatchers.IO",{"type":53,"value":224}," is not a free performance button. It moves blocking but can also hide architectural mismatch and increase context switching.",{"type":48,"tag":101,"props":226,"children":227},{},[228],{"type":53,"value":229},"Parallelizing downstream calls can reduce mean latency while worsening saturation and timeouts under load.",{"type":48,"tag":101,"props":231,"children":232},{},[233],{"type":53,"value":234},"Caches need invalidation, warm-up, and cardinality discipline. A bad cache can improve benchmarks and hurt production correctness.",{"type":48,"tag":101,"props":236,"children":237},{},[238],{"type":53,"value":239},"Large object graphs, verbose JSON, and repeated mapping can dominate latency once the database is already optimized.",{"type":48,"tag":101,"props":241,"children":242},{},[243],{"type":53,"value":244},"Lock contention and long transactions often look like random latency spikes until you correlate them with pool saturation and retries.",{"type":48,"tag":101,"props":246,"children":247},{},[248],{"type":53,"value":249},"GC tuning is downstream of allocation patterns. Do not jump to JVM flags before understanding object churn.",{"type":48,"tag":79,"props":251,"children":253},{"id":252},"measurement-nuances",[254],{"type":53,"value":255},"Measurement Nuances",{"type":48,"tag":97,"props":257,"children":258},{},[259,264,269,274,279],{"type":48,"tag":101,"props":260,"children":261},{},[262],{"type":53,"value":263},"Average latency hides tail pain. Prefer percentiles and saturation correlation when user pain is bursty.",{"type":48,"tag":101,"props":265,"children":266},{},[267],{"type":53,"value":268},"Coordinated omission can make a load test look healthier than production. Treat benchmark tooling assumptions as part of the evidence.",{"type":48,"tag":101,"props":270,"children":271},{},[272],{"type":53,"value":273},"Container CPU limits, memory limits, and JDK container-awareness can dominate runtime behavior even when local profiling looks clean.",{"type":48,"tag":101,"props":275,"children":276},{},[277],{"type":53,"value":278},"Warm-up state, JIT compilation, cache fill, and connection pool priming matter. Separate cold-start behavior from steady-state behavior.",{"type":48,"tag":101,"props":280,"children":281},{},[282],{"type":53,"value":283},"If queueing exists anywhere in the path, small utilization increases can create nonlinear latency growth. Think in queueing terms, not only in raw CPU percentages.",{"type":48,"tag":79,"props":285,"children":287},{"id":286},"expert-heuristics",[288],{"type":53,"value":289},"Expert Heuristics",{"type":48,"tag":97,"props":291,"children":292},{},[293,298,303,308],{"type":48,"tag":101,"props":294,"children":295},{},[296],{"type":53,"value":297},"Prefer eliminating unnecessary work before parallelizing existing work.",{"type":48,"tag":101,"props":299,"children":300},{},[301],{"type":53,"value":302},"If one optimization helps throughput but worsens tail latency or operator clarity, call that tradeoff out explicitly.",{"type":48,"tag":101,"props":304,"children":305},{},[306],{"type":53,"value":307},"When reactive or coroutine code is slower than blocking code, first verify hidden blocking boundaries and context switches before blaming the paradigm.",{"type":48,"tag":101,"props":309,"children":310},{},[311],{"type":53,"value":312},"If the service is already SLO-bound by a dependency, optimize isolation and graceful degradation before micro-optimizing local code.",{"type":48,"tag":79,"props":314,"children":316},{"id":315},"concurrency-rules",[317],{"type":53,"value":318},"Concurrency Rules",{"type":48,"tag":97,"props":320,"children":321},{},[322,327,332,337,342],{"type":48,"tag":101,"props":323,"children":324},{},[325],{"type":53,"value":326},"Distinguish I\u002FO-bound work from CPU-bound work before recommending async or parallel execution.",{"type":48,"tag":101,"props":328,"children":329},{},[330],{"type":53,"value":331},"Keep transaction scopes short when locks or connection usage are involved.",{"type":48,"tag":101,"props":333,"children":334},{},[335],{"type":53,"value":336},"Treat shared mutable in-memory state as a design smell in horizontally scaled services.",{"type":48,"tag":101,"props":338,"children":339},{},[340],{"type":53,"value":341},"For coroutine or reactive flows, verify context propagation for transactions, security, and MDC if debugging or tracing is part of the issue.",{"type":48,"tag":101,"props":343,"children":344},{},[345],{"type":53,"value":346},"Use backpressure, bulkheads, or bounded queues before unbounded parallelism.",{"type":48,"tag":79,"props":348,"children":350},{"id":349},"output-contract",[351],{"type":53,"value":352},"Output Contract",{"type":48,"tag":56,"props":354,"children":355},{},[356],{"type":53,"value":357},"Return these sections:",{"type":48,"tag":97,"props":359,"children":360},{},[361,372,383,394,405],{"type":48,"tag":101,"props":362,"children":363},{},[364,370],{"type":48,"tag":62,"props":365,"children":367},{"className":366},[],[368],{"type":53,"value":369},"Observed bottleneck",{"type":53,"value":371},": the most likely limiting resource or contention point.",{"type":48,"tag":101,"props":373,"children":374},{},[375,381],{"type":48,"tag":62,"props":376,"children":378},{"className":377},[],[379],{"type":53,"value":380},"Evidence",{"type":53,"value":382},": metrics, traces, code path, or SQL evidence supporting that conclusion.",{"type":48,"tag":101,"props":384,"children":385},{},[386,392],{"type":48,"tag":62,"props":387,"children":389},{"className":388},[],[390],{"type":53,"value":391},"Recommended change",{"type":53,"value":393},": the smallest high-impact optimization.",{"type":48,"tag":101,"props":395,"children":396},{},[397,403],{"type":48,"tag":62,"props":398,"children":400},{"className":399},[],[401],{"type":53,"value":402},"Tradeoffs",{"type":53,"value":404},": what gets better and what new risk appears.",{"type":48,"tag":101,"props":406,"children":407},{},[408,414],{"type":48,"tag":62,"props":409,"children":411},{"className":410},[],[412],{"type":53,"value":413},"Verification",{"type":53,"value":415},": the benchmark, metric, or load-test signal that should improve.",{"type":48,"tag":79,"props":417,"children":419},{"id":418},"guardrails",[420],{"type":53,"value":421},"Guardrails",{"type":48,"tag":97,"props":423,"children":424},{},[425,430,435,440],{"type":48,"tag":101,"props":426,"children":427},{},[428],{"type":53,"value":429},"Do not optimize without measurement.",{"type":48,"tag":101,"props":431,"children":432},{},[433],{"type":53,"value":434},"Do not recommend caching, async, or bigger pools as reflexes.",{"type":48,"tag":101,"props":436,"children":437},{},[438],{"type":53,"value":439},"Do not confuse throughput optimization with latency optimization; sometimes they move in opposite directions.",{"type":48,"tag":101,"props":441,"children":442},{},[443],{"type":53,"value":444},"Do not trust local benchmarks alone for highly concurrent or I\u002FO-heavy paths.",{"type":48,"tag":79,"props":446,"children":448},{"id":447},"quality-bar",[449],{"type":53,"value":450},"Quality Bar",{"type":48,"tag":56,"props":452,"children":453},{},[454],{"type":53,"value":455},"A good run of this skill identifies the true constraint and gives a measurable improvement plan.\nA bad run suggests generic tuning knobs with no evidence, no tradeoffs, and no way to confirm success.",{"items":457,"total":586},[458,474,483,492,503,513,526,535,544,554,563,576],{"slug":459,"name":459,"fn":460,"description":461,"org":462,"tags":463,"stars":471,"repoUrl":472,"updatedAt":473},"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},[464,467,470],{"name":465,"slug":466,"type":15},"Architecture","architecture",{"name":468,"slug":469,"type":15},"Configuration","configuration",{"name":26,"slug":27,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":475,"name":475,"fn":476,"description":477,"org":478,"tags":479,"stars":471,"repoUrl":472,"updatedAt":482},"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},[480,481],{"name":465,"slug":466,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:04:48.066901",{"slug":484,"name":484,"fn":485,"description":486,"org":487,"tags":488,"stars":471,"repoUrl":472,"updatedAt":491},"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},[489,490],{"name":465,"slug":466,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:45:21.757084",{"slug":493,"name":493,"fn":494,"description":495,"org":496,"tags":497,"stars":471,"repoUrl":472,"updatedAt":502},"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},[498,499],{"name":465,"slug":466,"type":15},{"name":500,"slug":501,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":504,"name":504,"fn":505,"description":506,"org":507,"tags":508,"stars":471,"repoUrl":472,"updatedAt":512},"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},[509],{"name":510,"slug":511,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":514,"name":514,"fn":515,"description":516,"org":517,"tags":518,"stars":471,"repoUrl":472,"updatedAt":525},"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},[519,522],{"name":520,"slug":521,"type":15},"Design","design",{"name":523,"slug":524,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":527,"name":527,"fn":528,"description":529,"org":530,"tags":531,"stars":471,"repoUrl":472,"updatedAt":534},"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},[532,533],{"name":26,"slug":27,"type":15},{"name":523,"slug":524,"type":15},"2026-07-23T05:41:49.666535",{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":471,"repoUrl":472,"updatedAt":543},"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},[541,542],{"name":465,"slug":466,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:44:59.507855",{"slug":545,"name":545,"fn":546,"description":547,"org":548,"tags":549,"stars":471,"repoUrl":472,"updatedAt":553},"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},[550,551,552],{"name":465,"slug":466,"type":15},{"name":500,"slug":501,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:06:58.042999",{"slug":555,"name":555,"fn":556,"description":557,"org":558,"tags":559,"stars":471,"repoUrl":472,"updatedAt":562},"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},[560,561],{"name":465,"slug":466,"type":15},{"name":26,"slug":27,"type":15},"2026-07-23T05:41:48.692899",{"slug":564,"name":564,"fn":565,"description":566,"org":567,"tags":568,"stars":471,"repoUrl":472,"updatedAt":575},"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},[569,572],{"name":570,"slug":571,"type":15},"Debugging","debugging",{"name":573,"slug":574,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":577,"name":577,"fn":578,"description":579,"org":580,"tags":581,"stars":471,"repoUrl":472,"updatedAt":585},"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},[582],{"name":583,"slug":584,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":588,"total":702},[589,608,623,637,652,671,688],{"slug":590,"name":590,"fn":591,"description":592,"org":593,"tags":594,"stars":28,"repoUrl":29,"updatedAt":607},"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},[595,598,601,604],{"name":596,"slug":597,"type":15},"Creative","creative",{"name":599,"slug":600,"type":15},"Generative Art","generative-art",{"name":602,"slug":603,"type":15},"Graphics","graphics",{"name":605,"slug":606,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":28,"repoUrl":29,"updatedAt":622},"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},[614,617,618,619],{"name":615,"slug":616,"type":15},"Best Practices","best-practices",{"name":26,"slug":27,"type":15},{"name":605,"slug":606,"type":15},{"name":620,"slug":621,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":28,"repoUrl":29,"updatedAt":636},"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},[629,632,633],{"name":630,"slug":631,"type":15},"Branding","branding",{"name":520,"slug":521,"type":15},{"name":634,"slug":635,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":638,"name":638,"fn":639,"description":640,"org":641,"tags":642,"stars":28,"repoUrl":29,"updatedAt":651},"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},[643,644,645,648],{"name":596,"slug":597,"type":15},{"name":520,"slug":521,"type":15},{"name":646,"slug":647,"type":15},"Images","images",{"name":649,"slug":650,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":28,"repoUrl":29,"updatedAt":670},"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},[658,661,664,667,668,669],{"name":659,"slug":660,"type":15},"CI\u002FCD","ci-cd",{"name":662,"slug":663,"type":15},"Containers","containers",{"name":665,"slug":666,"type":15},"Deployment","deployment",{"name":26,"slug":27,"type":15},{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:41:47.83899",{"slug":672,"name":672,"fn":673,"description":674,"org":675,"tags":676,"stars":28,"repoUrl":29,"updatedAt":687},"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},[677,680,683,686],{"name":678,"slug":679,"type":15},"Cloudflare","cloudflare",{"name":681,"slug":682,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":684,"slug":685,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":665,"slug":666,"type":15},"2026-07-17T06:04:42.853896",{"slug":689,"name":689,"fn":690,"description":691,"org":692,"tags":693,"stars":28,"repoUrl":29,"updatedAt":701},"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},[694,697,700],{"name":695,"slug":696,"type":15},"Automation","automation",{"name":698,"slug":699,"type":15},"Desktop","desktop",{"name":523,"slug":524,"type":15},"2026-07-13T06:40:38.798626",128]