[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-ci-cd-containerization-advisor":3,"mdc--m83mv8-key":42,"related-org-jetbrains-ci-cd-containerization-advisor":544,"related-repo-jetbrains-ci-cd-containerization-advisor":675},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":31,"repoUrl":32,"updatedAt":33,"license":34,"forks":35,"topics":36,"repo":37,"sourceUrl":40,"mdContent":41},"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},"jetbrains","JetBrains","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fjetbrains.png",[12,16,19,22,25,28],{"name":13,"slug":14,"type":15},"Kotlin","kotlin","tag",{"name":17,"slug":18,"type":15},"Containers","containers",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Deployment","deployment",{"name":26,"slug":27,"type":15},"Engineering","engineering",{"name":29,"slug":30,"type":15},"CI\u002FCD","ci-cd",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:47.83899",null,17,[],{"repoUrl":32,"stars":31,"forks":35,"topics":38,"description":39},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Fci-cd-containerization-advisor","---\nname: ci-cd-containerization-advisor\ndescription: 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.\nmetadata:\n  short-description: \"Ship Spring apps reliably and repeatably\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fci-cd-containerization-advisor\n---\n\n# CI CD Containerization Advisor\n\nSource mapping: Tier 3 specialized skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-23`).\n\n## Mission\n\nTurn a codebase into a repeatable artifact and a safe deployment process.\nTreat CI, container images, and rollout strategy as one delivery system, not disconnected YAML and Dockerfile fragments.\n\n## Read First\n\n- Build files, wrapper config, and artifact packaging approach.\n- Current CI workflow definitions and caching strategy.\n- Dockerfiles or buildpack usage.\n- Deployment manifests, Helm charts, or platform-specific deployment descriptors.\n- Runtime assumptions: JDK version, JVM options, health probes, config injection, migration process.\n\n## Build Pipeline Rules\n\n- Make the wrapper and toolchain the source of truth for build reproducibility.\n- Keep CI stages explicit:\n  - dependency resolution\n  - compile\n  - tests\n  - packaging\n  - security or policy checks\n  - publish\n- Cache deliberately, but never in a way that hides reproducibility issues.\n- Publish immutable versioned artifacts; avoid \"mystery latest\" promotion paths.\n\n## Container Rules\n\n- Prefer multi-stage builds or buildpacks that produce minimal, reproducible runtime images.\n- Run as non-root.\n- Pin base image families deliberately and know their tradeoffs:\n  - glibc vs musl\n  - distroless vs debug-friendly\n  - JRE vs full JDK\n- Keep image layers stable so dependency and application changes cache efficiently.\n- Separate build-time secrets from runtime secrets.\n- Align container memory and CPU assumptions with JVM container-awareness and runtime limits.\n\n## Deployment Rules\n\n- Define readiness, liveness, and startup probes that reflect real application behavior.\n- Coordinate schema migrations with rollout order deliberately.\n- Use rolling, canary, or blue-green strategies based on blast radius and compatibility constraints.\n- Prefer configuration injection that is explicit and auditable.\n- Record image version, git revision, and effective configuration linkage in the deployed artifact or metadata.\n\n## Advanced Delivery Traps\n\n- Alpine or musl-based images can break native dependencies, DNS behavior, or performance assumptions. Smaller is not always safer.\n- A fast CI cache can hide missing lockfiles, flaky dependency resolution, or undeclared build inputs.\n- Running migrations inside app startup may work locally and deadlock rollout safety in production.\n- Layered jars help build speed, but only if the Dockerfile or buildpack order preserves dependency-cache reuse.\n- Distroless images improve hardening but reduce debugging options. Know the operator tradeoff.\n- Health probes that are too eager can create crash loops during cold startup or migration windows.\n- Resource requests and limits interact with JVM heap sizing, GC, and startup time. Container configuration is part of application performance.\n- Supply-chain controls such as SBOM, vulnerability scanning, signature, and provenance are part of delivery quality for serious systems.\n\n## Runtime Delivery Nuances\n\n- PID 1 signal handling, graceful shutdown, and preStop hooks determine whether rolling deploys drain traffic cleanly or drop requests.\n- Read-only root filesystems, writable temp directories, and filesystem permissions are runtime design choices, not just hardening checkboxes.\n- Digest-pinned base images improve reproducibility but require deliberate patching strategy to avoid silent drift or stale images.\n- Hermetic or near-hermetic builds reduce \"works only in CI\" surprises by making network, timestamp, and undeclared tool dependencies visible.\n- Remote build cache can be a speed win or a correctness trap depending on how well task inputs are modeled.\n- Preview or ephemeral environments can catch config and migration issues early, but only if they use realistic secrets, networking, and backing services.\n\n## Expert Heuristics\n\n- Make local, CI, and production use the same major JDK and Gradle assumptions whenever possible.\n- Prefer one clean deployment path over several partially maintained ones.\n- Design deployment gates around rollback confidence and blast radius, not only around green unit tests.\n- Prefer one debug-friendly escape hatch in operations even if production images are hardened and minimal.\n- Treat supply-chain metadata as something operators may depend on later for incident response, not only for compliance.\n- If the service needs graceful drain or long request handling, prove shutdown behavior under rollout in tests or staging, not only by configuration reading.\n- If zero-downtime matters, force deployment and migration strategy to prove backward compatibility, not just assume it.\n- Design the pipeline so that a failed deploy is cheap to stop and cheap to roll back.\n\n## Output Contract\n\nReturn these sections:\n\n- `Artifact strategy`: how the service is built and packaged.\n- `CI plan`: stages, caches, gates, and artifact publication.\n- `Container plan`: image build strategy, hardening, and runtime assumptions.\n- `Deployment plan`: probe design, rollout strategy, config injection, and migration coordination.\n- `Operational risks`: what could go wrong during build or deploy.\n- `Verification`: the checks that prove the pipeline is reproducible and the rollout is safe.\n\n## Guardrails\n\n- Do not use floating production image tags.\n- Do not run as root without a strong reason.\n- Do not assume the same Docker or CPU environment locally and in CI unless proven.\n- Do not couple schema migration execution to app boot casually.\n- Do not optimize image size at the expense of runtime correctness or operability.\n\n## Quality Bar\n\nA good run of this skill gives the team a build and deployment path that is repeatable, observable, and rollback-aware.\nA bad run outputs a fashionable Dockerfile and CI YAML that still leave runtime drift and deployment risk unresolved.\n",{"data":43,"body":47},{"name":4,"description":6,"metadata":44},{"short-description":45,"author":13,"source":46},"Ship Spring apps reliably and repeatably","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fci-cd-containerization-advisor",{"type":48,"children":49},"root",[50,58,81,88,93,99,129,135,191,197,248,254,282,288,331,337,370,376,419,425,430,499,505,533,539],{"type":51,"tag":52,"props":53,"children":54},"element","h1",{"id":4},[55],{"type":56,"value":57},"text","CI CD Containerization Advisor",{"type":51,"tag":59,"props":60,"children":61},"p",{},[62,64,71,73,79],{"type":56,"value":63},"Source mapping: Tier 3 specialized skill derived from ",{"type":51,"tag":65,"props":66,"children":68},"code",{"className":67},[],[69],{"type":56,"value":70},"Kotlin_Spring_Developer_Pipeline.md",{"type":56,"value":72}," (",{"type":51,"tag":65,"props":74,"children":76},{"className":75},[],[77],{"type":56,"value":78},"SK-23",{"type":56,"value":80},").",{"type":51,"tag":82,"props":83,"children":85},"h2",{"id":84},"mission",[86],{"type":56,"value":87},"Mission",{"type":51,"tag":59,"props":89,"children":90},{},[91],{"type":56,"value":92},"Turn a codebase into a repeatable artifact and a safe deployment process.\nTreat CI, container images, and rollout strategy as one delivery system, not disconnected YAML and Dockerfile fragments.",{"type":51,"tag":82,"props":94,"children":96},{"id":95},"read-first",[97],{"type":56,"value":98},"Read First",{"type":51,"tag":100,"props":101,"children":102},"ul",{},[103,109,114,119,124],{"type":51,"tag":104,"props":105,"children":106},"li",{},[107],{"type":56,"value":108},"Build files, wrapper config, and artifact packaging approach.",{"type":51,"tag":104,"props":110,"children":111},{},[112],{"type":56,"value":113},"Current CI workflow definitions and caching strategy.",{"type":51,"tag":104,"props":115,"children":116},{},[117],{"type":56,"value":118},"Dockerfiles or buildpack usage.",{"type":51,"tag":104,"props":120,"children":121},{},[122],{"type":56,"value":123},"Deployment manifests, Helm charts, or platform-specific deployment descriptors.",{"type":51,"tag":104,"props":125,"children":126},{},[127],{"type":56,"value":128},"Runtime assumptions: JDK version, JVM options, health probes, config injection, migration process.",{"type":51,"tag":82,"props":130,"children":132},{"id":131},"build-pipeline-rules",[133],{"type":56,"value":134},"Build Pipeline Rules",{"type":51,"tag":100,"props":136,"children":137},{},[138,143,181,186],{"type":51,"tag":104,"props":139,"children":140},{},[141],{"type":56,"value":142},"Make the wrapper and toolchain the source of truth for build reproducibility.",{"type":51,"tag":104,"props":144,"children":145},{},[146,148],{"type":56,"value":147},"Keep CI stages explicit:\n",{"type":51,"tag":100,"props":149,"children":150},{},[151,156,161,166,171,176],{"type":51,"tag":104,"props":152,"children":153},{},[154],{"type":56,"value":155},"dependency resolution",{"type":51,"tag":104,"props":157,"children":158},{},[159],{"type":56,"value":160},"compile",{"type":51,"tag":104,"props":162,"children":163},{},[164],{"type":56,"value":165},"tests",{"type":51,"tag":104,"props":167,"children":168},{},[169],{"type":56,"value":170},"packaging",{"type":51,"tag":104,"props":172,"children":173},{},[174],{"type":56,"value":175},"security or policy checks",{"type":51,"tag":104,"props":177,"children":178},{},[179],{"type":56,"value":180},"publish",{"type":51,"tag":104,"props":182,"children":183},{},[184],{"type":56,"value":185},"Cache deliberately, but never in a way that hides reproducibility issues.",{"type":51,"tag":104,"props":187,"children":188},{},[189],{"type":56,"value":190},"Publish immutable versioned artifacts; avoid \"mystery latest\" promotion paths.",{"type":51,"tag":82,"props":192,"children":194},{"id":193},"container-rules",[195],{"type":56,"value":196},"Container Rules",{"type":51,"tag":100,"props":198,"children":199},{},[200,205,210,233,238,243],{"type":51,"tag":104,"props":201,"children":202},{},[203],{"type":56,"value":204},"Prefer multi-stage builds or buildpacks that produce minimal, reproducible runtime images.",{"type":51,"tag":104,"props":206,"children":207},{},[208],{"type":56,"value":209},"Run as non-root.",{"type":51,"tag":104,"props":211,"children":212},{},[213,215],{"type":56,"value":214},"Pin base image families deliberately and know their tradeoffs:\n",{"type":51,"tag":100,"props":216,"children":217},{},[218,223,228],{"type":51,"tag":104,"props":219,"children":220},{},[221],{"type":56,"value":222},"glibc vs musl",{"type":51,"tag":104,"props":224,"children":225},{},[226],{"type":56,"value":227},"distroless vs debug-friendly",{"type":51,"tag":104,"props":229,"children":230},{},[231],{"type":56,"value":232},"JRE vs full JDK",{"type":51,"tag":104,"props":234,"children":235},{},[236],{"type":56,"value":237},"Keep image layers stable so dependency and application changes cache efficiently.",{"type":51,"tag":104,"props":239,"children":240},{},[241],{"type":56,"value":242},"Separate build-time secrets from runtime secrets.",{"type":51,"tag":104,"props":244,"children":245},{},[246],{"type":56,"value":247},"Align container memory and CPU assumptions with JVM container-awareness and runtime limits.",{"type":51,"tag":82,"props":249,"children":251},{"id":250},"deployment-rules",[252],{"type":56,"value":253},"Deployment Rules",{"type":51,"tag":100,"props":255,"children":256},{},[257,262,267,272,277],{"type":51,"tag":104,"props":258,"children":259},{},[260],{"type":56,"value":261},"Define readiness, liveness, and startup probes that reflect real application behavior.",{"type":51,"tag":104,"props":263,"children":264},{},[265],{"type":56,"value":266},"Coordinate schema migrations with rollout order deliberately.",{"type":51,"tag":104,"props":268,"children":269},{},[270],{"type":56,"value":271},"Use rolling, canary, or blue-green strategies based on blast radius and compatibility constraints.",{"type":51,"tag":104,"props":273,"children":274},{},[275],{"type":56,"value":276},"Prefer configuration injection that is explicit and auditable.",{"type":51,"tag":104,"props":278,"children":279},{},[280],{"type":56,"value":281},"Record image version, git revision, and effective configuration linkage in the deployed artifact or metadata.",{"type":51,"tag":82,"props":283,"children":285},{"id":284},"advanced-delivery-traps",[286],{"type":56,"value":287},"Advanced Delivery Traps",{"type":51,"tag":100,"props":289,"children":290},{},[291,296,301,306,311,316,321,326],{"type":51,"tag":104,"props":292,"children":293},{},[294],{"type":56,"value":295},"Alpine or musl-based images can break native dependencies, DNS behavior, or performance assumptions. Smaller is not always safer.",{"type":51,"tag":104,"props":297,"children":298},{},[299],{"type":56,"value":300},"A fast CI cache can hide missing lockfiles, flaky dependency resolution, or undeclared build inputs.",{"type":51,"tag":104,"props":302,"children":303},{},[304],{"type":56,"value":305},"Running migrations inside app startup may work locally and deadlock rollout safety in production.",{"type":51,"tag":104,"props":307,"children":308},{},[309],{"type":56,"value":310},"Layered jars help build speed, but only if the Dockerfile or buildpack order preserves dependency-cache reuse.",{"type":51,"tag":104,"props":312,"children":313},{},[314],{"type":56,"value":315},"Distroless images improve hardening but reduce debugging options. Know the operator tradeoff.",{"type":51,"tag":104,"props":317,"children":318},{},[319],{"type":56,"value":320},"Health probes that are too eager can create crash loops during cold startup or migration windows.",{"type":51,"tag":104,"props":322,"children":323},{},[324],{"type":56,"value":325},"Resource requests and limits interact with JVM heap sizing, GC, and startup time. Container configuration is part of application performance.",{"type":51,"tag":104,"props":327,"children":328},{},[329],{"type":56,"value":330},"Supply-chain controls such as SBOM, vulnerability scanning, signature, and provenance are part of delivery quality for serious systems.",{"type":51,"tag":82,"props":332,"children":334},{"id":333},"runtime-delivery-nuances",[335],{"type":56,"value":336},"Runtime Delivery Nuances",{"type":51,"tag":100,"props":338,"children":339},{},[340,345,350,355,360,365],{"type":51,"tag":104,"props":341,"children":342},{},[343],{"type":56,"value":344},"PID 1 signal handling, graceful shutdown, and preStop hooks determine whether rolling deploys drain traffic cleanly or drop requests.",{"type":51,"tag":104,"props":346,"children":347},{},[348],{"type":56,"value":349},"Read-only root filesystems, writable temp directories, and filesystem permissions are runtime design choices, not just hardening checkboxes.",{"type":51,"tag":104,"props":351,"children":352},{},[353],{"type":56,"value":354},"Digest-pinned base images improve reproducibility but require deliberate patching strategy to avoid silent drift or stale images.",{"type":51,"tag":104,"props":356,"children":357},{},[358],{"type":56,"value":359},"Hermetic or near-hermetic builds reduce \"works only in CI\" surprises by making network, timestamp, and undeclared tool dependencies visible.",{"type":51,"tag":104,"props":361,"children":362},{},[363],{"type":56,"value":364},"Remote build cache can be a speed win or a correctness trap depending on how well task inputs are modeled.",{"type":51,"tag":104,"props":366,"children":367},{},[368],{"type":56,"value":369},"Preview or ephemeral environments can catch config and migration issues early, but only if they use realistic secrets, networking, and backing services.",{"type":51,"tag":82,"props":371,"children":373},{"id":372},"expert-heuristics",[374],{"type":56,"value":375},"Expert Heuristics",{"type":51,"tag":100,"props":377,"children":378},{},[379,384,389,394,399,404,409,414],{"type":51,"tag":104,"props":380,"children":381},{},[382],{"type":56,"value":383},"Make local, CI, and production use the same major JDK and Gradle assumptions whenever possible.",{"type":51,"tag":104,"props":385,"children":386},{},[387],{"type":56,"value":388},"Prefer one clean deployment path over several partially maintained ones.",{"type":51,"tag":104,"props":390,"children":391},{},[392],{"type":56,"value":393},"Design deployment gates around rollback confidence and blast radius, not only around green unit tests.",{"type":51,"tag":104,"props":395,"children":396},{},[397],{"type":56,"value":398},"Prefer one debug-friendly escape hatch in operations even if production images are hardened and minimal.",{"type":51,"tag":104,"props":400,"children":401},{},[402],{"type":56,"value":403},"Treat supply-chain metadata as something operators may depend on later for incident response, not only for compliance.",{"type":51,"tag":104,"props":405,"children":406},{},[407],{"type":56,"value":408},"If the service needs graceful drain or long request handling, prove shutdown behavior under rollout in tests or staging, not only by configuration reading.",{"type":51,"tag":104,"props":410,"children":411},{},[412],{"type":56,"value":413},"If zero-downtime matters, force deployment and migration strategy to prove backward compatibility, not just assume it.",{"type":51,"tag":104,"props":415,"children":416},{},[417],{"type":56,"value":418},"Design the pipeline so that a failed deploy is cheap to stop and cheap to roll back.",{"type":51,"tag":82,"props":420,"children":422},{"id":421},"output-contract",[423],{"type":56,"value":424},"Output Contract",{"type":51,"tag":59,"props":426,"children":427},{},[428],{"type":56,"value":429},"Return these sections:",{"type":51,"tag":100,"props":431,"children":432},{},[433,444,455,466,477,488],{"type":51,"tag":104,"props":434,"children":435},{},[436,442],{"type":51,"tag":65,"props":437,"children":439},{"className":438},[],[440],{"type":56,"value":441},"Artifact strategy",{"type":56,"value":443},": how the service is built and packaged.",{"type":51,"tag":104,"props":445,"children":446},{},[447,453],{"type":51,"tag":65,"props":448,"children":450},{"className":449},[],[451],{"type":56,"value":452},"CI plan",{"type":56,"value":454},": stages, caches, gates, and artifact publication.",{"type":51,"tag":104,"props":456,"children":457},{},[458,464],{"type":51,"tag":65,"props":459,"children":461},{"className":460},[],[462],{"type":56,"value":463},"Container plan",{"type":56,"value":465},": image build strategy, hardening, and runtime assumptions.",{"type":51,"tag":104,"props":467,"children":468},{},[469,475],{"type":51,"tag":65,"props":470,"children":472},{"className":471},[],[473],{"type":56,"value":474},"Deployment plan",{"type":56,"value":476},": probe design, rollout strategy, config injection, and migration coordination.",{"type":51,"tag":104,"props":478,"children":479},{},[480,486],{"type":51,"tag":65,"props":481,"children":483},{"className":482},[],[484],{"type":56,"value":485},"Operational risks",{"type":56,"value":487},": what could go wrong during build or deploy.",{"type":51,"tag":104,"props":489,"children":490},{},[491,497],{"type":51,"tag":65,"props":492,"children":494},{"className":493},[],[495],{"type":56,"value":496},"Verification",{"type":56,"value":498},": the checks that prove the pipeline is reproducible and the rollout is safe.",{"type":51,"tag":82,"props":500,"children":502},{"id":501},"guardrails",[503],{"type":56,"value":504},"Guardrails",{"type":51,"tag":100,"props":506,"children":507},{},[508,513,518,523,528],{"type":51,"tag":104,"props":509,"children":510},{},[511],{"type":56,"value":512},"Do not use floating production image tags.",{"type":51,"tag":104,"props":514,"children":515},{},[516],{"type":56,"value":517},"Do not run as root without a strong reason.",{"type":51,"tag":104,"props":519,"children":520},{},[521],{"type":56,"value":522},"Do not assume the same Docker or CPU environment locally and in CI unless proven.",{"type":51,"tag":104,"props":524,"children":525},{},[526],{"type":56,"value":527},"Do not couple schema migration execution to app boot casually.",{"type":51,"tag":104,"props":529,"children":530},{},[531],{"type":56,"value":532},"Do not optimize image size at the expense of runtime correctness or operability.",{"type":51,"tag":82,"props":534,"children":536},{"id":535},"quality-bar",[537],{"type":56,"value":538},"Quality Bar",{"type":51,"tag":59,"props":540,"children":541},{},[542],{"type":56,"value":543},"A good run of this skill gives the team a build and deployment path that is repeatable, observable, and rollback-aware.\nA bad run outputs a fashionable Dockerfile and CI YAML that still leave runtime drift and deployment risk unresolved.",{"items":545,"total":674},[546,562,571,580,591,601,614,623,632,642,651,664],{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":559,"repoUrl":560,"updatedAt":561},"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},[552,555,558],{"name":553,"slug":554,"type":15},"Architecture","architecture",{"name":556,"slug":557,"type":15},"Configuration","configuration",{"name":26,"slug":27,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":563,"name":563,"fn":564,"description":565,"org":566,"tags":567,"stars":559,"repoUrl":560,"updatedAt":570},"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},[568,569],{"name":553,"slug":554,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:04:48.066901",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":559,"repoUrl":560,"updatedAt":579},"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},[577,578],{"name":553,"slug":554,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:45:21.757084",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":559,"repoUrl":560,"updatedAt":590},"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},[586,587],{"name":553,"slug":554,"type":15},{"name":588,"slug":589,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":592,"name":592,"fn":593,"description":594,"org":595,"tags":596,"stars":559,"repoUrl":560,"updatedAt":600},"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},[597],{"name":598,"slug":599,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":602,"name":602,"fn":603,"description":604,"org":605,"tags":606,"stars":559,"repoUrl":560,"updatedAt":613},"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},[607,610],{"name":608,"slug":609,"type":15},"Design","design",{"name":611,"slug":612,"type":15},"UI Components","ui-components","2026-07-23T05:41:56.638151",{"slug":615,"name":615,"fn":616,"description":617,"org":618,"tags":619,"stars":559,"repoUrl":560,"updatedAt":622},"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},[620,621],{"name":26,"slug":27,"type":15},{"name":611,"slug":612,"type":15},"2026-07-23T05:41:49.666535",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":559,"repoUrl":560,"updatedAt":631},"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},[629,630],{"name":553,"slug":554,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:44:59.507855",{"slug":633,"name":633,"fn":634,"description":635,"org":636,"tags":637,"stars":559,"repoUrl":560,"updatedAt":641},"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},[638,639,640],{"name":553,"slug":554,"type":15},{"name":588,"slug":589,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:06:58.042999",{"slug":643,"name":643,"fn":644,"description":645,"org":646,"tags":647,"stars":559,"repoUrl":560,"updatedAt":650},"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},[648,649],{"name":553,"slug":554,"type":15},{"name":26,"slug":27,"type":15},"2026-07-23T05:41:48.692899",{"slug":652,"name":652,"fn":653,"description":654,"org":655,"tags":656,"stars":559,"repoUrl":560,"updatedAt":663},"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},[657,660],{"name":658,"slug":659,"type":15},"Debugging","debugging",{"name":661,"slug":662,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":665,"name":665,"fn":666,"description":667,"org":668,"tags":669,"stars":559,"repoUrl":560,"updatedAt":673},"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},[670],{"name":671,"slug":672,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188,{"items":676,"total":780},[677,696,711,725,740,749,766],{"slug":678,"name":678,"fn":679,"description":680,"org":681,"tags":682,"stars":31,"repoUrl":32,"updatedAt":695},"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},[683,686,689,692],{"name":684,"slug":685,"type":15},"Creative","creative",{"name":687,"slug":688,"type":15},"Generative Art","generative-art",{"name":690,"slug":691,"type":15},"Graphics","graphics",{"name":693,"slug":694,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":697,"name":697,"fn":698,"description":699,"org":700,"tags":701,"stars":31,"repoUrl":32,"updatedAt":710},"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},[702,705,706,707],{"name":703,"slug":704,"type":15},"Best Practices","best-practices",{"name":26,"slug":27,"type":15},{"name":693,"slug":694,"type":15},{"name":708,"slug":709,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":31,"repoUrl":32,"updatedAt":724},"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},[717,720,721],{"name":718,"slug":719,"type":15},"Branding","branding",{"name":608,"slug":609,"type":15},{"name":722,"slug":723,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":726,"name":726,"fn":727,"description":728,"org":729,"tags":730,"stars":31,"repoUrl":32,"updatedAt":739},"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},[731,732,733,736],{"name":684,"slug":685,"type":15},{"name":608,"slug":609,"type":15},{"name":734,"slug":735,"type":15},"Images","images",{"name":737,"slug":738,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":4,"name":4,"fn":5,"description":6,"org":741,"tags":742,"stars":31,"repoUrl":32,"updatedAt":33},{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},[743,744,745,746,747,748],{"name":29,"slug":30,"type":15},{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},{"name":26,"slug":27,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},{"slug":750,"name":750,"fn":751,"description":752,"org":753,"tags":754,"stars":31,"repoUrl":32,"updatedAt":765},"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},[755,758,761,764],{"name":756,"slug":757,"type":15},"Cloudflare","cloudflare",{"name":759,"slug":760,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":762,"slug":763,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":23,"slug":24,"type":15},"2026-07-17T06:04:42.853896",{"slug":767,"name":767,"fn":768,"description":769,"org":770,"tags":771,"stars":31,"repoUrl":32,"updatedAt":779},"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},[772,775,778],{"name":773,"slug":774,"type":15},"Automation","automation",{"name":776,"slug":777,"type":15},"Desktop","desktop",{"name":611,"slug":612,"type":15},"2026-07-13T06:40:38.798626",128]