[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-integration-resilience-engineer":3,"mdc--koohnx-key":39,"related-repo-jetbrains-integration-resilience-engineer":518,"related-org-jetbrains-integration-resilience-engineer":638},{"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},"integration-resilience-engineer","design resilient integrations for Spring services","Design resilient HTTP, messaging, and scheduled integrations for Kotlin plus Spring services with explicit timeout budgets, retries, idempotency, circuit breakers, DLQ behavior, and failure observability. Use when integrating with unstable external systems, designing retry logic, handling duplicate delivery, preventing thundering herds, or making message-driven and scheduled workflows safe in production.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":9},"jetbrains","JetBrains","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fjetbrains.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":18,"type":15},"Kotlin","kotlin",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Engineering","engineering",{"name":26,"slug":27,"type":15},"API Development","api-development",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:50.158424",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\u002Fintegration-resilience-engineer","---\nname: integration-resilience-engineer\ndescription: Design resilient HTTP, messaging, and scheduled integrations for Kotlin plus Spring services with explicit timeout budgets, retries, idempotency, circuit breakers, DLQ behavior, and failure observability. Use when integrating with unstable external systems, designing retry logic, handling duplicate delivery, preventing thundering herds, or making message-driven and scheduled workflows safe in production.\nmetadata:\n  short-description: \"Harden clients, retries, and messaging\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fintegration-resilience-engineer\n---\n\n# Integration Resilience Engineer\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-12`).\n\n## Mission\n\nMake integrations behave predictably under partial failure, timeouts, retries, and duplicate delivery.\nTreat every remote boundary as unreliable and every retry as a potential multiplier of load.\n\n## Read First\n\n- External API or messaging contract, including status codes or message schema.\n- SLA, timeout budget, rate-limit rules, and idempotency guarantees.\n- Current client configuration, retry logic, circuit breaker settings, and scheduling configuration.\n- Business criticality of the operation and acceptable degradation behavior.\n- Existing observability around request outcome, retry count, queue depth, and DLQ.\n\n## Design Sequence\n\n1. Classify the operation:\n   - read-only or state-changing\n   - idempotent or non-idempotent\n   - synchronous user path or asynchronous background path\n2. Set timeout budgets from the caller's SLO backward.\n3. Decide which failures are retryable and which are terminal.\n4. Decide where deduplication or idempotency must be enforced.\n5. Add circuit breaking, bulkheading, or rate limiting where failure amplification is plausible.\n6. Add metrics, tracing, and structured outcome logging.\n\n## HTTP Client Rules\n\n- Set connect and response timeouts explicitly.\n- Retry only when the operation is safe to replay or explicitly idempotent.\n- Use exponential backoff with jitter, not fixed-interval retries.\n- Respect `429`, `Retry-After`, and dependency-specific throttling semantics.\n- Distinguish timeout before request reached the server from timeout after side effects may already have happened.\n- Map downstream errors into local semantics deliberately. Do not leak raw remote failures by accident.\n\n## Messaging And Scheduling Rules\n\n- Treat consumers as at-least-once unless a stronger guarantee is proven end to end.\n- Design deduplication with stable keys and durable storage when duplicate delivery matters.\n- Use DLQ or poison-message handling instead of infinite redelivery loops.\n- Be explicit about ordering guarantees and partition-key strategy.\n- For scheduled jobs, prevent overlap with distributed locking when multiple nodes can run the same task.\n- Account for clock skew, long-running jobs, and partial completion when scheduling recurring work.\n\n## Advanced Failure Modes\n\n- Retries at multiple layers multiply explosively. One client retry policy plus platform retry plus queue retry can create storms.\n- Circuit breakers without sensible fallback or operator visibility often only change the failure shape.\n- Fallback data can become a stale correctness problem, not merely a degraded UX.\n- A timeout on a state-changing call may leave the caller uncertain whether the remote side succeeded. This is an idempotency design problem, not just a timeout problem.\n- DLQ without replay discipline creates permanent operational debt.\n- Exactly-once is usually a system property claim, not an individual code property. Be skeptical and precise.\n- If message schema evolution is expected, plan backward-compatible consumers before the first change arrives.\n\n## Boundary-Specific Nuances\n\n- HTTP connection pooling, DNS caching, TLS handshakes, and per-host limits can dominate latency long before business logic does. Client-level transport settings matter.\n- A `202 Accepted` plus asynchronous completion model may be safer than a synchronous state-changing call when dependency latency is unpredictable.\n- Outbox and inbox patterns solve different halves of reliability. Do not talk about one as if it covers both publish and consume idempotency.\n- Kafka rebalance behavior, consumer lag, and partition skew are part of resiliency, not only throughput tuning.\n- Schedulers need both overlap prevention and business-level idempotency. A distributed lock alone does not make the job semantically safe.\n\n## Expert Heuristics\n\n- Put a retry budget around each integration path. If retries exceed the budget, fail fast and surface the degradation clearly.\n- If a dependency is slow but not down, circuit breaking may be less useful than tight timeouts plus bulkheads.\n- If the caller cannot safely determine whether a remote write succeeded, design a reconciliation path, not only a retry policy.\n- If a queue consumer is critical, define operator behavior for DLQ replay before the first poison message appears.\n\n## Output Contract\n\nReturn these sections:\n\n- `Failure model`: what can go wrong at this boundary.\n- `Resilience policy`: timeouts, retries, circuit breaking, bulkheads, fallback, and deduplication.\n- `Idempotency rule`: how duplicate or uncertain delivery is handled.\n- `Operational signals`: which metrics, logs, traces, and alerts are required.\n- `Minimal implementation plan`: client, listener, scheduler, or config changes to make.\n- `Verification`: chaos, integration, or replay tests that prove the design.\n\n## Guardrails\n\n- Do not retry non-idempotent operations by default.\n- Do not add retries without jitter and a retry budget.\n- Do not use fallbacks that silently violate business invariants.\n- Do not leave outcome ambiguity unexplained for timed-out state changes.\n- Do not build resilience policies that operators cannot observe.\n\n## Quality Bar\n\nA good run of this skill produces an integration policy that fails in controlled, explainable ways.\nA bad run adds retries and circuit breakers everywhere while increasing duplication, latency, and operational confusion.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":17,"source":43},"Harden clients, retries, and messaging","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fintegration-resilience-engineer",{"type":45,"children":46},"root",[47,55,78,85,90,96,126,132,184,190,239,245,278,284,322,328,364,370,393,399,404,473,479,507,513],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Integration Resilience Engineer",{"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-12",{"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},"Make integrations behave predictably under partial failure, timeouts, retries, and duplicate delivery.\nTreat every remote boundary as unreliable and every retry as a potential multiplier of load.",{"type":48,"tag":79,"props":91,"children":93},{"id":92},"read-first",[94],{"type":53,"value":95},"Read First",{"type":48,"tag":97,"props":98,"children":99},"ul",{},[100,106,111,116,121],{"type":48,"tag":101,"props":102,"children":103},"li",{},[104],{"type":53,"value":105},"External API or messaging contract, including status codes or message schema.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"SLA, timeout budget, rate-limit rules, and idempotency guarantees.",{"type":48,"tag":101,"props":112,"children":113},{},[114],{"type":53,"value":115},"Current client configuration, retry logic, circuit breaker settings, and scheduling configuration.",{"type":48,"tag":101,"props":117,"children":118},{},[119],{"type":53,"value":120},"Business criticality of the operation and acceptable degradation behavior.",{"type":48,"tag":101,"props":122,"children":123},{},[124],{"type":53,"value":125},"Existing observability around request outcome, retry count, queue depth, and DLQ.",{"type":48,"tag":79,"props":127,"children":129},{"id":128},"design-sequence",[130],{"type":53,"value":131},"Design Sequence",{"type":48,"tag":133,"props":134,"children":135},"ol",{},[136,159,164,169,174,179],{"type":48,"tag":101,"props":137,"children":138},{},[139,141],{"type":53,"value":140},"Classify the operation:\n",{"type":48,"tag":97,"props":142,"children":143},{},[144,149,154],{"type":48,"tag":101,"props":145,"children":146},{},[147],{"type":53,"value":148},"read-only or state-changing",{"type":48,"tag":101,"props":150,"children":151},{},[152],{"type":53,"value":153},"idempotent or non-idempotent",{"type":48,"tag":101,"props":155,"children":156},{},[157],{"type":53,"value":158},"synchronous user path or asynchronous background path",{"type":48,"tag":101,"props":160,"children":161},{},[162],{"type":53,"value":163},"Set timeout budgets from the caller's SLO backward.",{"type":48,"tag":101,"props":165,"children":166},{},[167],{"type":53,"value":168},"Decide which failures are retryable and which are terminal.",{"type":48,"tag":101,"props":170,"children":171},{},[172],{"type":53,"value":173},"Decide where deduplication or idempotency must be enforced.",{"type":48,"tag":101,"props":175,"children":176},{},[177],{"type":53,"value":178},"Add circuit breaking, bulkheading, or rate limiting where failure amplification is plausible.",{"type":48,"tag":101,"props":180,"children":181},{},[182],{"type":53,"value":183},"Add metrics, tracing, and structured outcome logging.",{"type":48,"tag":79,"props":185,"children":187},{"id":186},"http-client-rules",[188],{"type":53,"value":189},"HTTP Client Rules",{"type":48,"tag":97,"props":191,"children":192},{},[193,198,203,208,229,234],{"type":48,"tag":101,"props":194,"children":195},{},[196],{"type":53,"value":197},"Set connect and response timeouts explicitly.",{"type":48,"tag":101,"props":199,"children":200},{},[201],{"type":53,"value":202},"Retry only when the operation is safe to replay or explicitly idempotent.",{"type":48,"tag":101,"props":204,"children":205},{},[206],{"type":53,"value":207},"Use exponential backoff with jitter, not fixed-interval retries.",{"type":48,"tag":101,"props":209,"children":210},{},[211,213,219,221,227],{"type":53,"value":212},"Respect ",{"type":48,"tag":62,"props":214,"children":216},{"className":215},[],[217],{"type":53,"value":218},"429",{"type":53,"value":220},", ",{"type":48,"tag":62,"props":222,"children":224},{"className":223},[],[225],{"type":53,"value":226},"Retry-After",{"type":53,"value":228},", and dependency-specific throttling semantics.",{"type":48,"tag":101,"props":230,"children":231},{},[232],{"type":53,"value":233},"Distinguish timeout before request reached the server from timeout after side effects may already have happened.",{"type":48,"tag":101,"props":235,"children":236},{},[237],{"type":53,"value":238},"Map downstream errors into local semantics deliberately. Do not leak raw remote failures by accident.",{"type":48,"tag":79,"props":240,"children":242},{"id":241},"messaging-and-scheduling-rules",[243],{"type":53,"value":244},"Messaging And Scheduling Rules",{"type":48,"tag":97,"props":246,"children":247},{},[248,253,258,263,268,273],{"type":48,"tag":101,"props":249,"children":250},{},[251],{"type":53,"value":252},"Treat consumers as at-least-once unless a stronger guarantee is proven end to end.",{"type":48,"tag":101,"props":254,"children":255},{},[256],{"type":53,"value":257},"Design deduplication with stable keys and durable storage when duplicate delivery matters.",{"type":48,"tag":101,"props":259,"children":260},{},[261],{"type":53,"value":262},"Use DLQ or poison-message handling instead of infinite redelivery loops.",{"type":48,"tag":101,"props":264,"children":265},{},[266],{"type":53,"value":267},"Be explicit about ordering guarantees and partition-key strategy.",{"type":48,"tag":101,"props":269,"children":270},{},[271],{"type":53,"value":272},"For scheduled jobs, prevent overlap with distributed locking when multiple nodes can run the same task.",{"type":48,"tag":101,"props":274,"children":275},{},[276],{"type":53,"value":277},"Account for clock skew, long-running jobs, and partial completion when scheduling recurring work.",{"type":48,"tag":79,"props":279,"children":281},{"id":280},"advanced-failure-modes",[282],{"type":53,"value":283},"Advanced Failure Modes",{"type":48,"tag":97,"props":285,"children":286},{},[287,292,297,302,307,312,317],{"type":48,"tag":101,"props":288,"children":289},{},[290],{"type":53,"value":291},"Retries at multiple layers multiply explosively. One client retry policy plus platform retry plus queue retry can create storms.",{"type":48,"tag":101,"props":293,"children":294},{},[295],{"type":53,"value":296},"Circuit breakers without sensible fallback or operator visibility often only change the failure shape.",{"type":48,"tag":101,"props":298,"children":299},{},[300],{"type":53,"value":301},"Fallback data can become a stale correctness problem, not merely a degraded UX.",{"type":48,"tag":101,"props":303,"children":304},{},[305],{"type":53,"value":306},"A timeout on a state-changing call may leave the caller uncertain whether the remote side succeeded. This is an idempotency design problem, not just a timeout problem.",{"type":48,"tag":101,"props":308,"children":309},{},[310],{"type":53,"value":311},"DLQ without replay discipline creates permanent operational debt.",{"type":48,"tag":101,"props":313,"children":314},{},[315],{"type":53,"value":316},"Exactly-once is usually a system property claim, not an individual code property. Be skeptical and precise.",{"type":48,"tag":101,"props":318,"children":319},{},[320],{"type":53,"value":321},"If message schema evolution is expected, plan backward-compatible consumers before the first change arrives.",{"type":48,"tag":79,"props":323,"children":325},{"id":324},"boundary-specific-nuances",[326],{"type":53,"value":327},"Boundary-Specific Nuances",{"type":48,"tag":97,"props":329,"children":330},{},[331,336,349,354,359],{"type":48,"tag":101,"props":332,"children":333},{},[334],{"type":53,"value":335},"HTTP connection pooling, DNS caching, TLS handshakes, and per-host limits can dominate latency long before business logic does. Client-level transport settings matter.",{"type":48,"tag":101,"props":337,"children":338},{},[339,341,347],{"type":53,"value":340},"A ",{"type":48,"tag":62,"props":342,"children":344},{"className":343},[],[345],{"type":53,"value":346},"202 Accepted",{"type":53,"value":348}," plus asynchronous completion model may be safer than a synchronous state-changing call when dependency latency is unpredictable.",{"type":48,"tag":101,"props":350,"children":351},{},[352],{"type":53,"value":353},"Outbox and inbox patterns solve different halves of reliability. Do not talk about one as if it covers both publish and consume idempotency.",{"type":48,"tag":101,"props":355,"children":356},{},[357],{"type":53,"value":358},"Kafka rebalance behavior, consumer lag, and partition skew are part of resiliency, not only throughput tuning.",{"type":48,"tag":101,"props":360,"children":361},{},[362],{"type":53,"value":363},"Schedulers need both overlap prevention and business-level idempotency. A distributed lock alone does not make the job semantically safe.",{"type":48,"tag":79,"props":365,"children":367},{"id":366},"expert-heuristics",[368],{"type":53,"value":369},"Expert Heuristics",{"type":48,"tag":97,"props":371,"children":372},{},[373,378,383,388],{"type":48,"tag":101,"props":374,"children":375},{},[376],{"type":53,"value":377},"Put a retry budget around each integration path. If retries exceed the budget, fail fast and surface the degradation clearly.",{"type":48,"tag":101,"props":379,"children":380},{},[381],{"type":53,"value":382},"If a dependency is slow but not down, circuit breaking may be less useful than tight timeouts plus bulkheads.",{"type":48,"tag":101,"props":384,"children":385},{},[386],{"type":53,"value":387},"If the caller cannot safely determine whether a remote write succeeded, design a reconciliation path, not only a retry policy.",{"type":48,"tag":101,"props":389,"children":390},{},[391],{"type":53,"value":392},"If a queue consumer is critical, define operator behavior for DLQ replay before the first poison message appears.",{"type":48,"tag":79,"props":394,"children":396},{"id":395},"output-contract",[397],{"type":53,"value":398},"Output Contract",{"type":48,"tag":56,"props":400,"children":401},{},[402],{"type":53,"value":403},"Return these sections:",{"type":48,"tag":97,"props":405,"children":406},{},[407,418,429,440,451,462],{"type":48,"tag":101,"props":408,"children":409},{},[410,416],{"type":48,"tag":62,"props":411,"children":413},{"className":412},[],[414],{"type":53,"value":415},"Failure model",{"type":53,"value":417},": what can go wrong at this boundary.",{"type":48,"tag":101,"props":419,"children":420},{},[421,427],{"type":48,"tag":62,"props":422,"children":424},{"className":423},[],[425],{"type":53,"value":426},"Resilience policy",{"type":53,"value":428},": timeouts, retries, circuit breaking, bulkheads, fallback, and deduplication.",{"type":48,"tag":101,"props":430,"children":431},{},[432,438],{"type":48,"tag":62,"props":433,"children":435},{"className":434},[],[436],{"type":53,"value":437},"Idempotency rule",{"type":53,"value":439},": how duplicate or uncertain delivery is handled.",{"type":48,"tag":101,"props":441,"children":442},{},[443,449],{"type":48,"tag":62,"props":444,"children":446},{"className":445},[],[447],{"type":53,"value":448},"Operational signals",{"type":53,"value":450},": which metrics, logs, traces, and alerts are required.",{"type":48,"tag":101,"props":452,"children":453},{},[454,460],{"type":48,"tag":62,"props":455,"children":457},{"className":456},[],[458],{"type":53,"value":459},"Minimal implementation plan",{"type":53,"value":461},": client, listener, scheduler, or config changes to make.",{"type":48,"tag":101,"props":463,"children":464},{},[465,471],{"type":48,"tag":62,"props":466,"children":468},{"className":467},[],[469],{"type":53,"value":470},"Verification",{"type":53,"value":472},": chaos, integration, or replay tests that prove the design.",{"type":48,"tag":79,"props":474,"children":476},{"id":475},"guardrails",[477],{"type":53,"value":478},"Guardrails",{"type":48,"tag":97,"props":480,"children":481},{},[482,487,492,497,502],{"type":48,"tag":101,"props":483,"children":484},{},[485],{"type":53,"value":486},"Do not retry non-idempotent operations by default.",{"type":48,"tag":101,"props":488,"children":489},{},[490],{"type":53,"value":491},"Do not add retries without jitter and a retry budget.",{"type":48,"tag":101,"props":493,"children":494},{},[495],{"type":53,"value":496},"Do not use fallbacks that silently violate business invariants.",{"type":48,"tag":101,"props":498,"children":499},{},[500],{"type":53,"value":501},"Do not leave outcome ambiguity unexplained for timed-out state changes.",{"type":48,"tag":101,"props":503,"children":504},{},[505],{"type":53,"value":506},"Do not build resilience policies that operators cannot observe.",{"type":48,"tag":79,"props":508,"children":510},{"id":509},"quality-bar",[511],{"type":53,"value":512},"Quality Bar",{"type":48,"tag":56,"props":514,"children":515},{},[516],{"type":53,"value":517},"A good run of this skill produces an integration policy that fails in controlled, explainable ways.\nA bad run adds retries and circuit breakers everywhere while increasing duplication, latency, and operational confusion.",{"items":519,"total":637},[520,539,554,570,585,604,621],{"slug":521,"name":521,"fn":522,"description":523,"org":524,"tags":525,"stars":28,"repoUrl":29,"updatedAt":538},"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},[526,529,532,535],{"name":527,"slug":528,"type":15},"Creative","creative",{"name":530,"slug":531,"type":15},"Generative Art","generative-art",{"name":533,"slug":534,"type":15},"Graphics","graphics",{"name":536,"slug":537,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":540,"name":540,"fn":541,"description":542,"org":543,"tags":544,"stars":28,"repoUrl":29,"updatedAt":553},"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},[545,548,549,550],{"name":546,"slug":547,"type":15},"Best Practices","best-practices",{"name":23,"slug":24,"type":15},{"name":536,"slug":537,"type":15},{"name":551,"slug":552,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":555,"name":555,"fn":556,"description":557,"org":558,"tags":559,"stars":28,"repoUrl":29,"updatedAt":569},"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},[560,563,566],{"name":561,"slug":562,"type":15},"Branding","branding",{"name":564,"slug":565,"type":15},"Design","design",{"name":567,"slug":568,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":571,"name":571,"fn":572,"description":573,"org":574,"tags":575,"stars":28,"repoUrl":29,"updatedAt":584},"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},[576,577,578,581],{"name":527,"slug":528,"type":15},{"name":564,"slug":565,"type":15},{"name":579,"slug":580,"type":15},"Images","images",{"name":582,"slug":583,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":586,"name":586,"fn":587,"description":588,"org":589,"tags":590,"stars":28,"repoUrl":29,"updatedAt":603},"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},[591,594,597,600,601,602],{"name":592,"slug":593,"type":15},"CI\u002FCD","ci-cd",{"name":595,"slug":596,"type":15},"Containers","containers",{"name":598,"slug":599,"type":15},"Deployment","deployment",{"name":23,"slug":24,"type":15},{"name":17,"slug":18,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":605,"name":605,"fn":606,"description":607,"org":608,"tags":609,"stars":28,"repoUrl":29,"updatedAt":620},"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},[610,613,616,619],{"name":611,"slug":612,"type":15},"Cloudflare","cloudflare",{"name":614,"slug":615,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":617,"slug":618,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":598,"slug":599,"type":15},"2026-07-17T06:04:42.853896",{"slug":622,"name":622,"fn":623,"description":624,"org":625,"tags":626,"stars":28,"repoUrl":29,"updatedAt":636},"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},[627,630,633],{"name":628,"slug":629,"type":15},"Automation","automation",{"name":631,"slug":632,"type":15},"Desktop","desktop",{"name":634,"slug":635,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":639,"total":764},[640,656,665,674,685,695,704,713,722,732,741,754],{"slug":641,"name":641,"fn":642,"description":643,"org":644,"tags":645,"stars":653,"repoUrl":654,"updatedAt":655},"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},[646,649,652],{"name":647,"slug":648,"type":15},"Architecture","architecture",{"name":650,"slug":651,"type":15},"Configuration","configuration",{"name":23,"slug":24,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":657,"name":657,"fn":658,"description":659,"org":660,"tags":661,"stars":653,"repoUrl":654,"updatedAt":664},"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},[662,663],{"name":647,"slug":648,"type":15},{"name":23,"slug":24,"type":15},"2026-07-17T06:04:48.066901",{"slug":666,"name":666,"fn":667,"description":668,"org":669,"tags":670,"stars":653,"repoUrl":654,"updatedAt":673},"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},[671,672],{"name":647,"slug":648,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:45:21.757084",{"slug":675,"name":675,"fn":676,"description":677,"org":678,"tags":679,"stars":653,"repoUrl":654,"updatedAt":684},"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},[680,681],{"name":647,"slug":648,"type":15},{"name":682,"slug":683,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":686,"name":686,"fn":687,"description":688,"org":689,"tags":690,"stars":653,"repoUrl":654,"updatedAt":694},"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},[691],{"name":692,"slug":693,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":696,"name":696,"fn":697,"description":698,"org":699,"tags":700,"stars":653,"repoUrl":654,"updatedAt":703},"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},[701,702],{"name":564,"slug":565,"type":15},{"name":634,"slug":635,"type":15},"2026-07-23T05:41:56.638151",{"slug":705,"name":705,"fn":706,"description":707,"org":708,"tags":709,"stars":653,"repoUrl":654,"updatedAt":712},"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},[710,711],{"name":23,"slug":24,"type":15},{"name":634,"slug":635,"type":15},"2026-07-23T05:41:49.666535",{"slug":714,"name":714,"fn":715,"description":716,"org":717,"tags":718,"stars":653,"repoUrl":654,"updatedAt":721},"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},[719,720],{"name":647,"slug":648,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:44:59.507855",{"slug":723,"name":723,"fn":724,"description":725,"org":726,"tags":727,"stars":653,"repoUrl":654,"updatedAt":731},"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},[728,729,730],{"name":647,"slug":648,"type":15},{"name":682,"slug":683,"type":15},{"name":23,"slug":24,"type":15},"2026-07-17T06:06:58.042999",{"slug":733,"name":733,"fn":734,"description":735,"org":736,"tags":737,"stars":653,"repoUrl":654,"updatedAt":740},"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},[738,739],{"name":647,"slug":648,"type":15},{"name":23,"slug":24,"type":15},"2026-07-23T05:41:48.692899",{"slug":742,"name":742,"fn":743,"description":744,"org":745,"tags":746,"stars":653,"repoUrl":654,"updatedAt":753},"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},[747,750],{"name":748,"slug":749,"type":15},"Debugging","debugging",{"name":751,"slug":752,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":755,"name":755,"fn":756,"description":757,"org":758,"tags":759,"stars":653,"repoUrl":654,"updatedAt":763},"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},[760],{"name":761,"slug":762,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]