[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-stacktrace-log-triage":3,"mdc--e3vwp-key":36,"related-repo-jetbrains-stacktrace-log-triage":514,"related-org-jetbrains-stacktrace-log-triage":636},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"stacktrace-log-triage","triage Kotlin Spring runtime failures","Diagnose Kotlin + Spring failures from stack traces, startup logs, runtime logs, and related metric anomalies, then separate root cause from wrapper exceptions and propose safe next steps. Use when the application fails to start, an endpoint crashes, logs are noisy or deeply nested, or the agent must produce both a quick mitigation and a proper long-term fix without guessing.",{"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],{"name":13,"slug":14,"type":15},"Kotlin","kotlin","tag",{"name":17,"slug":18,"type":15},"Logs","logs",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Debugging","debugging",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:09.70729",null,17,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Fstacktrace-log-triage","---\nname: stacktrace-log-triage\ndescription: Diagnose Kotlin + Spring failures from stack traces, startup logs, runtime logs, and related metric anomalies, then separate root cause from wrapper exceptions and propose safe next steps. Use when the application fails to start, an endpoint crashes, logs are noisy or deeply nested, or the agent must produce both a quick mitigation and a proper long-term fix without guessing.\nmetadata:\n  short-description: \"Diagnose Spring\u002FKotlin failures fast\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fstacktrace-log-triage\n---\n\n# Stacktrace Log Triage\n\nSource mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-15`).\n\n## Mission\n\nTurn noisy failure evidence into a ranked diagnosis with explicit confidence.\nAlways distinguish symptom, proximate cause, and true root cause.\n\n## Gather Evidence First\n\n- Read the full stack trace, not only the top frame.\n- Read the surrounding log lines before and after the first failure.\n- Capture timestamps, correlation ids, request ids, thread names, and active profiles when available.\n- Read recent relevant code or config changes if they are available.\n- Reuse repository constraints from `project-context-ingestion` when possible.\n\n## Triage Workflow\n\n1. Find the earliest meaningful failure signal.\n2. Walk the `Caused by:` chain until it stops getting more specific.\n3. Classify the incident:\n   - DI and context startup\n   - configuration binding\n   - serialization or validation\n   - SQL or migration\n   - HTTP or timeout\n   - security\n   - concurrency or locking\n   - classpath or version mismatch\n4. Separate what failed from why it failed.\n5. Rank hypotheses when evidence is incomplete.\n6. Propose a quick mitigation and a proper fix separately.\n\n## Diagnostic Rules\n\n- Treat `BeanCreationException`, `InvocationTargetException`, and similar wrappers as transport, not diagnosis.\n- Treat the first user-code frame after framework wrappers as high-signal evidence.\n- Use log chronology, not stack depth alone.\n- If the logs are truncated, say so and lower confidence.\n- Prefer an explanation grounded in the observed code path or configuration over pattern-matching from memory.\n\n## Advanced Signal Patterns\n\n- Check suppressed exceptions, root-cause logging one or two lines above the stack trace, and companion failures on adjacent threads. The most useful clue is often not in the main stack at all.\n- Distinguish hard failures from saturation patterns: connection pool exhaustion, thread pool starvation, event-loop blocking, retry storms, and deadlock retries often show up as secondary symptoms first.\n- For SQL failures, inspect vendor codes and SQL state when available. They are often more actionable than the wrapper exception type.\n- For startup failures after version or deploy changes, compare classpath and configuration drift before assuming a code bug.\n- For intermittent failures, weigh time correlation and concurrency context heavily. A race rarely leaves a clean single-thread narrative.\n- For OOM or GC-related incidents, plain stack traces are weak evidence. Thread dumps, heap symptoms, and allocation context matter more.\n- If metrics exist, correlate the first error spike with latency, pool saturation, or downstream dependency degradation rather than treating logs in isolation.\n- If the symptom appears in reactive or coroutine code, verify whether context propagation broke logging correlation before dismissing missing IDs or misleading thread names.\n\n## Expert Heuristics\n\n- The first fix after triage should reduce uncertainty as well as reduce pain. Prefer mitigations that also sharpen diagnosis.\n- If several candidate causes fit, rank them by evidence, blast radius, and reversibility of the proposed mitigation.\n- If the trace points to a framework wrapper, move outward to code and config that changed recently, then inward again through the causal chain.\n- Always state what evidence would falsify the leading hypothesis.\n\n## Output Contract\n\nReturn these sections:\n\n- `Root cause`: confirmed or most likely cause in plain language.\n- `Confidence`: confirmed, high, medium, or low.\n- `Evidence`: the log line, exception, config fact, or code path supporting the diagnosis.\n- `Hotfix`: the safest immediate containment or unblocking step.\n- `Long-term fix`: the proper code or configuration correction.\n- `Reproduction and verification`: how to reproduce, test, and monitor the fix.\n\n## Safety Rules\n\n- Label hypotheses as hypotheses.\n- Do not recommend risky schema changes, version upgrades, or broad refactors as a hotfix unless the incident truly leaves no safer option.\n- Do not claim certainty when the logs are incomplete.\n- Do not ignore alerting or monitoring implications after the fix.\n\n## Kotlin-Specific Checks\n\n- Watch for platform-type `NullPointerException`.\n- Watch for coroutine stack traces that obscure the original call path.\n- Watch for missing Kotlin compiler plugins causing runtime behavior gaps.\n- Watch for Jackson plus Kotlin constructor issues that surface as generic deserialization errors.\n\n## Quality Bar\n\nA good run of this skill gives the user a path from failure evidence to safe remediation.\nA bad run repeats the top exception, ignores the `Caused by:` chain, or offers a dangerous hotfix without explaining the risk.\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Diagnose Spring\u002FKotlin failures fast","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fstacktrace-log-triage",{"type":42,"children":43},"root",[44,52,75,82,87,93,131,137,222,228,272,278,321,327,350,356,361,430,436,459,465,496,502],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Stacktrace Log Triage",{"type":45,"tag":53,"props":54,"children":55},"p",{},[56,58,65,67,73],{"type":50,"value":57},"Source mapping: Tier 1 critical skill derived from ",{"type":45,"tag":59,"props":60,"children":62},"code",{"className":61},[],[63],{"type":50,"value":64},"Kotlin_Spring_Developer_Pipeline.md",{"type":50,"value":66}," (",{"type":45,"tag":59,"props":68,"children":70},{"className":69},[],[71],{"type":50,"value":72},"SK-15",{"type":50,"value":74},").",{"type":45,"tag":76,"props":77,"children":79},"h2",{"id":78},"mission",[80],{"type":50,"value":81},"Mission",{"type":45,"tag":53,"props":83,"children":84},{},[85],{"type":50,"value":86},"Turn noisy failure evidence into a ranked diagnosis with explicit confidence.\nAlways distinguish symptom, proximate cause, and true root cause.",{"type":45,"tag":76,"props":88,"children":90},{"id":89},"gather-evidence-first",[91],{"type":50,"value":92},"Gather Evidence First",{"type":45,"tag":94,"props":95,"children":96},"ul",{},[97,103,108,113,118],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101],{"type":50,"value":102},"Read the full stack trace, not only the top frame.",{"type":45,"tag":98,"props":104,"children":105},{},[106],{"type":50,"value":107},"Read the surrounding log lines before and after the first failure.",{"type":45,"tag":98,"props":109,"children":110},{},[111],{"type":50,"value":112},"Capture timestamps, correlation ids, request ids, thread names, and active profiles when available.",{"type":45,"tag":98,"props":114,"children":115},{},[116],{"type":50,"value":117},"Read recent relevant code or config changes if they are available.",{"type":45,"tag":98,"props":119,"children":120},{},[121,123,129],{"type":50,"value":122},"Reuse repository constraints from ",{"type":45,"tag":59,"props":124,"children":126},{"className":125},[],[127],{"type":50,"value":128},"project-context-ingestion",{"type":50,"value":130}," when possible.",{"type":45,"tag":76,"props":132,"children":134},{"id":133},"triage-workflow",[135],{"type":50,"value":136},"Triage Workflow",{"type":45,"tag":138,"props":139,"children":140},"ol",{},[141,146,159,207,212,217],{"type":45,"tag":98,"props":142,"children":143},{},[144],{"type":50,"value":145},"Find the earliest meaningful failure signal.",{"type":45,"tag":98,"props":147,"children":148},{},[149,151,157],{"type":50,"value":150},"Walk the ",{"type":45,"tag":59,"props":152,"children":154},{"className":153},[],[155],{"type":50,"value":156},"Caused by:",{"type":50,"value":158}," chain until it stops getting more specific.",{"type":45,"tag":98,"props":160,"children":161},{},[162,164],{"type":50,"value":163},"Classify the incident:\n",{"type":45,"tag":94,"props":165,"children":166},{},[167,172,177,182,187,192,197,202],{"type":45,"tag":98,"props":168,"children":169},{},[170],{"type":50,"value":171},"DI and context startup",{"type":45,"tag":98,"props":173,"children":174},{},[175],{"type":50,"value":176},"configuration binding",{"type":45,"tag":98,"props":178,"children":179},{},[180],{"type":50,"value":181},"serialization or validation",{"type":45,"tag":98,"props":183,"children":184},{},[185],{"type":50,"value":186},"SQL or migration",{"type":45,"tag":98,"props":188,"children":189},{},[190],{"type":50,"value":191},"HTTP or timeout",{"type":45,"tag":98,"props":193,"children":194},{},[195],{"type":50,"value":196},"security",{"type":45,"tag":98,"props":198,"children":199},{},[200],{"type":50,"value":201},"concurrency or locking",{"type":45,"tag":98,"props":203,"children":204},{},[205],{"type":50,"value":206},"classpath or version mismatch",{"type":45,"tag":98,"props":208,"children":209},{},[210],{"type":50,"value":211},"Separate what failed from why it failed.",{"type":45,"tag":98,"props":213,"children":214},{},[215],{"type":50,"value":216},"Rank hypotheses when evidence is incomplete.",{"type":45,"tag":98,"props":218,"children":219},{},[220],{"type":50,"value":221},"Propose a quick mitigation and a proper fix separately.",{"type":45,"tag":76,"props":223,"children":225},{"id":224},"diagnostic-rules",[226],{"type":50,"value":227},"Diagnostic Rules",{"type":45,"tag":94,"props":229,"children":230},{},[231,252,257,262,267],{"type":45,"tag":98,"props":232,"children":233},{},[234,236,242,244,250],{"type":50,"value":235},"Treat ",{"type":45,"tag":59,"props":237,"children":239},{"className":238},[],[240],{"type":50,"value":241},"BeanCreationException",{"type":50,"value":243},", ",{"type":45,"tag":59,"props":245,"children":247},{"className":246},[],[248],{"type":50,"value":249},"InvocationTargetException",{"type":50,"value":251},", and similar wrappers as transport, not diagnosis.",{"type":45,"tag":98,"props":253,"children":254},{},[255],{"type":50,"value":256},"Treat the first user-code frame after framework wrappers as high-signal evidence.",{"type":45,"tag":98,"props":258,"children":259},{},[260],{"type":50,"value":261},"Use log chronology, not stack depth alone.",{"type":45,"tag":98,"props":263,"children":264},{},[265],{"type":50,"value":266},"If the logs are truncated, say so and lower confidence.",{"type":45,"tag":98,"props":268,"children":269},{},[270],{"type":50,"value":271},"Prefer an explanation grounded in the observed code path or configuration over pattern-matching from memory.",{"type":45,"tag":76,"props":273,"children":275},{"id":274},"advanced-signal-patterns",[276],{"type":50,"value":277},"Advanced Signal Patterns",{"type":45,"tag":94,"props":279,"children":280},{},[281,286,291,296,301,306,311,316],{"type":45,"tag":98,"props":282,"children":283},{},[284],{"type":50,"value":285},"Check suppressed exceptions, root-cause logging one or two lines above the stack trace, and companion failures on adjacent threads. The most useful clue is often not in the main stack at all.",{"type":45,"tag":98,"props":287,"children":288},{},[289],{"type":50,"value":290},"Distinguish hard failures from saturation patterns: connection pool exhaustion, thread pool starvation, event-loop blocking, retry storms, and deadlock retries often show up as secondary symptoms first.",{"type":45,"tag":98,"props":292,"children":293},{},[294],{"type":50,"value":295},"For SQL failures, inspect vendor codes and SQL state when available. They are often more actionable than the wrapper exception type.",{"type":45,"tag":98,"props":297,"children":298},{},[299],{"type":50,"value":300},"For startup failures after version or deploy changes, compare classpath and configuration drift before assuming a code bug.",{"type":45,"tag":98,"props":302,"children":303},{},[304],{"type":50,"value":305},"For intermittent failures, weigh time correlation and concurrency context heavily. A race rarely leaves a clean single-thread narrative.",{"type":45,"tag":98,"props":307,"children":308},{},[309],{"type":50,"value":310},"For OOM or GC-related incidents, plain stack traces are weak evidence. Thread dumps, heap symptoms, and allocation context matter more.",{"type":45,"tag":98,"props":312,"children":313},{},[314],{"type":50,"value":315},"If metrics exist, correlate the first error spike with latency, pool saturation, or downstream dependency degradation rather than treating logs in isolation.",{"type":45,"tag":98,"props":317,"children":318},{},[319],{"type":50,"value":320},"If the symptom appears in reactive or coroutine code, verify whether context propagation broke logging correlation before dismissing missing IDs or misleading thread names.",{"type":45,"tag":76,"props":322,"children":324},{"id":323},"expert-heuristics",[325],{"type":50,"value":326},"Expert Heuristics",{"type":45,"tag":94,"props":328,"children":329},{},[330,335,340,345],{"type":45,"tag":98,"props":331,"children":332},{},[333],{"type":50,"value":334},"The first fix after triage should reduce uncertainty as well as reduce pain. Prefer mitigations that also sharpen diagnosis.",{"type":45,"tag":98,"props":336,"children":337},{},[338],{"type":50,"value":339},"If several candidate causes fit, rank them by evidence, blast radius, and reversibility of the proposed mitigation.",{"type":45,"tag":98,"props":341,"children":342},{},[343],{"type":50,"value":344},"If the trace points to a framework wrapper, move outward to code and config that changed recently, then inward again through the causal chain.",{"type":45,"tag":98,"props":346,"children":347},{},[348],{"type":50,"value":349},"Always state what evidence would falsify the leading hypothesis.",{"type":45,"tag":76,"props":351,"children":353},{"id":352},"output-contract",[354],{"type":50,"value":355},"Output Contract",{"type":45,"tag":53,"props":357,"children":358},{},[359],{"type":50,"value":360},"Return these sections:",{"type":45,"tag":94,"props":362,"children":363},{},[364,375,386,397,408,419],{"type":45,"tag":98,"props":365,"children":366},{},[367,373],{"type":45,"tag":59,"props":368,"children":370},{"className":369},[],[371],{"type":50,"value":372},"Root cause",{"type":50,"value":374},": confirmed or most likely cause in plain language.",{"type":45,"tag":98,"props":376,"children":377},{},[378,384],{"type":45,"tag":59,"props":379,"children":381},{"className":380},[],[382],{"type":50,"value":383},"Confidence",{"type":50,"value":385},": confirmed, high, medium, or low.",{"type":45,"tag":98,"props":387,"children":388},{},[389,395],{"type":45,"tag":59,"props":390,"children":392},{"className":391},[],[393],{"type":50,"value":394},"Evidence",{"type":50,"value":396},": the log line, exception, config fact, or code path supporting the diagnosis.",{"type":45,"tag":98,"props":398,"children":399},{},[400,406],{"type":45,"tag":59,"props":401,"children":403},{"className":402},[],[404],{"type":50,"value":405},"Hotfix",{"type":50,"value":407},": the safest immediate containment or unblocking step.",{"type":45,"tag":98,"props":409,"children":410},{},[411,417],{"type":45,"tag":59,"props":412,"children":414},{"className":413},[],[415],{"type":50,"value":416},"Long-term fix",{"type":50,"value":418},": the proper code or configuration correction.",{"type":45,"tag":98,"props":420,"children":421},{},[422,428],{"type":45,"tag":59,"props":423,"children":425},{"className":424},[],[426],{"type":50,"value":427},"Reproduction and verification",{"type":50,"value":429},": how to reproduce, test, and monitor the fix.",{"type":45,"tag":76,"props":431,"children":433},{"id":432},"safety-rules",[434],{"type":50,"value":435},"Safety Rules",{"type":45,"tag":94,"props":437,"children":438},{},[439,444,449,454],{"type":45,"tag":98,"props":440,"children":441},{},[442],{"type":50,"value":443},"Label hypotheses as hypotheses.",{"type":45,"tag":98,"props":445,"children":446},{},[447],{"type":50,"value":448},"Do not recommend risky schema changes, version upgrades, or broad refactors as a hotfix unless the incident truly leaves no safer option.",{"type":45,"tag":98,"props":450,"children":451},{},[452],{"type":50,"value":453},"Do not claim certainty when the logs are incomplete.",{"type":45,"tag":98,"props":455,"children":456},{},[457],{"type":50,"value":458},"Do not ignore alerting or monitoring implications after the fix.",{"type":45,"tag":76,"props":460,"children":462},{"id":461},"kotlin-specific-checks",[463],{"type":50,"value":464},"Kotlin-Specific Checks",{"type":45,"tag":94,"props":466,"children":467},{},[468,481,486,491],{"type":45,"tag":98,"props":469,"children":470},{},[471,473,479],{"type":50,"value":472},"Watch for platform-type ",{"type":45,"tag":59,"props":474,"children":476},{"className":475},[],[477],{"type":50,"value":478},"NullPointerException",{"type":50,"value":480},".",{"type":45,"tag":98,"props":482,"children":483},{},[484],{"type":50,"value":485},"Watch for coroutine stack traces that obscure the original call path.",{"type":45,"tag":98,"props":487,"children":488},{},[489],{"type":50,"value":490},"Watch for missing Kotlin compiler plugins causing runtime behavior gaps.",{"type":45,"tag":98,"props":492,"children":493},{},[494],{"type":50,"value":495},"Watch for Jackson plus Kotlin constructor issues that surface as generic deserialization errors.",{"type":45,"tag":76,"props":497,"children":499},{"id":498},"quality-bar",[500],{"type":50,"value":501},"Quality Bar",{"type":45,"tag":53,"props":503,"children":504},{},[505,507,512],{"type":50,"value":506},"A good run of this skill gives the user a path from failure evidence to safe remediation.\nA bad run repeats the top exception, ignores the ",{"type":45,"tag":59,"props":508,"children":510},{"className":509},[],[511],{"type":50,"value":156},{"type":50,"value":513}," chain, or offers a dangerous hotfix without explaining the risk.",{"items":515,"total":635},[516,535,552,568,583,602,619],{"slug":517,"name":517,"fn":518,"description":519,"org":520,"tags":521,"stars":25,"repoUrl":26,"updatedAt":534},"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},[522,525,528,531],{"name":523,"slug":524,"type":15},"Creative","creative",{"name":526,"slug":527,"type":15},"Generative Art","generative-art",{"name":529,"slug":530,"type":15},"Graphics","graphics",{"name":532,"slug":533,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":25,"repoUrl":26,"updatedAt":551},"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},[541,544,547,548],{"name":542,"slug":543,"type":15},"Best Practices","best-practices",{"name":545,"slug":546,"type":15},"Engineering","engineering",{"name":532,"slug":533,"type":15},{"name":549,"slug":550,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":25,"repoUrl":26,"updatedAt":567},"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},[558,561,564],{"name":559,"slug":560,"type":15},"Branding","branding",{"name":562,"slug":563,"type":15},"Design","design",{"name":565,"slug":566,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":569,"name":569,"fn":570,"description":571,"org":572,"tags":573,"stars":25,"repoUrl":26,"updatedAt":582},"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},[574,575,576,579],{"name":523,"slug":524,"type":15},{"name":562,"slug":563,"type":15},{"name":577,"slug":578,"type":15},"Images","images",{"name":580,"slug":581,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":584,"name":584,"fn":585,"description":586,"org":587,"tags":588,"stars":25,"repoUrl":26,"updatedAt":601},"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},[589,592,595,598,599,600],{"name":590,"slug":591,"type":15},"CI\u002FCD","ci-cd",{"name":593,"slug":594,"type":15},"Containers","containers",{"name":596,"slug":597,"type":15},"Deployment","deployment",{"name":545,"slug":546,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":603,"name":603,"fn":604,"description":605,"org":606,"tags":607,"stars":25,"repoUrl":26,"updatedAt":618},"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},[608,611,614,617],{"name":609,"slug":610,"type":15},"Cloudflare","cloudflare",{"name":612,"slug":613,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":615,"slug":616,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":596,"slug":597,"type":15},"2026-07-17T06:04:42.853896",{"slug":620,"name":620,"fn":621,"description":622,"org":623,"tags":624,"stars":25,"repoUrl":26,"updatedAt":634},"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},[625,628,631],{"name":626,"slug":627,"type":15},"Automation","automation",{"name":629,"slug":630,"type":15},"Desktop","desktop",{"name":632,"slug":633,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":637,"total":760},[638,654,663,672,683,693,702,711,720,730,739,750],{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":651,"repoUrl":652,"updatedAt":653},"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},[644,647,650],{"name":645,"slug":646,"type":15},"Architecture","architecture",{"name":648,"slug":649,"type":15},"Configuration","configuration",{"name":545,"slug":546,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":655,"name":655,"fn":656,"description":657,"org":658,"tags":659,"stars":651,"repoUrl":652,"updatedAt":662},"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},[660,661],{"name":645,"slug":646,"type":15},{"name":545,"slug":546,"type":15},"2026-07-17T06:04:48.066901",{"slug":664,"name":664,"fn":665,"description":666,"org":667,"tags":668,"stars":651,"repoUrl":652,"updatedAt":671},"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},[669,670],{"name":645,"slug":646,"type":15},{"name":545,"slug":546,"type":15},"2026-07-13T06:45:21.757084",{"slug":673,"name":673,"fn":674,"description":675,"org":676,"tags":677,"stars":651,"repoUrl":652,"updatedAt":682},"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},[678,679],{"name":645,"slug":646,"type":15},{"name":680,"slug":681,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":684,"name":684,"fn":685,"description":686,"org":687,"tags":688,"stars":651,"repoUrl":652,"updatedAt":692},"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},[689],{"name":690,"slug":691,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":694,"name":694,"fn":695,"description":696,"org":697,"tags":698,"stars":651,"repoUrl":652,"updatedAt":701},"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},[699,700],{"name":562,"slug":563,"type":15},{"name":632,"slug":633,"type":15},"2026-07-23T05:41:56.638151",{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":651,"repoUrl":652,"updatedAt":710},"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},[708,709],{"name":545,"slug":546,"type":15},{"name":632,"slug":633,"type":15},"2026-07-23T05:41:49.666535",{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":651,"repoUrl":652,"updatedAt":719},"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},[717,718],{"name":645,"slug":646,"type":15},{"name":545,"slug":546,"type":15},"2026-07-13T06:44:59.507855",{"slug":721,"name":721,"fn":722,"description":723,"org":724,"tags":725,"stars":651,"repoUrl":652,"updatedAt":729},"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},[726,727,728],{"name":645,"slug":646,"type":15},{"name":680,"slug":681,"type":15},{"name":545,"slug":546,"type":15},"2026-07-17T06:06:58.042999",{"slug":731,"name":731,"fn":732,"description":733,"org":734,"tags":735,"stars":651,"repoUrl":652,"updatedAt":738},"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},[736,737],{"name":645,"slug":646,"type":15},{"name":545,"slug":546,"type":15},"2026-07-23T05:41:48.692899",{"slug":740,"name":740,"fn":741,"description":742,"org":743,"tags":744,"stars":651,"repoUrl":652,"updatedAt":749},"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},[745,746],{"name":23,"slug":24,"type":15},{"name":747,"slug":748,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":751,"name":751,"fn":752,"description":753,"org":754,"tags":755,"stars":651,"repoUrl":652,"updatedAt":759},"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},[756],{"name":757,"slug":758,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]