[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-spring-kotlin-code-review":3,"mdc-q2wcmk-key":39,"related-org-jetbrains-spring-kotlin-code-review":471,"related-repo-jetbrains-spring-kotlin-code-review":602},{"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},"spring-kotlin-code-review","review Kotlin and Spring application code","Review Kotlin + Spring changes for behavioral regressions, transaction and proxy bugs, API and serialization mistakes, persistence risks, security issues, configuration drift, and missing tests. Use when reviewing a PR, diff, patch, or design change where generic style-focused review would miss Spring-specific correctness and operational risks.",{"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},"Security","security","tag",{"name":17,"slug":18,"type":15},"Kotlin","kotlin",{"name":20,"slug":21,"type":15},"Code Review","code-review",{"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:42:26.905459",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\u002Fspring-kotlin-code-review","---\nname: spring-kotlin-code-review\ndescription: Review Kotlin + Spring changes for behavioral regressions, transaction and proxy bugs, API and serialization mistakes, persistence risks, security issues, configuration drift, and missing tests. Use when reviewing a PR, diff, patch, or design change where generic style-focused review would miss Spring-specific correctness and operational risks.\nmetadata:\n  short-description: \"Review PRs for Spring-specific risks\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fspring-kotlin-code-review\n---\n\n# Spring Kotlin Code Review\n\nSource mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-21`).\n\n## Mission\n\nReview changes the way a strong Kotlin plus Spring teammate would review them: behavior first, risk first, evidence first.\nOptimize for catching bugs, regressions, and missing tests, not for polishing style.\n\n## Read In This Order\n\n- Diff or changed files.\n- Related tests.\n- Configuration or build file changes.\n- Impacted controllers, services, repositories, security config, and migrations.\n- Project conventions from `project-context-ingestion` if available.\n\n## Review Dimensions\n\nCheck every relevant change for:\n\n- transaction boundaries and rollback behavior\n- proxy compatibility and self-invocation traps\n- bean wiring and configuration safety\n- API contract, validation, and serialization correctness\n- JPA or repository correctness and performance\n- security exposure and authorization drift\n- concurrency, retries, and idempotency risks\n- observability regressions\n- test adequacy and missing failure-path coverage\n- Kotlin-specific problems such as `!!`, unsafe platform types, and misuse of `lateinit`\n\n## Output Contract\n\nReturn findings first and order them by severity.\nUse this structure:\n\n- `Findings`: each finding should name the risk, explain the consequence, and point to the relevant file and line when available.\n- `Open questions or assumptions`: only where uncertainty changes the review outcome.\n- `Summary`: only after findings, and only briefly.\n\nIf no material findings exist, say so explicitly and still note residual risk or testing gaps.\n\n## What Counts As A Real Finding\n\n- A correctness bug.\n- A production-risking design choice.\n- A likely regression.\n- A security or data-consistency hole.\n- Missing coverage for a meaningful failure path.\n\nMinor style suggestions are secondary and should never drown out real risk.\n\n## Review Heuristics\n\n- Prefer a smaller number of well-supported findings over a long list of weak suspicions.\n- Tie every finding to behavior, not only to taste.\n- Verify whether the repository's existing conventions intentionally justify an unusual pattern before flagging it.\n- Distinguish `must fix` concerns from `consider improving` concerns.\n\n## Advanced Review Checklist\n\n- Check deploy-order safety. A code change, config change, and migration may each be correct alone but unsafe in rolling deployment order.\n- Check backward compatibility of JSON contracts, event schemas, database writes, and feature flags. Additive changes are safer than semantic changes hidden behind the same shape.\n- Check cache invalidation, deduplication, retry semantics, and idempotency whenever writes or integrations change.\n- Check whether observability changed with the behavior. A new critical path without metrics, logs, or trace propagation is a real operational regression.\n- Check whether new repository queries need supporting indexes or whether an innocuous loop creates N+1 behavior.\n- Check whether any new async, scheduled, or concurrent path changes transaction scope, MDC propagation, or security context.\n- Check build and dependency changes for BOM drift, plugin mismatches, or silent classpath changes.\n- Check what was removed, not only what was added. Missing validation, logging, or authorization is often the real regression.\n\n## Expert Heuristics\n\n- Read the change as a workflow, not as isolated files. Many Spring bugs live in the seam between controller, service, repository, and config.\n- If a finding depends on an assumption, state the assumption and the fastest way to confirm it.\n- Prefer findings that are expensive for the team to rediscover in production.\n- Use style comments only when they prevent future correctness bugs or materially improve maintainability.\n\n## Guardrails\n\n- Do not nitpick naming or formatting when the change contains higher-severity risk.\n- Do not invent risks without code evidence.\n- Do not praise or summarize before surfacing findings.\n- Do not ignore missing tests just because the code \"looks straightforward.\"\n- Do not apply generic Java advice without checking Kotlin and Spring specifics.\n\n## Quality Bar\n\nA good run of this skill gives the author a short list of concrete, high-signal risks to address.\nA bad run reads like a generic lint pass and misses the transactional, proxy, security, or persistence behavior that actually matters.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":17,"source":43},"Review PRs for Spring-specific risks","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fspring-kotlin-code-review",{"type":45,"children":46},"root",[47,55,78,85,90,96,134,140,145,212,218,223,259,264,270,298,303,309,348,354,397,403,426,432,460,466],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Spring Kotlin Code Review",{"type":48,"tag":56,"props":57,"children":58},"p",{},[59,61,68,70,76],{"type":53,"value":60},"Source mapping: Tier 1 critical 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-21",{"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},"Review changes the way a strong Kotlin plus Spring teammate would review them: behavior first, risk first, evidence first.\nOptimize for catching bugs, regressions, and missing tests, not for polishing style.",{"type":48,"tag":79,"props":91,"children":93},{"id":92},"read-in-this-order",[94],{"type":53,"value":95},"Read In This Order",{"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},"Diff or changed files.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"Related tests.",{"type":48,"tag":101,"props":112,"children":113},{},[114],{"type":53,"value":115},"Configuration or build file changes.",{"type":48,"tag":101,"props":117,"children":118},{},[119],{"type":53,"value":120},"Impacted controllers, services, repositories, security config, and migrations.",{"type":48,"tag":101,"props":122,"children":123},{},[124,126,132],{"type":53,"value":125},"Project conventions from ",{"type":48,"tag":62,"props":127,"children":129},{"className":128},[],[130],{"type":53,"value":131},"project-context-ingestion",{"type":53,"value":133}," if available.",{"type":48,"tag":79,"props":135,"children":137},{"id":136},"review-dimensions",[138],{"type":53,"value":139},"Review Dimensions",{"type":48,"tag":56,"props":141,"children":142},{},[143],{"type":53,"value":144},"Check every relevant change for:",{"type":48,"tag":97,"props":146,"children":147},{},[148,153,158,163,168,173,178,183,188,193],{"type":48,"tag":101,"props":149,"children":150},{},[151],{"type":53,"value":152},"transaction boundaries and rollback behavior",{"type":48,"tag":101,"props":154,"children":155},{},[156],{"type":53,"value":157},"proxy compatibility and self-invocation traps",{"type":48,"tag":101,"props":159,"children":160},{},[161],{"type":53,"value":162},"bean wiring and configuration safety",{"type":48,"tag":101,"props":164,"children":165},{},[166],{"type":53,"value":167},"API contract, validation, and serialization correctness",{"type":48,"tag":101,"props":169,"children":170},{},[171],{"type":53,"value":172},"JPA or repository correctness and performance",{"type":48,"tag":101,"props":174,"children":175},{},[176],{"type":53,"value":177},"security exposure and authorization drift",{"type":48,"tag":101,"props":179,"children":180},{},[181],{"type":53,"value":182},"concurrency, retries, and idempotency risks",{"type":48,"tag":101,"props":184,"children":185},{},[186],{"type":53,"value":187},"observability regressions",{"type":48,"tag":101,"props":189,"children":190},{},[191],{"type":53,"value":192},"test adequacy and missing failure-path coverage",{"type":48,"tag":101,"props":194,"children":195},{},[196,198,204,206],{"type":53,"value":197},"Kotlin-specific problems such as ",{"type":48,"tag":62,"props":199,"children":201},{"className":200},[],[202],{"type":53,"value":203},"!!",{"type":53,"value":205},", unsafe platform types, and misuse of ",{"type":48,"tag":62,"props":207,"children":209},{"className":208},[],[210],{"type":53,"value":211},"lateinit",{"type":48,"tag":79,"props":213,"children":215},{"id":214},"output-contract",[216],{"type":53,"value":217},"Output Contract",{"type":48,"tag":56,"props":219,"children":220},{},[221],{"type":53,"value":222},"Return findings first and order them by severity.\nUse this structure:",{"type":48,"tag":97,"props":224,"children":225},{},[226,237,248],{"type":48,"tag":101,"props":227,"children":228},{},[229,235],{"type":48,"tag":62,"props":230,"children":232},{"className":231},[],[233],{"type":53,"value":234},"Findings",{"type":53,"value":236},": each finding should name the risk, explain the consequence, and point to the relevant file and line when available.",{"type":48,"tag":101,"props":238,"children":239},{},[240,246],{"type":48,"tag":62,"props":241,"children":243},{"className":242},[],[244],{"type":53,"value":245},"Open questions or assumptions",{"type":53,"value":247},": only where uncertainty changes the review outcome.",{"type":48,"tag":101,"props":249,"children":250},{},[251,257],{"type":48,"tag":62,"props":252,"children":254},{"className":253},[],[255],{"type":53,"value":256},"Summary",{"type":53,"value":258},": only after findings, and only briefly.",{"type":48,"tag":56,"props":260,"children":261},{},[262],{"type":53,"value":263},"If no material findings exist, say so explicitly and still note residual risk or testing gaps.",{"type":48,"tag":79,"props":265,"children":267},{"id":266},"what-counts-as-a-real-finding",[268],{"type":53,"value":269},"What Counts As A Real Finding",{"type":48,"tag":97,"props":271,"children":272},{},[273,278,283,288,293],{"type":48,"tag":101,"props":274,"children":275},{},[276],{"type":53,"value":277},"A correctness bug.",{"type":48,"tag":101,"props":279,"children":280},{},[281],{"type":53,"value":282},"A production-risking design choice.",{"type":48,"tag":101,"props":284,"children":285},{},[286],{"type":53,"value":287},"A likely regression.",{"type":48,"tag":101,"props":289,"children":290},{},[291],{"type":53,"value":292},"A security or data-consistency hole.",{"type":48,"tag":101,"props":294,"children":295},{},[296],{"type":53,"value":297},"Missing coverage for a meaningful failure path.",{"type":48,"tag":56,"props":299,"children":300},{},[301],{"type":53,"value":302},"Minor style suggestions are secondary and should never drown out real risk.",{"type":48,"tag":79,"props":304,"children":306},{"id":305},"review-heuristics",[307],{"type":53,"value":308},"Review Heuristics",{"type":48,"tag":97,"props":310,"children":311},{},[312,317,322,327],{"type":48,"tag":101,"props":313,"children":314},{},[315],{"type":53,"value":316},"Prefer a smaller number of well-supported findings over a long list of weak suspicions.",{"type":48,"tag":101,"props":318,"children":319},{},[320],{"type":53,"value":321},"Tie every finding to behavior, not only to taste.",{"type":48,"tag":101,"props":323,"children":324},{},[325],{"type":53,"value":326},"Verify whether the repository's existing conventions intentionally justify an unusual pattern before flagging it.",{"type":48,"tag":101,"props":328,"children":329},{},[330,332,338,340,346],{"type":53,"value":331},"Distinguish ",{"type":48,"tag":62,"props":333,"children":335},{"className":334},[],[336],{"type":53,"value":337},"must fix",{"type":53,"value":339}," concerns from ",{"type":48,"tag":62,"props":341,"children":343},{"className":342},[],[344],{"type":53,"value":345},"consider improving",{"type":53,"value":347}," concerns.",{"type":48,"tag":79,"props":349,"children":351},{"id":350},"advanced-review-checklist",[352],{"type":53,"value":353},"Advanced Review Checklist",{"type":48,"tag":97,"props":355,"children":356},{},[357,362,367,372,377,382,387,392],{"type":48,"tag":101,"props":358,"children":359},{},[360],{"type":53,"value":361},"Check deploy-order safety. A code change, config change, and migration may each be correct alone but unsafe in rolling deployment order.",{"type":48,"tag":101,"props":363,"children":364},{},[365],{"type":53,"value":366},"Check backward compatibility of JSON contracts, event schemas, database writes, and feature flags. Additive changes are safer than semantic changes hidden behind the same shape.",{"type":48,"tag":101,"props":368,"children":369},{},[370],{"type":53,"value":371},"Check cache invalidation, deduplication, retry semantics, and idempotency whenever writes or integrations change.",{"type":48,"tag":101,"props":373,"children":374},{},[375],{"type":53,"value":376},"Check whether observability changed with the behavior. A new critical path without metrics, logs, or trace propagation is a real operational regression.",{"type":48,"tag":101,"props":378,"children":379},{},[380],{"type":53,"value":381},"Check whether new repository queries need supporting indexes or whether an innocuous loop creates N+1 behavior.",{"type":48,"tag":101,"props":383,"children":384},{},[385],{"type":53,"value":386},"Check whether any new async, scheduled, or concurrent path changes transaction scope, MDC propagation, or security context.",{"type":48,"tag":101,"props":388,"children":389},{},[390],{"type":53,"value":391},"Check build and dependency changes for BOM drift, plugin mismatches, or silent classpath changes.",{"type":48,"tag":101,"props":393,"children":394},{},[395],{"type":53,"value":396},"Check what was removed, not only what was added. Missing validation, logging, or authorization is often the real regression.",{"type":48,"tag":79,"props":398,"children":400},{"id":399},"expert-heuristics",[401],{"type":53,"value":402},"Expert Heuristics",{"type":48,"tag":97,"props":404,"children":405},{},[406,411,416,421],{"type":48,"tag":101,"props":407,"children":408},{},[409],{"type":53,"value":410},"Read the change as a workflow, not as isolated files. Many Spring bugs live in the seam between controller, service, repository, and config.",{"type":48,"tag":101,"props":412,"children":413},{},[414],{"type":53,"value":415},"If a finding depends on an assumption, state the assumption and the fastest way to confirm it.",{"type":48,"tag":101,"props":417,"children":418},{},[419],{"type":53,"value":420},"Prefer findings that are expensive for the team to rediscover in production.",{"type":48,"tag":101,"props":422,"children":423},{},[424],{"type":53,"value":425},"Use style comments only when they prevent future correctness bugs or materially improve maintainability.",{"type":48,"tag":79,"props":427,"children":429},{"id":428},"guardrails",[430],{"type":53,"value":431},"Guardrails",{"type":48,"tag":97,"props":433,"children":434},{},[435,440,445,450,455],{"type":48,"tag":101,"props":436,"children":437},{},[438],{"type":53,"value":439},"Do not nitpick naming or formatting when the change contains higher-severity risk.",{"type":48,"tag":101,"props":441,"children":442},{},[443],{"type":53,"value":444},"Do not invent risks without code evidence.",{"type":48,"tag":101,"props":446,"children":447},{},[448],{"type":53,"value":449},"Do not praise or summarize before surfacing findings.",{"type":48,"tag":101,"props":451,"children":452},{},[453],{"type":53,"value":454},"Do not ignore missing tests just because the code \"looks straightforward.\"",{"type":48,"tag":101,"props":456,"children":457},{},[458],{"type":53,"value":459},"Do not apply generic Java advice without checking Kotlin and Spring specifics.",{"type":48,"tag":79,"props":461,"children":463},{"id":462},"quality-bar",[464],{"type":53,"value":465},"Quality Bar",{"type":48,"tag":56,"props":467,"children":468},{},[469],{"type":53,"value":470},"A good run of this skill gives the author a short list of concrete, high-signal risks to address.\nA bad run reads like a generic lint pass and misses the transactional, proxy, security, or persistence behavior that actually matters.",{"items":472,"total":601},[473,491,500,509,520,530,543,552,561,571,580,591],{"slug":474,"name":474,"fn":475,"description":476,"org":477,"tags":478,"stars":488,"repoUrl":489,"updatedAt":490},"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},[479,482,485],{"name":480,"slug":481,"type":15},"Architecture","architecture",{"name":483,"slug":484,"type":15},"Configuration","configuration",{"name":486,"slug":487,"type":15},"Engineering","engineering",1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":492,"name":492,"fn":493,"description":494,"org":495,"tags":496,"stars":488,"repoUrl":489,"updatedAt":499},"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},[497,498],{"name":480,"slug":481,"type":15},{"name":486,"slug":487,"type":15},"2026-07-17T06:04:48.066901",{"slug":501,"name":501,"fn":502,"description":503,"org":504,"tags":505,"stars":488,"repoUrl":489,"updatedAt":508},"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},[506,507],{"name":480,"slug":481,"type":15},{"name":486,"slug":487,"type":15},"2026-07-13T06:45:21.757084",{"slug":510,"name":510,"fn":511,"description":512,"org":513,"tags":514,"stars":488,"repoUrl":489,"updatedAt":519},"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},[515,516],{"name":480,"slug":481,"type":15},{"name":517,"slug":518,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":521,"name":521,"fn":522,"description":523,"org":524,"tags":525,"stars":488,"repoUrl":489,"updatedAt":529},"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},[526],{"name":527,"slug":528,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":488,"repoUrl":489,"updatedAt":542},"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},[536,539],{"name":537,"slug":538,"type":15},"Design","design",{"name":540,"slug":541,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":544,"name":544,"fn":545,"description":546,"org":547,"tags":548,"stars":488,"repoUrl":489,"updatedAt":551},"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},[549,550],{"name":486,"slug":487,"type":15},{"name":540,"slug":541,"type":15},"2026-07-23T05:41:49.666535",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":488,"repoUrl":489,"updatedAt":560},"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},[558,559],{"name":480,"slug":481,"type":15},{"name":486,"slug":487,"type":15},"2026-07-13T06:44:59.507855",{"slug":562,"name":562,"fn":563,"description":564,"org":565,"tags":566,"stars":488,"repoUrl":489,"updatedAt":570},"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},[567,568,569],{"name":480,"slug":481,"type":15},{"name":517,"slug":518,"type":15},{"name":486,"slug":487,"type":15},"2026-07-17T06:06:58.042999",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":488,"repoUrl":489,"updatedAt":579},"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},[577,578],{"name":480,"slug":481,"type":15},{"name":486,"slug":487,"type":15},"2026-07-23T05:41:48.692899",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":488,"repoUrl":489,"updatedAt":590},"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},[586,587],{"name":26,"slug":27,"type":15},{"name":588,"slug":589,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":592,"name":592,"fn":593,"description":594,"org":595,"tags":596,"stars":488,"repoUrl":489,"updatedAt":600},"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},[597],{"name":598,"slug":599,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":603,"total":717},[604,623,638,652,667,686,703],{"slug":605,"name":605,"fn":606,"description":607,"org":608,"tags":609,"stars":28,"repoUrl":29,"updatedAt":622},"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},[610,613,616,619],{"name":611,"slug":612,"type":15},"Creative","creative",{"name":614,"slug":615,"type":15},"Generative Art","generative-art",{"name":617,"slug":618,"type":15},"Graphics","graphics",{"name":620,"slug":621,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":28,"repoUrl":29,"updatedAt":637},"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},[629,632,633,634],{"name":630,"slug":631,"type":15},"Best Practices","best-practices",{"name":486,"slug":487,"type":15},{"name":620,"slug":621,"type":15},{"name":635,"slug":636,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":28,"repoUrl":29,"updatedAt":651},"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},[644,647,648],{"name":645,"slug":646,"type":15},"Branding","branding",{"name":537,"slug":538,"type":15},{"name":649,"slug":650,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":28,"repoUrl":29,"updatedAt":666},"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},[658,659,660,663],{"name":611,"slug":612,"type":15},{"name":537,"slug":538,"type":15},{"name":661,"slug":662,"type":15},"Images","images",{"name":664,"slug":665,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":668,"name":668,"fn":669,"description":670,"org":671,"tags":672,"stars":28,"repoUrl":29,"updatedAt":685},"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},[673,676,679,682,683,684],{"name":674,"slug":675,"type":15},"CI\u002FCD","ci-cd",{"name":677,"slug":678,"type":15},"Containers","containers",{"name":680,"slug":681,"type":15},"Deployment","deployment",{"name":486,"slug":487,"type":15},{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:41:47.83899",{"slug":687,"name":687,"fn":688,"description":689,"org":690,"tags":691,"stars":28,"repoUrl":29,"updatedAt":702},"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},[692,695,698,701],{"name":693,"slug":694,"type":15},"Cloudflare","cloudflare",{"name":696,"slug":697,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":699,"slug":700,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":680,"slug":681,"type":15},"2026-07-17T06:04:42.853896",{"slug":704,"name":704,"fn":705,"description":706,"org":707,"tags":708,"stars":28,"repoUrl":29,"updatedAt":716},"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},[709,712,715],{"name":710,"slug":711,"type":15},"Automation","automation",{"name":713,"slug":714,"type":15},"Desktop","desktop",{"name":540,"slug":541,"type":15},"2026-07-13T06:40:38.798626",128]