[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-observability-integrator":3,"mdc-wciegp-key":39,"related-repo-jetbrains-observability-integrator":523,"related-org-jetbrains-observability-integrator":643},{"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},"observability-integrator","design observability for Kotlin and Spring services","Design actionable observability for Kotlin plus Spring services across logs, metrics, tracing, and health endpoints. Use when instrumenting a service, improving incident diagnosis, defining SLO-driven metrics and alerts, adding trace propagation, controlling metric-cardinality cost, or ensuring async and coroutine flows remain observable 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},"Monitoring","monitoring",{"name":23,"slug":24,"type":15},"Spring","spring",{"name":26,"slug":27,"type":15},"Engineering","engineering",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:38.985804",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\u002Fobservability-integrator","---\nname: observability-integrator\ndescription: Design actionable observability for Kotlin plus Spring services across logs, metrics, tracing, and health endpoints. Use when instrumenting a service, improving incident diagnosis, defining SLO-driven metrics and alerts, adding trace propagation, controlling metric-cardinality cost, or ensuring async and coroutine flows remain observable in production.\nmetadata:\n  short-description: \"Design metrics, logs, and tracing well\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fobservability-integrator\n---\n\n# Observability Integrator\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-17`).\n\n## Mission\n\nMake the service explain its own behavior under normal load and under failure.\nInstrument for operational questions and decisions, not for vanity dashboards.\n\n## Read First\n\n- Business-critical user journeys and SLO or SLA targets.\n- Existing metrics, logs, traces, and actuator exposure.\n- Platform stack: Prometheus, Grafana, OpenTelemetry, ELK, Loki, vendor APM, or mixed.\n- Service topology, downstream dependencies, async boundaries, and coroutine usage.\n- Existing runbooks or alerting gaps.\n\n## Design Sequence\n\n1. Define the most important operational questions:\n   - is the service healthy\n   - which journey is slow\n   - which dependency is failing\n   - where saturation is growing\n2. Instrument the critical path before the nice-to-have path.\n3. Add metrics, traces, and logs that answer those questions together.\n4. Add health indicators and alerts with clear actionability.\n5. Re-check cardinality, PII, and exposure risk.\n\n## Metrics Rules\n\n- Prefer metrics tied to user journeys, dependencies, pool saturation, queue depth, and retry behavior.\n- Choose labels with a cardinality budget in mind.\n- Favor histogram or timer metrics where latency distributions matter.\n- Separate success, client error, server error, and dependency failure semantics clearly.\n- Include outcome metrics for retries, circuit breakers, cache behavior, and scheduler work when they affect operations.\n\n## Logging Rules\n\n- Use structured logs with stable field names.\n- Include correlation identifiers such as trace id or request id when the platform supports them consistently.\n- Log business-relevant events at service boundaries and failure points, not every line of code.\n- Redact or avoid PII, secrets, tokens, and credentials by policy, not by luck.\n- Prefer stable event names or codes over prose-only log statements when operations depend on searchability.\n\n## Tracing And Health Rules\n\n- Propagate trace context across HTTP, messaging, async execution, and coroutine boundaries.\n- Sample traces deliberately. Full sampling is not always affordable or necessary.\n- Distinguish liveness, readiness, and startup health semantics.\n- Keep actuator exposure minimal and authenticated where needed.\n- Include dependency health only when the signal is actionable and does not create cascading false alarms.\n\n## Advanced Observability Traps\n\n- High-cardinality labels can make a metric unusable and expensive at the same time.\n- Trace propagation may silently fail across executors, coroutines, or listeners even when HTTP tracing looks fine.\n- Logs without stable correlation are often worse than fewer logs with consistent context.\n- A metric that never drives an alert, dashboard, or investigation path is probably noise.\n- Readiness that depends on every optional downstream can create self-inflicted outages.\n- Health endpoints that expose secrets or internal topology are security risks, not observability wins.\n- Poor sampling decisions can hide the exact slow or failing traces operators care about.\n\n## SLO And Cost Nuances\n\n- RED and USE perspectives complement each other. User-facing latency and error metrics do not replace resource saturation visibility, and vice versa.\n- Burn-rate alerting is often more actionable than static threshold alerting for SLO-backed services.\n- Histogram bucket choice affects both storage cost and usefulness. Buckets should reflect user-facing latency objectives, not library defaults.\n- Exemplars or trace links can shorten incident diagnosis dramatically when supported by the platform.\n- Metric names and labels become quasi-APIs for operators. Renaming them casually creates observability drift across dashboards and alerts.\n- Observability cost is part of the design. Sampling, retention, and cardinality are architectural choices, not cleanup work for later.\n\n## Expert Heuristics\n\n- Instrument the path that paged someone last time before instrumenting the path that is merely interesting.\n- Prefer a smaller set of trusted dashboards and alerts over a broad telemetry surface nobody uses.\n- If correlation breaks across async boundaries, fix that before adding more log lines.\n- Good observability makes rollback, mitigation, and capacity decisions faster. Favor signals that support those decisions directly.\n\n## Output Contract\n\nReturn these sections:\n\n- `Operational questions`: what the instrumentation must answer.\n- `Metrics plan`: the key metrics and label strategy.\n- `Logging plan`: structure, correlation, and redaction rules.\n- `Tracing plan`: propagation points and sampling guidance.\n- `Health and alerting`: readiness, liveness, startup, and actionable alerts.\n- `Minimal implementation plan`: the smallest set of instrumentation changes that materially improves operability.\n\n## Guardrails\n\n- Do not instrument everything.\n- Do not expose actuator or debug endpoints casually.\n- Do not emit sensitive data in logs or traces.\n- Do not add cardinality-heavy labels such as raw user ids, full URLs, or free-form exception messages.\n- Do not create alerts with no obvious operator action.\n\n## Quality Bar\n\nA good run of this skill gives operators clear signals, low-noise alerts, and fast incident localization.\nA bad run produces a large telemetry bill, noisy dashboards, and no practical improvement in diagnosis.\n",{"data":40,"body":44},{"name":4,"description":6,"metadata":41},{"short-description":42,"author":17,"source":43},"Design metrics, logs, and tracing well","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fobservability-integrator",{"type":45,"children":46},"root",[47,55,78,85,90,96,126,132,184,190,218,224,252,258,286,292,330,336,369,375,398,404,409,478,484,512,518],{"type":48,"tag":49,"props":50,"children":51},"element","h1",{"id":4},[52],{"type":53,"value":54},"text","Observability Integrator",{"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-17",{"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 the service explain its own behavior under normal load and under failure.\nInstrument for operational questions and decisions, not for vanity dashboards.",{"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},"Business-critical user journeys and SLO or SLA targets.",{"type":48,"tag":101,"props":107,"children":108},{},[109],{"type":53,"value":110},"Existing metrics, logs, traces, and actuator exposure.",{"type":48,"tag":101,"props":112,"children":113},{},[114],{"type":53,"value":115},"Platform stack: Prometheus, Grafana, OpenTelemetry, ELK, Loki, vendor APM, or mixed.",{"type":48,"tag":101,"props":117,"children":118},{},[119],{"type":53,"value":120},"Service topology, downstream dependencies, async boundaries, and coroutine usage.",{"type":48,"tag":101,"props":122,"children":123},{},[124],{"type":53,"value":125},"Existing runbooks or alerting gaps.",{"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,164,169,174,179],{"type":48,"tag":101,"props":137,"children":138},{},[139,141],{"type":53,"value":140},"Define the most important operational questions:\n",{"type":48,"tag":97,"props":142,"children":143},{},[144,149,154,159],{"type":48,"tag":101,"props":145,"children":146},{},[147],{"type":53,"value":148},"is the service healthy",{"type":48,"tag":101,"props":150,"children":151},{},[152],{"type":53,"value":153},"which journey is slow",{"type":48,"tag":101,"props":155,"children":156},{},[157],{"type":53,"value":158},"which dependency is failing",{"type":48,"tag":101,"props":160,"children":161},{},[162],{"type":53,"value":163},"where saturation is growing",{"type":48,"tag":101,"props":165,"children":166},{},[167],{"type":53,"value":168},"Instrument the critical path before the nice-to-have path.",{"type":48,"tag":101,"props":170,"children":171},{},[172],{"type":53,"value":173},"Add metrics, traces, and logs that answer those questions together.",{"type":48,"tag":101,"props":175,"children":176},{},[177],{"type":53,"value":178},"Add health indicators and alerts with clear actionability.",{"type":48,"tag":101,"props":180,"children":181},{},[182],{"type":53,"value":183},"Re-check cardinality, PII, and exposure risk.",{"type":48,"tag":79,"props":185,"children":187},{"id":186},"metrics-rules",[188],{"type":53,"value":189},"Metrics Rules",{"type":48,"tag":97,"props":191,"children":192},{},[193,198,203,208,213],{"type":48,"tag":101,"props":194,"children":195},{},[196],{"type":53,"value":197},"Prefer metrics tied to user journeys, dependencies, pool saturation, queue depth, and retry behavior.",{"type":48,"tag":101,"props":199,"children":200},{},[201],{"type":53,"value":202},"Choose labels with a cardinality budget in mind.",{"type":48,"tag":101,"props":204,"children":205},{},[206],{"type":53,"value":207},"Favor histogram or timer metrics where latency distributions matter.",{"type":48,"tag":101,"props":209,"children":210},{},[211],{"type":53,"value":212},"Separate success, client error, server error, and dependency failure semantics clearly.",{"type":48,"tag":101,"props":214,"children":215},{},[216],{"type":53,"value":217},"Include outcome metrics for retries, circuit breakers, cache behavior, and scheduler work when they affect operations.",{"type":48,"tag":79,"props":219,"children":221},{"id":220},"logging-rules",[222],{"type":53,"value":223},"Logging Rules",{"type":48,"tag":97,"props":225,"children":226},{},[227,232,237,242,247],{"type":48,"tag":101,"props":228,"children":229},{},[230],{"type":53,"value":231},"Use structured logs with stable field names.",{"type":48,"tag":101,"props":233,"children":234},{},[235],{"type":53,"value":236},"Include correlation identifiers such as trace id or request id when the platform supports them consistently.",{"type":48,"tag":101,"props":238,"children":239},{},[240],{"type":53,"value":241},"Log business-relevant events at service boundaries and failure points, not every line of code.",{"type":48,"tag":101,"props":243,"children":244},{},[245],{"type":53,"value":246},"Redact or avoid PII, secrets, tokens, and credentials by policy, not by luck.",{"type":48,"tag":101,"props":248,"children":249},{},[250],{"type":53,"value":251},"Prefer stable event names or codes over prose-only log statements when operations depend on searchability.",{"type":48,"tag":79,"props":253,"children":255},{"id":254},"tracing-and-health-rules",[256],{"type":53,"value":257},"Tracing And Health Rules",{"type":48,"tag":97,"props":259,"children":260},{},[261,266,271,276,281],{"type":48,"tag":101,"props":262,"children":263},{},[264],{"type":53,"value":265},"Propagate trace context across HTTP, messaging, async execution, and coroutine boundaries.",{"type":48,"tag":101,"props":267,"children":268},{},[269],{"type":53,"value":270},"Sample traces deliberately. Full sampling is not always affordable or necessary.",{"type":48,"tag":101,"props":272,"children":273},{},[274],{"type":53,"value":275},"Distinguish liveness, readiness, and startup health semantics.",{"type":48,"tag":101,"props":277,"children":278},{},[279],{"type":53,"value":280},"Keep actuator exposure minimal and authenticated where needed.",{"type":48,"tag":101,"props":282,"children":283},{},[284],{"type":53,"value":285},"Include dependency health only when the signal is actionable and does not create cascading false alarms.",{"type":48,"tag":79,"props":287,"children":289},{"id":288},"advanced-observability-traps",[290],{"type":53,"value":291},"Advanced Observability Traps",{"type":48,"tag":97,"props":293,"children":294},{},[295,300,305,310,315,320,325],{"type":48,"tag":101,"props":296,"children":297},{},[298],{"type":53,"value":299},"High-cardinality labels can make a metric unusable and expensive at the same time.",{"type":48,"tag":101,"props":301,"children":302},{},[303],{"type":53,"value":304},"Trace propagation may silently fail across executors, coroutines, or listeners even when HTTP tracing looks fine.",{"type":48,"tag":101,"props":306,"children":307},{},[308],{"type":53,"value":309},"Logs without stable correlation are often worse than fewer logs with consistent context.",{"type":48,"tag":101,"props":311,"children":312},{},[313],{"type":53,"value":314},"A metric that never drives an alert, dashboard, or investigation path is probably noise.",{"type":48,"tag":101,"props":316,"children":317},{},[318],{"type":53,"value":319},"Readiness that depends on every optional downstream can create self-inflicted outages.",{"type":48,"tag":101,"props":321,"children":322},{},[323],{"type":53,"value":324},"Health endpoints that expose secrets or internal topology are security risks, not observability wins.",{"type":48,"tag":101,"props":326,"children":327},{},[328],{"type":53,"value":329},"Poor sampling decisions can hide the exact slow or failing traces operators care about.",{"type":48,"tag":79,"props":331,"children":333},{"id":332},"slo-and-cost-nuances",[334],{"type":53,"value":335},"SLO And Cost Nuances",{"type":48,"tag":97,"props":337,"children":338},{},[339,344,349,354,359,364],{"type":48,"tag":101,"props":340,"children":341},{},[342],{"type":53,"value":343},"RED and USE perspectives complement each other. User-facing latency and error metrics do not replace resource saturation visibility, and vice versa.",{"type":48,"tag":101,"props":345,"children":346},{},[347],{"type":53,"value":348},"Burn-rate alerting is often more actionable than static threshold alerting for SLO-backed services.",{"type":48,"tag":101,"props":350,"children":351},{},[352],{"type":53,"value":353},"Histogram bucket choice affects both storage cost and usefulness. Buckets should reflect user-facing latency objectives, not library defaults.",{"type":48,"tag":101,"props":355,"children":356},{},[357],{"type":53,"value":358},"Exemplars or trace links can shorten incident diagnosis dramatically when supported by the platform.",{"type":48,"tag":101,"props":360,"children":361},{},[362],{"type":53,"value":363},"Metric names and labels become quasi-APIs for operators. Renaming them casually creates observability drift across dashboards and alerts.",{"type":48,"tag":101,"props":365,"children":366},{},[367],{"type":53,"value":368},"Observability cost is part of the design. Sampling, retention, and cardinality are architectural choices, not cleanup work for later.",{"type":48,"tag":79,"props":370,"children":372},{"id":371},"expert-heuristics",[373],{"type":53,"value":374},"Expert Heuristics",{"type":48,"tag":97,"props":376,"children":377},{},[378,383,388,393],{"type":48,"tag":101,"props":379,"children":380},{},[381],{"type":53,"value":382},"Instrument the path that paged someone last time before instrumenting the path that is merely interesting.",{"type":48,"tag":101,"props":384,"children":385},{},[386],{"type":53,"value":387},"Prefer a smaller set of trusted dashboards and alerts over a broad telemetry surface nobody uses.",{"type":48,"tag":101,"props":389,"children":390},{},[391],{"type":53,"value":392},"If correlation breaks across async boundaries, fix that before adding more log lines.",{"type":48,"tag":101,"props":394,"children":395},{},[396],{"type":53,"value":397},"Good observability makes rollback, mitigation, and capacity decisions faster. Favor signals that support those decisions directly.",{"type":48,"tag":79,"props":399,"children":401},{"id":400},"output-contract",[402],{"type":53,"value":403},"Output Contract",{"type":48,"tag":56,"props":405,"children":406},{},[407],{"type":53,"value":408},"Return these sections:",{"type":48,"tag":97,"props":410,"children":411},{},[412,423,434,445,456,467],{"type":48,"tag":101,"props":413,"children":414},{},[415,421],{"type":48,"tag":62,"props":416,"children":418},{"className":417},[],[419],{"type":53,"value":420},"Operational questions",{"type":53,"value":422},": what the instrumentation must answer.",{"type":48,"tag":101,"props":424,"children":425},{},[426,432],{"type":48,"tag":62,"props":427,"children":429},{"className":428},[],[430],{"type":53,"value":431},"Metrics plan",{"type":53,"value":433},": the key metrics and label strategy.",{"type":48,"tag":101,"props":435,"children":436},{},[437,443],{"type":48,"tag":62,"props":438,"children":440},{"className":439},[],[441],{"type":53,"value":442},"Logging plan",{"type":53,"value":444},": structure, correlation, and redaction rules.",{"type":48,"tag":101,"props":446,"children":447},{},[448,454],{"type":48,"tag":62,"props":449,"children":451},{"className":450},[],[452],{"type":53,"value":453},"Tracing plan",{"type":53,"value":455},": propagation points and sampling guidance.",{"type":48,"tag":101,"props":457,"children":458},{},[459,465],{"type":48,"tag":62,"props":460,"children":462},{"className":461},[],[463],{"type":53,"value":464},"Health and alerting",{"type":53,"value":466},": readiness, liveness, startup, and actionable alerts.",{"type":48,"tag":101,"props":468,"children":469},{},[470,476],{"type":48,"tag":62,"props":471,"children":473},{"className":472},[],[474],{"type":53,"value":475},"Minimal implementation plan",{"type":53,"value":477},": the smallest set of instrumentation changes that materially improves operability.",{"type":48,"tag":79,"props":479,"children":481},{"id":480},"guardrails",[482],{"type":53,"value":483},"Guardrails",{"type":48,"tag":97,"props":485,"children":486},{},[487,492,497,502,507],{"type":48,"tag":101,"props":488,"children":489},{},[490],{"type":53,"value":491},"Do not instrument everything.",{"type":48,"tag":101,"props":493,"children":494},{},[495],{"type":53,"value":496},"Do not expose actuator or debug endpoints casually.",{"type":48,"tag":101,"props":498,"children":499},{},[500],{"type":53,"value":501},"Do not emit sensitive data in logs or traces.",{"type":48,"tag":101,"props":503,"children":504},{},[505],{"type":53,"value":506},"Do not add cardinality-heavy labels such as raw user ids, full URLs, or free-form exception messages.",{"type":48,"tag":101,"props":508,"children":509},{},[510],{"type":53,"value":511},"Do not create alerts with no obvious operator action.",{"type":48,"tag":79,"props":513,"children":515},{"id":514},"quality-bar",[516],{"type":53,"value":517},"Quality Bar",{"type":48,"tag":56,"props":519,"children":520},{},[521],{"type":53,"value":522},"A good run of this skill gives operators clear signals, low-noise alerts, and fast incident localization.\nA bad run produces a large telemetry bill, noisy dashboards, and no practical improvement in diagnosis.",{"items":524,"total":642},[525,544,559,575,590,609,626],{"slug":526,"name":526,"fn":527,"description":528,"org":529,"tags":530,"stars":28,"repoUrl":29,"updatedAt":543},"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},[531,534,537,540],{"name":532,"slug":533,"type":15},"Creative","creative",{"name":535,"slug":536,"type":15},"Generative Art","generative-art",{"name":538,"slug":539,"type":15},"Graphics","graphics",{"name":541,"slug":542,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":545,"name":545,"fn":546,"description":547,"org":548,"tags":549,"stars":28,"repoUrl":29,"updatedAt":558},"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},[550,553,554,555],{"name":551,"slug":552,"type":15},"Best Practices","best-practices",{"name":26,"slug":27,"type":15},{"name":541,"slug":542,"type":15},{"name":556,"slug":557,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":560,"name":560,"fn":561,"description":562,"org":563,"tags":564,"stars":28,"repoUrl":29,"updatedAt":574},"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},[565,568,571],{"name":566,"slug":567,"type":15},"Branding","branding",{"name":569,"slug":570,"type":15},"Design","design",{"name":572,"slug":573,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":576,"name":576,"fn":577,"description":578,"org":579,"tags":580,"stars":28,"repoUrl":29,"updatedAt":589},"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},[581,582,583,586],{"name":532,"slug":533,"type":15},{"name":569,"slug":570,"type":15},{"name":584,"slug":585,"type":15},"Images","images",{"name":587,"slug":588,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":591,"name":591,"fn":592,"description":593,"org":594,"tags":595,"stars":28,"repoUrl":29,"updatedAt":608},"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},[596,599,602,605,606,607],{"name":597,"slug":598,"type":15},"CI\u002FCD","ci-cd",{"name":600,"slug":601,"type":15},"Containers","containers",{"name":603,"slug":604,"type":15},"Deployment","deployment",{"name":26,"slug":27,"type":15},{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:41:47.83899",{"slug":610,"name":610,"fn":611,"description":612,"org":613,"tags":614,"stars":28,"repoUrl":29,"updatedAt":625},"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},[615,618,621,624],{"name":616,"slug":617,"type":15},"Cloudflare","cloudflare",{"name":619,"slug":620,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":622,"slug":623,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":603,"slug":604,"type":15},"2026-07-17T06:04:42.853896",{"slug":627,"name":627,"fn":628,"description":629,"org":630,"tags":631,"stars":28,"repoUrl":29,"updatedAt":641},"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},[632,635,638],{"name":633,"slug":634,"type":15},"Automation","automation",{"name":636,"slug":637,"type":15},"Desktop","desktop",{"name":639,"slug":640,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":644,"total":769},[645,661,670,679,690,700,709,718,727,737,746,759],{"slug":646,"name":646,"fn":647,"description":648,"org":649,"tags":650,"stars":658,"repoUrl":659,"updatedAt":660},"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},[651,654,657],{"name":652,"slug":653,"type":15},"Architecture","architecture",{"name":655,"slug":656,"type":15},"Configuration","configuration",{"name":26,"slug":27,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":662,"name":662,"fn":663,"description":664,"org":665,"tags":666,"stars":658,"repoUrl":659,"updatedAt":669},"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},[667,668],{"name":652,"slug":653,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:04:48.066901",{"slug":671,"name":671,"fn":672,"description":673,"org":674,"tags":675,"stars":658,"repoUrl":659,"updatedAt":678},"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},[676,677],{"name":652,"slug":653,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:45:21.757084",{"slug":680,"name":680,"fn":681,"description":682,"org":683,"tags":684,"stars":658,"repoUrl":659,"updatedAt":689},"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},[685,686],{"name":652,"slug":653,"type":15},{"name":687,"slug":688,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":658,"repoUrl":659,"updatedAt":699},"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},[696],{"name":697,"slug":698,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":701,"name":701,"fn":702,"description":703,"org":704,"tags":705,"stars":658,"repoUrl":659,"updatedAt":708},"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},[706,707],{"name":569,"slug":570,"type":15},{"name":639,"slug":640,"type":15},"2026-07-23T05:41:56.638151",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":658,"repoUrl":659,"updatedAt":717},"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},[715,716],{"name":26,"slug":27,"type":15},{"name":639,"slug":640,"type":15},"2026-07-23T05:41:49.666535",{"slug":719,"name":719,"fn":720,"description":721,"org":722,"tags":723,"stars":658,"repoUrl":659,"updatedAt":726},"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},[724,725],{"name":652,"slug":653,"type":15},{"name":26,"slug":27,"type":15},"2026-07-13T06:44:59.507855",{"slug":728,"name":728,"fn":729,"description":730,"org":731,"tags":732,"stars":658,"repoUrl":659,"updatedAt":736},"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},[733,734,735],{"name":652,"slug":653,"type":15},{"name":687,"slug":688,"type":15},{"name":26,"slug":27,"type":15},"2026-07-17T06:06:58.042999",{"slug":738,"name":738,"fn":739,"description":740,"org":741,"tags":742,"stars":658,"repoUrl":659,"updatedAt":745},"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},[743,744],{"name":652,"slug":653,"type":15},{"name":26,"slug":27,"type":15},"2026-07-23T05:41:48.692899",{"slug":747,"name":747,"fn":748,"description":749,"org":750,"tags":751,"stars":658,"repoUrl":659,"updatedAt":758},"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},[752,755],{"name":753,"slug":754,"type":15},"Debugging","debugging",{"name":756,"slug":757,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":760,"name":760,"fn":761,"description":762,"org":763,"tags":764,"stars":658,"repoUrl":659,"updatedAt":768},"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},[765],{"name":766,"slug":767,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]