[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-production-incident-responder":3,"mdc--8eq3y0-key":39,"related-org-jetbrains-production-incident-responder":460,"related-repo-jetbrains-production-incident-responder":591},{"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},"production-incident-responder","guide production incident response for Spring services","Guide production incident response for Kotlin plus Spring services from first alert through mitigation, diagnosis, and follow-up. Use when error rates spike, latency degrades, capacity saturates, a bad deploy or config change is suspected, or the team needs reversible mitigation first and deeper root-cause work second.",{"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},"SRE","sre","tag",{"name":17,"slug":18,"type":15},"Kotlin","kotlin",{"name":20,"slug":21,"type":15},"Incident Response","incident-response",{"name":23,"slug":24,"type":15},"Spring","spring",{"name":26,"slug":27,"type":15},"Debugging","debugging",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:46.074784",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\u002Fproduction-incident-responder","---\nname: production-incident-responder\ndescription: Guide production incident response for Kotlin plus Spring services from first alert through mitigation, diagnosis, and follow-up. Use when error rates spike, latency degrades, capacity saturates, a bad deploy or config change is suspected, or the team needs reversible mitigation first and deeper root-cause work second.\nmetadata:\n  short-description: \"Mitigate incidents before deep diagnosis\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fproduction-incident-responder\n---\n\n# Production Incident Responder\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-24`).\n\n## Mission\n\nRestore service safely before chasing perfect explanations.\nKeep mitigation, diagnosis, communication, and evidence preservation disciplined and explicit.\n\n## First Principles\n\n- Mitigate first.\n- Prefer reversible actions over heroic code changes.\n- Preserve evidence while the system is still exhibiting the problem.\n- Separate confirmed facts from working hypotheses.\n\n## Inputs To Gather\n\n- Current alert state, user impact, and blast radius.\n- Recent deploys, config changes, feature-flag changes, and dependency incidents.\n- Key dashboards: latency, error rate, saturation, dependency health, queue depth, pool usage.\n- Correlated traces and logs for the failing path.\n- Known runbooks, rollback mechanisms, and feature flags.\n\n## Response Sequence\n\n1. State impact and likely severity.\n2. Stop unsafe changes and identify the fastest reversible mitigation:\n   - rollback\n   - disable feature\n   - reduce concurrency\n   - shed load\n   - rate-limit callers\n   - isolate or degrade a dependency\n3. Preserve high-signal evidence while the symptom still exists.\n4. Compare timeline of incident onset with recent changes.\n5. Localize the failing layer: application, database, downstream dependency, queue, infrastructure, or configuration.\n6. Propose long-term corrective actions only after the service is stable.\n\n## Advanced Incident Heuristics\n\n- Restarting everything can destroy the best evidence and amplify a connection storm. Use restarts deliberately, not reflexively.\n- Scaling the app tier does not help when the database or a downstream service is the bottleneck.\n- Rate-limiting or queue pausing may protect core flows better than full rollback when only one feature path is toxic.\n- A config-only incident can look like a code regression; compare effective runtime values before patching application code.\n- A healthy dependency at low volume can still fail under retry storms from your own fleet.\n- If the system uses caches, verify whether bad cache fill, stampede, or stale data amplified the incident.\n- If the incident is intermittent, preserve timing and hypothesis logs. Races and saturation patterns are easy to lose after mitigation.\n- Post-incident work must include detection and prevention, not only the code fix.\n\n## Incident Command Nuances\n\n- One person should own technical command during a serious incident. Parallel debugging without a decision owner often slows mitigation.\n- Communication cadence matters. Operators and stakeholders need regular updates even when the technical picture is incomplete.\n- Rollback is not always safe if data shape or side effects have already changed. Assess rollback safety before pressing the button.\n- Canary comparison, feature-flag cohort analysis, and effective-config diffing often localize incidents faster than code inspection.\n- Preserve version, commit, config, and infrastructure fingerprints in the incident notes while they are still recoverable.\n\n## Expert Heuristics\n\n- Choose the first mitigation that reduces blast radius and buys time, not the one that feels most technically satisfying.\n- Prefer mitigations that also test a hypothesis when that can be done safely.\n- If the incident spans several layers, identify the current bottlenecked layer first. Solving secondary symptoms wastes the window of action.\n- A good postmortem action item changes detection, defaults, rollout strategy, or operational safety nets, not just one line of code.\n\n## Output Contract\n\nReturn these sections:\n\n- `Impact`: who or what is affected and how badly.\n- `Immediate mitigation`: the safest reversible action to reduce pain now.\n- `Evidence`: the strongest signals collected so far.\n- `Working hypothesis`: the leading explanation plus uncertainty.\n- `Next diagnostic step`: the most informative next action once stable.\n- `Follow-up`: long-term fix, monitoring change, and postmortem actions.\n\n## Guardrails\n\n- Do not recommend code changes as the very first incident action when a reversible mitigation exists.\n- Do not claim root cause certainty without evidence.\n- Do not optimize for elegance over containment during an outage.\n- Do not forget operator communication and blast-radius tracking while debugging.\n\n## Quality Bar\n\nA good run of this skill reduces user pain quickly and leaves the team with a cleaner path to root cause.\nA bad run jumps to speculative code fixes while the service remains unstable and evidence disappears.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":17,"source":43},"Mitigate incidents before deep diagnosis","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fproduction-incident-responder",{"type":45,"children":46},"root",[47,55,78,85,90,96,121,127,155,161,228,234,277,283,311,317,340,346,351,420,426,449,455],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Production Incident Responder",{"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-24",{"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},"Restore service safely before chasing perfect explanations.\nKeep mitigation, diagnosis, communication, and evidence preservation disciplined and explicit.",{"type":48,"tag":79,"props":91,"children":93},{"id":92},"first-principles",[94],{"type":53,"value":95},"First Principles",{"type":48,"tag":97,"props":98,"children":99},"ul",{},[100,106,111,116],{"type":48,"tag":101,"props":102,"children":103},"li",{},[104],{"type":53,"value":105},"Mitigate first.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"Prefer reversible actions over heroic code changes.",{"type":48,"tag":101,"props":112,"children":113},{},[114],{"type":53,"value":115},"Preserve evidence while the system is still exhibiting the problem.",{"type":48,"tag":101,"props":117,"children":118},{},[119],{"type":53,"value":120},"Separate confirmed facts from working hypotheses.",{"type":48,"tag":79,"props":122,"children":124},{"id":123},"inputs-to-gather",[125],{"type":53,"value":126},"Inputs To Gather",{"type":48,"tag":97,"props":128,"children":129},{},[130,135,140,145,150],{"type":48,"tag":101,"props":131,"children":132},{},[133],{"type":53,"value":134},"Current alert state, user impact, and blast radius.",{"type":48,"tag":101,"props":136,"children":137},{},[138],{"type":53,"value":139},"Recent deploys, config changes, feature-flag changes, and dependency incidents.",{"type":48,"tag":101,"props":141,"children":142},{},[143],{"type":53,"value":144},"Key dashboards: latency, error rate, saturation, dependency health, queue depth, pool usage.",{"type":48,"tag":101,"props":146,"children":147},{},[148],{"type":53,"value":149},"Correlated traces and logs for the failing path.",{"type":48,"tag":101,"props":151,"children":152},{},[153],{"type":53,"value":154},"Known runbooks, rollback mechanisms, and feature flags.",{"type":48,"tag":79,"props":156,"children":158},{"id":157},"response-sequence",[159],{"type":53,"value":160},"Response Sequence",{"type":48,"tag":162,"props":163,"children":164},"ol",{},[165,170,208,213,218,223],{"type":48,"tag":101,"props":166,"children":167},{},[168],{"type":53,"value":169},"State impact and likely severity.",{"type":48,"tag":101,"props":171,"children":172},{},[173,175],{"type":53,"value":174},"Stop unsafe changes and identify the fastest reversible mitigation:\n",{"type":48,"tag":97,"props":176,"children":177},{},[178,183,188,193,198,203],{"type":48,"tag":101,"props":179,"children":180},{},[181],{"type":53,"value":182},"rollback",{"type":48,"tag":101,"props":184,"children":185},{},[186],{"type":53,"value":187},"disable feature",{"type":48,"tag":101,"props":189,"children":190},{},[191],{"type":53,"value":192},"reduce concurrency",{"type":48,"tag":101,"props":194,"children":195},{},[196],{"type":53,"value":197},"shed load",{"type":48,"tag":101,"props":199,"children":200},{},[201],{"type":53,"value":202},"rate-limit callers",{"type":48,"tag":101,"props":204,"children":205},{},[206],{"type":53,"value":207},"isolate or degrade a dependency",{"type":48,"tag":101,"props":209,"children":210},{},[211],{"type":53,"value":212},"Preserve high-signal evidence while the symptom still exists.",{"type":48,"tag":101,"props":214,"children":215},{},[216],{"type":53,"value":217},"Compare timeline of incident onset with recent changes.",{"type":48,"tag":101,"props":219,"children":220},{},[221],{"type":53,"value":222},"Localize the failing layer: application, database, downstream dependency, queue, infrastructure, or configuration.",{"type":48,"tag":101,"props":224,"children":225},{},[226],{"type":53,"value":227},"Propose long-term corrective actions only after the service is stable.",{"type":48,"tag":79,"props":229,"children":231},{"id":230},"advanced-incident-heuristics",[232],{"type":53,"value":233},"Advanced Incident Heuristics",{"type":48,"tag":97,"props":235,"children":236},{},[237,242,247,252,257,262,267,272],{"type":48,"tag":101,"props":238,"children":239},{},[240],{"type":53,"value":241},"Restarting everything can destroy the best evidence and amplify a connection storm. Use restarts deliberately, not reflexively.",{"type":48,"tag":101,"props":243,"children":244},{},[245],{"type":53,"value":246},"Scaling the app tier does not help when the database or a downstream service is the bottleneck.",{"type":48,"tag":101,"props":248,"children":249},{},[250],{"type":53,"value":251},"Rate-limiting or queue pausing may protect core flows better than full rollback when only one feature path is toxic.",{"type":48,"tag":101,"props":253,"children":254},{},[255],{"type":53,"value":256},"A config-only incident can look like a code regression; compare effective runtime values before patching application code.",{"type":48,"tag":101,"props":258,"children":259},{},[260],{"type":53,"value":261},"A healthy dependency at low volume can still fail under retry storms from your own fleet.",{"type":48,"tag":101,"props":263,"children":264},{},[265],{"type":53,"value":266},"If the system uses caches, verify whether bad cache fill, stampede, or stale data amplified the incident.",{"type":48,"tag":101,"props":268,"children":269},{},[270],{"type":53,"value":271},"If the incident is intermittent, preserve timing and hypothesis logs. Races and saturation patterns are easy to lose after mitigation.",{"type":48,"tag":101,"props":273,"children":274},{},[275],{"type":53,"value":276},"Post-incident work must include detection and prevention, not only the code fix.",{"type":48,"tag":79,"props":278,"children":280},{"id":279},"incident-command-nuances",[281],{"type":53,"value":282},"Incident Command Nuances",{"type":48,"tag":97,"props":284,"children":285},{},[286,291,296,301,306],{"type":48,"tag":101,"props":287,"children":288},{},[289],{"type":53,"value":290},"One person should own technical command during a serious incident. Parallel debugging without a decision owner often slows mitigation.",{"type":48,"tag":101,"props":292,"children":293},{},[294],{"type":53,"value":295},"Communication cadence matters. Operators and stakeholders need regular updates even when the technical picture is incomplete.",{"type":48,"tag":101,"props":297,"children":298},{},[299],{"type":53,"value":300},"Rollback is not always safe if data shape or side effects have already changed. Assess rollback safety before pressing the button.",{"type":48,"tag":101,"props":302,"children":303},{},[304],{"type":53,"value":305},"Canary comparison, feature-flag cohort analysis, and effective-config diffing often localize incidents faster than code inspection.",{"type":48,"tag":101,"props":307,"children":308},{},[309],{"type":53,"value":310},"Preserve version, commit, config, and infrastructure fingerprints in the incident notes while they are still recoverable.",{"type":48,"tag":79,"props":312,"children":314},{"id":313},"expert-heuristics",[315],{"type":53,"value":316},"Expert Heuristics",{"type":48,"tag":97,"props":318,"children":319},{},[320,325,330,335],{"type":48,"tag":101,"props":321,"children":322},{},[323],{"type":53,"value":324},"Choose the first mitigation that reduces blast radius and buys time, not the one that feels most technically satisfying.",{"type":48,"tag":101,"props":326,"children":327},{},[328],{"type":53,"value":329},"Prefer mitigations that also test a hypothesis when that can be done safely.",{"type":48,"tag":101,"props":331,"children":332},{},[333],{"type":53,"value":334},"If the incident spans several layers, identify the current bottlenecked layer first. Solving secondary symptoms wastes the window of action.",{"type":48,"tag":101,"props":336,"children":337},{},[338],{"type":53,"value":339},"A good postmortem action item changes detection, defaults, rollout strategy, or operational safety nets, not just one line of code.",{"type":48,"tag":79,"props":341,"children":343},{"id":342},"output-contract",[344],{"type":53,"value":345},"Output Contract",{"type":48,"tag":56,"props":347,"children":348},{},[349],{"type":53,"value":350},"Return these sections:",{"type":48,"tag":97,"props":352,"children":353},{},[354,365,376,387,398,409],{"type":48,"tag":101,"props":355,"children":356},{},[357,363],{"type":48,"tag":62,"props":358,"children":360},{"className":359},[],[361],{"type":53,"value":362},"Impact",{"type":53,"value":364},": who or what is affected and how badly.",{"type":48,"tag":101,"props":366,"children":367},{},[368,374],{"type":48,"tag":62,"props":369,"children":371},{"className":370},[],[372],{"type":53,"value":373},"Immediate mitigation",{"type":53,"value":375},": the safest reversible action to reduce pain now.",{"type":48,"tag":101,"props":377,"children":378},{},[379,385],{"type":48,"tag":62,"props":380,"children":382},{"className":381},[],[383],{"type":53,"value":384},"Evidence",{"type":53,"value":386},": the strongest signals collected so far.",{"type":48,"tag":101,"props":388,"children":389},{},[390,396],{"type":48,"tag":62,"props":391,"children":393},{"className":392},[],[394],{"type":53,"value":395},"Working hypothesis",{"type":53,"value":397},": the leading explanation plus uncertainty.",{"type":48,"tag":101,"props":399,"children":400},{},[401,407],{"type":48,"tag":62,"props":402,"children":404},{"className":403},[],[405],{"type":53,"value":406},"Next diagnostic step",{"type":53,"value":408},": the most informative next action once stable.",{"type":48,"tag":101,"props":410,"children":411},{},[412,418],{"type":48,"tag":62,"props":413,"children":415},{"className":414},[],[416],{"type":53,"value":417},"Follow-up",{"type":53,"value":419},": long-term fix, monitoring change, and postmortem actions.",{"type":48,"tag":79,"props":421,"children":423},{"id":422},"guardrails",[424],{"type":53,"value":425},"Guardrails",{"type":48,"tag":97,"props":427,"children":428},{},[429,434,439,444],{"type":48,"tag":101,"props":430,"children":431},{},[432],{"type":53,"value":433},"Do not recommend code changes as the very first incident action when a reversible mitigation exists.",{"type":48,"tag":101,"props":435,"children":436},{},[437],{"type":53,"value":438},"Do not claim root cause certainty without evidence.",{"type":48,"tag":101,"props":440,"children":441},{},[442],{"type":53,"value":443},"Do not optimize for elegance over containment during an outage.",{"type":48,"tag":101,"props":445,"children":446},{},[447],{"type":53,"value":448},"Do not forget operator communication and blast-radius tracking while debugging.",{"type":48,"tag":79,"props":450,"children":452},{"id":451},"quality-bar",[453],{"type":53,"value":454},"Quality Bar",{"type":48,"tag":56,"props":456,"children":457},{},[458],{"type":53,"value":459},"A good run of this skill reduces user pain quickly and leaves the team with a cleaner path to root cause.\nA bad run jumps to speculative code fixes while the service remains unstable and evidence disappears.",{"items":461,"total":590},[462,480,489,498,509,519,532,541,550,560,569,580],{"slug":463,"name":463,"fn":464,"description":465,"org":466,"tags":467,"stars":477,"repoUrl":478,"updatedAt":479},"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},[468,471,474],{"name":469,"slug":470,"type":15},"Architecture","architecture",{"name":472,"slug":473,"type":15},"Configuration","configuration",{"name":475,"slug":476,"type":15},"Engineering","engineering",1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":481,"name":481,"fn":482,"description":483,"org":484,"tags":485,"stars":477,"repoUrl":478,"updatedAt":488},"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},[486,487],{"name":469,"slug":470,"type":15},{"name":475,"slug":476,"type":15},"2026-07-17T06:04:48.066901",{"slug":490,"name":490,"fn":491,"description":492,"org":493,"tags":494,"stars":477,"repoUrl":478,"updatedAt":497},"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},[495,496],{"name":469,"slug":470,"type":15},{"name":475,"slug":476,"type":15},"2026-07-13T06:45:21.757084",{"slug":499,"name":499,"fn":500,"description":501,"org":502,"tags":503,"stars":477,"repoUrl":478,"updatedAt":508},"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},[504,505],{"name":469,"slug":470,"type":15},{"name":506,"slug":507,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":510,"name":510,"fn":511,"description":512,"org":513,"tags":514,"stars":477,"repoUrl":478,"updatedAt":518},"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},[515],{"name":516,"slug":517,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":520,"name":520,"fn":521,"description":522,"org":523,"tags":524,"stars":477,"repoUrl":478,"updatedAt":531},"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},[525,528],{"name":526,"slug":527,"type":15},"Design","design",{"name":529,"slug":530,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":533,"name":533,"fn":534,"description":535,"org":536,"tags":537,"stars":477,"repoUrl":478,"updatedAt":540},"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},[538,539],{"name":475,"slug":476,"type":15},{"name":529,"slug":530,"type":15},"2026-07-23T05:41:49.666535",{"slug":542,"name":542,"fn":543,"description":544,"org":545,"tags":546,"stars":477,"repoUrl":478,"updatedAt":549},"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},[547,548],{"name":469,"slug":470,"type":15},{"name":475,"slug":476,"type":15},"2026-07-13T06:44:59.507855",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":477,"repoUrl":478,"updatedAt":559},"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},[556,557,558],{"name":469,"slug":470,"type":15},{"name":506,"slug":507,"type":15},{"name":475,"slug":476,"type":15},"2026-07-17T06:06:58.042999",{"slug":561,"name":561,"fn":562,"description":563,"org":564,"tags":565,"stars":477,"repoUrl":478,"updatedAt":568},"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},[566,567],{"name":469,"slug":470,"type":15},{"name":475,"slug":476,"type":15},"2026-07-23T05:41:48.692899",{"slug":570,"name":570,"fn":571,"description":572,"org":573,"tags":574,"stars":477,"repoUrl":478,"updatedAt":579},"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},[575,576],{"name":26,"slug":27,"type":15},{"name":577,"slug":578,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":477,"repoUrl":478,"updatedAt":589},"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},[586],{"name":587,"slug":588,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":592,"total":706},[593,612,627,641,656,675,692],{"slug":594,"name":594,"fn":595,"description":596,"org":597,"tags":598,"stars":28,"repoUrl":29,"updatedAt":611},"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},[599,602,605,608],{"name":600,"slug":601,"type":15},"Creative","creative",{"name":603,"slug":604,"type":15},"Generative Art","generative-art",{"name":606,"slug":607,"type":15},"Graphics","graphics",{"name":609,"slug":610,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":613,"name":613,"fn":614,"description":615,"org":616,"tags":617,"stars":28,"repoUrl":29,"updatedAt":626},"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},[618,621,622,623],{"name":619,"slug":620,"type":15},"Best Practices","best-practices",{"name":475,"slug":476,"type":15},{"name":609,"slug":610,"type":15},{"name":624,"slug":625,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":628,"name":628,"fn":629,"description":630,"org":631,"tags":632,"stars":28,"repoUrl":29,"updatedAt":640},"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},[633,636,637],{"name":634,"slug":635,"type":15},"Branding","branding",{"name":526,"slug":527,"type":15},{"name":638,"slug":639,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":642,"name":642,"fn":643,"description":644,"org":645,"tags":646,"stars":28,"repoUrl":29,"updatedAt":655},"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},[647,648,649,652],{"name":600,"slug":601,"type":15},{"name":526,"slug":527,"type":15},{"name":650,"slug":651,"type":15},"Images","images",{"name":653,"slug":654,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":657,"name":657,"fn":658,"description":659,"org":660,"tags":661,"stars":28,"repoUrl":29,"updatedAt":674},"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},[662,665,668,671,672,673],{"name":663,"slug":664,"type":15},"CI\u002FCD","ci-cd",{"name":666,"slug":667,"type":15},"Containers","containers",{"name":669,"slug":670,"type":15},"Deployment","deployment",{"name":475,"slug":476,"type":15},{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:41:47.83899",{"slug":676,"name":676,"fn":677,"description":678,"org":679,"tags":680,"stars":28,"repoUrl":29,"updatedAt":691},"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},[681,684,687,690],{"name":682,"slug":683,"type":15},"Cloudflare","cloudflare",{"name":685,"slug":686,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":688,"slug":689,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":669,"slug":670,"type":15},"2026-07-17T06:04:42.853896",{"slug":693,"name":693,"fn":694,"description":695,"org":696,"tags":697,"stars":28,"repoUrl":29,"updatedAt":705},"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},[698,701,704],{"name":699,"slug":700,"type":15},"Automation","automation",{"name":702,"slug":703,"type":15},"Desktop","desktop",{"name":529,"slug":530,"type":15},"2026-07-13T06:40:38.798626",128]