[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-test-suite-builder":3,"mdc-ccppa7-key":33,"related-repo-jetbrains-test-suite-builder":569,"related-org-jetbrains-test-suite-builder":691},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":22,"repoUrl":23,"updatedAt":24,"license":25,"forks":26,"topics":27,"repo":28,"sourceUrl":31,"mdContent":32},"test-suite-builder","generate layered Kotlin and Spring tests","Design and generate layered Kotlin + Spring tests that balance speed, realism, and regression value across unit, slice, and integration levels. Use when adding coverage for business logic, controllers, repositories, security, serialization, or end-to-end workflows, and when generic AI output would otherwise overuse `@SpringBootTest`, misuse mocks, or ignore MockK and coroutine testing idioms.",{"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],{"name":13,"slug":14,"type":15},"Kotlin","kotlin","tag",{"name":17,"slug":18,"type":15},"Spring","spring",{"name":20,"slug":21,"type":15},"Testing","testing",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:42:57.197153",null,17,[],{"repoUrl":23,"stars":22,"forks":26,"topics":29,"description":30},[],"Curated agent skills collection verified by JetBrains","https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills\u002Ftree\u002FHEAD\u002Ftest-suite-builder","---\nname: test-suite-builder\ndescription: Design and generate layered Kotlin + Spring tests that balance speed, realism, and regression value across unit, slice, and integration levels. Use when adding coverage for business logic, controllers, repositories, security, serialization, or end-to-end workflows, and when generic AI output would otherwise overuse `@SpringBootTest`, misuse mocks, or ignore MockK and coroutine testing idioms.\nmetadata:\n  short-description: \"Design layered Kotlin\u002FSpring tests\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Ftest-suite-builder\n---\n\n# Test Suite Builder\n\nSource mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-14`).\n\n## Mission\n\nChoose the lightest test that proves the behavior.\nGenerate tests that catch regressions instead of reproducing the implementation line by line.\n\n## Start With A Test Strategy\n\nBefore writing code, classify what needs to be proven:\n\n- pure business logic\n- HTTP contract and validation\n- repository query behavior\n- serialization behavior\n- security rules\n- cross-component integration\n- database or message-broker integration\n\n## Three-Layer Strategy\n\n- Use unit tests for domain logic, calculations, decision tables, and deterministic branching.\n- Use slice tests for framework boundaries:\n  - `@WebMvcTest` or `WebTestClient` for HTTP\n  - `@DataJpaTest` for repositories\n  - focused JSON or security slices when available in the project\n- Use `@SpringBootTest` and Testcontainers only when a realistic application graph or infrastructure boundary must be proven.\n\n## Kotlin Testing Rules\n\n- Prefer JUnit 5.\n- Prefer MockK over Mockito unless the repository already standardizes on something else.\n- Use readable backtick test names when that matches the project style.\n- Use `runTest` and the coroutine test toolkit for coroutine-heavy code.\n- Build reusable fixtures, builders, or object mothers instead of duplicating inline object construction.\n\n## What To Cover\n\n- Success path.\n- Validation failures.\n- Business rule failures.\n- Edge cases around nullability, optional fields, empty collections, and duplicates.\n- At least one regression-oriented test for the bug or change that motivated the work.\n\n## What Not To Do\n\n- Do not default to `@SpringBootTest` when a slice test or unit test is enough.\n- Do not write tests that only verify mock interactions and prove nothing observable.\n- Do not couple assertions to private implementation details when public behavior is enough.\n- Do not use real time, random values, or shared mutable state without control.\n\n## Output Contract\n\nReturn these sections:\n\n- `Test plan`: which layers to use and why.\n- `Generated tests`: the concrete test classes or patch plan.\n- `Test data support`: builders, fixtures, or factories to add.\n- `Coverage gaps`: important cases still not covered.\n- `Verification`: commands to run and which tests should fail before the fix.\n\n## Framework-Specific Checks\n\n- Match `MockMvc` vs `WebTestClient` to MVC vs WebFlux.\n- Match Testcontainers setup to the actual database or broker in the repository.\n- If serialization or validation is the bug, include a test that proves the wire contract, not only the service logic.\n- If transaction behavior matters, add a test that proves rollback or uniqueness behavior in the real persistence layer.\n\n## Advanced Testing Nuances\n\n- A transactional test that always rolls back can hide commit-time failures. Use explicit flush or real commit boundaries when unique constraints, triggers, or transaction listeners matter.\n- H2 is not a safe stand-in for Postgres or MySQL when dialect, JSON, locking, index use, or transaction semantics matter. Prefer the real engine with Testcontainers for those cases.\n- `@MockBean` is powerful but expensive. Overusing it turns integration tests into slow unit tests with hidden wiring.\n- Security tests should usually prove both `401` and `403`, not just the happy authorized path.\n- Async and event-driven flows need deterministic waiting strategies such as controlled schedulers, latches, or Awaitility. Do not scatter sleeps.\n- Concurrency and deadlock behavior cannot be proven in a single-threaded rollback test. Use multiple transactions and explicit synchronization when reviewing those cases.\n- Reused containers improve speed but require strict state isolation. Do not trade determinism away for a faster green build.\n- Use deterministic time and ID providers when business logic depends on clocks or UUIDs.\n\n## Expert Heuristics\n\n- If a bug was caused by framework wiring, add at least one test above unit level.\n- If a bug was caused by domain branching, do not drag the whole Spring context into the fix.\n- When in doubt, choose the smallest test that would have failed before the change.\n- Treat test code as production code for readability and maintenance. Fixtures and helpers should reduce noise, not hide behavior.\n\n## Guardrails\n\n- Keep tests deterministic.\n- Keep setup explicit and local to the scenario.\n- Prefer one clear reason for failure per test.\n- Do not silently introduce slow infrastructure-heavy tests into fast unit test suites.\n\n## Quality Bar\n\nA good run of this skill produces a test suite that is fast where possible and realistic where necessary.\nA bad run floods the project with context-heavy tests, brittle mocks, and no clear explanation of why each test level exists.\n",{"data":34,"body":38},{"name":4,"description":6,"metadata":35},{"short-description":36,"author":13,"source":37},"Design layered Kotlin\u002FSpring tests","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Ftest-suite-builder",{"type":39,"children":40},"root",[41,49,72,79,84,90,95,135,141,205,211,246,252,280,286,316,322,327,385,391,429,435,500,506,529,535,558,564],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Test Suite Builder",{"type":42,"tag":50,"props":51,"children":52},"p",{},[53,55,62,64,70],{"type":47,"value":54},"Source mapping: Tier 1 critical skill derived from ",{"type":42,"tag":56,"props":57,"children":59},"code",{"className":58},[],[60],{"type":47,"value":61},"Kotlin_Spring_Developer_Pipeline.md",{"type":47,"value":63}," (",{"type":42,"tag":56,"props":65,"children":67},{"className":66},[],[68],{"type":47,"value":69},"SK-14",{"type":47,"value":71},").",{"type":42,"tag":73,"props":74,"children":76},"h2",{"id":75},"mission",[77],{"type":47,"value":78},"Mission",{"type":42,"tag":50,"props":80,"children":81},{},[82],{"type":47,"value":83},"Choose the lightest test that proves the behavior.\nGenerate tests that catch regressions instead of reproducing the implementation line by line.",{"type":42,"tag":73,"props":85,"children":87},{"id":86},"start-with-a-test-strategy",[88],{"type":47,"value":89},"Start With A Test Strategy",{"type":42,"tag":50,"props":91,"children":92},{},[93],{"type":47,"value":94},"Before writing code, classify what needs to be proven:",{"type":42,"tag":96,"props":97,"children":98},"ul",{},[99,105,110,115,120,125,130],{"type":42,"tag":100,"props":101,"children":102},"li",{},[103],{"type":47,"value":104},"pure business logic",{"type":42,"tag":100,"props":106,"children":107},{},[108],{"type":47,"value":109},"HTTP contract and validation",{"type":42,"tag":100,"props":111,"children":112},{},[113],{"type":47,"value":114},"repository query behavior",{"type":42,"tag":100,"props":116,"children":117},{},[118],{"type":47,"value":119},"serialization behavior",{"type":42,"tag":100,"props":121,"children":122},{},[123],{"type":47,"value":124},"security rules",{"type":42,"tag":100,"props":126,"children":127},{},[128],{"type":47,"value":129},"cross-component integration",{"type":42,"tag":100,"props":131,"children":132},{},[133],{"type":47,"value":134},"database or message-broker integration",{"type":42,"tag":73,"props":136,"children":138},{"id":137},"three-layer-strategy",[139],{"type":47,"value":140},"Three-Layer Strategy",{"type":42,"tag":96,"props":142,"children":143},{},[144,149,192],{"type":42,"tag":100,"props":145,"children":146},{},[147],{"type":47,"value":148},"Use unit tests for domain logic, calculations, decision tables, and deterministic branching.",{"type":42,"tag":100,"props":150,"children":151},{},[152,154],{"type":47,"value":153},"Use slice tests for framework boundaries:\n",{"type":42,"tag":96,"props":155,"children":156},{},[157,176,187],{"type":42,"tag":100,"props":158,"children":159},{},[160,166,168,174],{"type":42,"tag":56,"props":161,"children":163},{"className":162},[],[164],{"type":47,"value":165},"@WebMvcTest",{"type":47,"value":167}," or ",{"type":42,"tag":56,"props":169,"children":171},{"className":170},[],[172],{"type":47,"value":173},"WebTestClient",{"type":47,"value":175}," for HTTP",{"type":42,"tag":100,"props":177,"children":178},{},[179,185],{"type":42,"tag":56,"props":180,"children":182},{"className":181},[],[183],{"type":47,"value":184},"@DataJpaTest",{"type":47,"value":186}," for repositories",{"type":42,"tag":100,"props":188,"children":189},{},[190],{"type":47,"value":191},"focused JSON or security slices when available in the project",{"type":42,"tag":100,"props":193,"children":194},{},[195,197,203],{"type":47,"value":196},"Use ",{"type":42,"tag":56,"props":198,"children":200},{"className":199},[],[201],{"type":47,"value":202},"@SpringBootTest",{"type":47,"value":204}," and Testcontainers only when a realistic application graph or infrastructure boundary must be proven.",{"type":42,"tag":73,"props":206,"children":208},{"id":207},"kotlin-testing-rules",[209],{"type":47,"value":210},"Kotlin Testing Rules",{"type":42,"tag":96,"props":212,"children":213},{},[214,219,224,229,241],{"type":42,"tag":100,"props":215,"children":216},{},[217],{"type":47,"value":218},"Prefer JUnit 5.",{"type":42,"tag":100,"props":220,"children":221},{},[222],{"type":47,"value":223},"Prefer MockK over Mockito unless the repository already standardizes on something else.",{"type":42,"tag":100,"props":225,"children":226},{},[227],{"type":47,"value":228},"Use readable backtick test names when that matches the project style.",{"type":42,"tag":100,"props":230,"children":231},{},[232,233,239],{"type":47,"value":196},{"type":42,"tag":56,"props":234,"children":236},{"className":235},[],[237],{"type":47,"value":238},"runTest",{"type":47,"value":240}," and the coroutine test toolkit for coroutine-heavy code.",{"type":42,"tag":100,"props":242,"children":243},{},[244],{"type":47,"value":245},"Build reusable fixtures, builders, or object mothers instead of duplicating inline object construction.",{"type":42,"tag":73,"props":247,"children":249},{"id":248},"what-to-cover",[250],{"type":47,"value":251},"What To Cover",{"type":42,"tag":96,"props":253,"children":254},{},[255,260,265,270,275],{"type":42,"tag":100,"props":256,"children":257},{},[258],{"type":47,"value":259},"Success path.",{"type":42,"tag":100,"props":261,"children":262},{},[263],{"type":47,"value":264},"Validation failures.",{"type":42,"tag":100,"props":266,"children":267},{},[268],{"type":47,"value":269},"Business rule failures.",{"type":42,"tag":100,"props":271,"children":272},{},[273],{"type":47,"value":274},"Edge cases around nullability, optional fields, empty collections, and duplicates.",{"type":42,"tag":100,"props":276,"children":277},{},[278],{"type":47,"value":279},"At least one regression-oriented test for the bug or change that motivated the work.",{"type":42,"tag":73,"props":281,"children":283},{"id":282},"what-not-to-do",[284],{"type":47,"value":285},"What Not To Do",{"type":42,"tag":96,"props":287,"children":288},{},[289,301,306,311],{"type":42,"tag":100,"props":290,"children":291},{},[292,294,299],{"type":47,"value":293},"Do not default to ",{"type":42,"tag":56,"props":295,"children":297},{"className":296},[],[298],{"type":47,"value":202},{"type":47,"value":300}," when a slice test or unit test is enough.",{"type":42,"tag":100,"props":302,"children":303},{},[304],{"type":47,"value":305},"Do not write tests that only verify mock interactions and prove nothing observable.",{"type":42,"tag":100,"props":307,"children":308},{},[309],{"type":47,"value":310},"Do not couple assertions to private implementation details when public behavior is enough.",{"type":42,"tag":100,"props":312,"children":313},{},[314],{"type":47,"value":315},"Do not use real time, random values, or shared mutable state without control.",{"type":42,"tag":73,"props":317,"children":319},{"id":318},"output-contract",[320],{"type":47,"value":321},"Output Contract",{"type":42,"tag":50,"props":323,"children":324},{},[325],{"type":47,"value":326},"Return these sections:",{"type":42,"tag":96,"props":328,"children":329},{},[330,341,352,363,374],{"type":42,"tag":100,"props":331,"children":332},{},[333,339],{"type":42,"tag":56,"props":334,"children":336},{"className":335},[],[337],{"type":47,"value":338},"Test plan",{"type":47,"value":340},": which layers to use and why.",{"type":42,"tag":100,"props":342,"children":343},{},[344,350],{"type":42,"tag":56,"props":345,"children":347},{"className":346},[],[348],{"type":47,"value":349},"Generated tests",{"type":47,"value":351},": the concrete test classes or patch plan.",{"type":42,"tag":100,"props":353,"children":354},{},[355,361],{"type":42,"tag":56,"props":356,"children":358},{"className":357},[],[359],{"type":47,"value":360},"Test data support",{"type":47,"value":362},": builders, fixtures, or factories to add.",{"type":42,"tag":100,"props":364,"children":365},{},[366,372],{"type":42,"tag":56,"props":367,"children":369},{"className":368},[],[370],{"type":47,"value":371},"Coverage gaps",{"type":47,"value":373},": important cases still not covered.",{"type":42,"tag":100,"props":375,"children":376},{},[377,383],{"type":42,"tag":56,"props":378,"children":380},{"className":379},[],[381],{"type":47,"value":382},"Verification",{"type":47,"value":384},": commands to run and which tests should fail before the fix.",{"type":42,"tag":73,"props":386,"children":388},{"id":387},"framework-specific-checks",[389],{"type":47,"value":390},"Framework-Specific Checks",{"type":42,"tag":96,"props":392,"children":393},{},[394,414,419,424],{"type":42,"tag":100,"props":395,"children":396},{},[397,399,405,407,412],{"type":47,"value":398},"Match ",{"type":42,"tag":56,"props":400,"children":402},{"className":401},[],[403],{"type":47,"value":404},"MockMvc",{"type":47,"value":406}," vs ",{"type":42,"tag":56,"props":408,"children":410},{"className":409},[],[411],{"type":47,"value":173},{"type":47,"value":413}," to MVC vs WebFlux.",{"type":42,"tag":100,"props":415,"children":416},{},[417],{"type":47,"value":418},"Match Testcontainers setup to the actual database or broker in the repository.",{"type":42,"tag":100,"props":420,"children":421},{},[422],{"type":47,"value":423},"If serialization or validation is the bug, include a test that proves the wire contract, not only the service logic.",{"type":42,"tag":100,"props":425,"children":426},{},[427],{"type":47,"value":428},"If transaction behavior matters, add a test that proves rollback or uniqueness behavior in the real persistence layer.",{"type":42,"tag":73,"props":430,"children":432},{"id":431},"advanced-testing-nuances",[433],{"type":47,"value":434},"Advanced Testing Nuances",{"type":42,"tag":96,"props":436,"children":437},{},[438,443,448,459,480,485,490,495],{"type":42,"tag":100,"props":439,"children":440},{},[441],{"type":47,"value":442},"A transactional test that always rolls back can hide commit-time failures. Use explicit flush or real commit boundaries when unique constraints, triggers, or transaction listeners matter.",{"type":42,"tag":100,"props":444,"children":445},{},[446],{"type":47,"value":447},"H2 is not a safe stand-in for Postgres or MySQL when dialect, JSON, locking, index use, or transaction semantics matter. Prefer the real engine with Testcontainers for those cases.",{"type":42,"tag":100,"props":449,"children":450},{},[451,457],{"type":42,"tag":56,"props":452,"children":454},{"className":453},[],[455],{"type":47,"value":456},"@MockBean",{"type":47,"value":458}," is powerful but expensive. Overusing it turns integration tests into slow unit tests with hidden wiring.",{"type":42,"tag":100,"props":460,"children":461},{},[462,464,470,472,478],{"type":47,"value":463},"Security tests should usually prove both ",{"type":42,"tag":56,"props":465,"children":467},{"className":466},[],[468],{"type":47,"value":469},"401",{"type":47,"value":471}," and ",{"type":42,"tag":56,"props":473,"children":475},{"className":474},[],[476],{"type":47,"value":477},"403",{"type":47,"value":479},", not just the happy authorized path.",{"type":42,"tag":100,"props":481,"children":482},{},[483],{"type":47,"value":484},"Async and event-driven flows need deterministic waiting strategies such as controlled schedulers, latches, or Awaitility. Do not scatter sleeps.",{"type":42,"tag":100,"props":486,"children":487},{},[488],{"type":47,"value":489},"Concurrency and deadlock behavior cannot be proven in a single-threaded rollback test. Use multiple transactions and explicit synchronization when reviewing those cases.",{"type":42,"tag":100,"props":491,"children":492},{},[493],{"type":47,"value":494},"Reused containers improve speed but require strict state isolation. Do not trade determinism away for a faster green build.",{"type":42,"tag":100,"props":496,"children":497},{},[498],{"type":47,"value":499},"Use deterministic time and ID providers when business logic depends on clocks or UUIDs.",{"type":42,"tag":73,"props":501,"children":503},{"id":502},"expert-heuristics",[504],{"type":47,"value":505},"Expert Heuristics",{"type":42,"tag":96,"props":507,"children":508},{},[509,514,519,524],{"type":42,"tag":100,"props":510,"children":511},{},[512],{"type":47,"value":513},"If a bug was caused by framework wiring, add at least one test above unit level.",{"type":42,"tag":100,"props":515,"children":516},{},[517],{"type":47,"value":518},"If a bug was caused by domain branching, do not drag the whole Spring context into the fix.",{"type":42,"tag":100,"props":520,"children":521},{},[522],{"type":47,"value":523},"When in doubt, choose the smallest test that would have failed before the change.",{"type":42,"tag":100,"props":525,"children":526},{},[527],{"type":47,"value":528},"Treat test code as production code for readability and maintenance. Fixtures and helpers should reduce noise, not hide behavior.",{"type":42,"tag":73,"props":530,"children":532},{"id":531},"guardrails",[533],{"type":47,"value":534},"Guardrails",{"type":42,"tag":96,"props":536,"children":537},{},[538,543,548,553],{"type":42,"tag":100,"props":539,"children":540},{},[541],{"type":47,"value":542},"Keep tests deterministic.",{"type":42,"tag":100,"props":544,"children":545},{},[546],{"type":47,"value":547},"Keep setup explicit and local to the scenario.",{"type":42,"tag":100,"props":549,"children":550},{},[551],{"type":47,"value":552},"Prefer one clear reason for failure per test.",{"type":42,"tag":100,"props":554,"children":555},{},[556],{"type":47,"value":557},"Do not silently introduce slow infrastructure-heavy tests into fast unit test suites.",{"type":42,"tag":73,"props":559,"children":561},{"id":560},"quality-bar",[562],{"type":47,"value":563},"Quality Bar",{"type":42,"tag":50,"props":565,"children":566},{},[567],{"type":47,"value":568},"A good run of this skill produces a test suite that is fast where possible and realistic where necessary.\nA bad run floods the project with context-heavy tests, brittle mocks, and no clear explanation of why each test level exists.",{"items":570,"total":690},[571,590,607,623,638,657,674],{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":22,"repoUrl":23,"updatedAt":589},"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},[577,580,583,586],{"name":578,"slug":579,"type":15},"Creative","creative",{"name":581,"slug":582,"type":15},"Generative Art","generative-art",{"name":584,"slug":585,"type":15},"Graphics","graphics",{"name":587,"slug":588,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":591,"name":591,"fn":592,"description":593,"org":594,"tags":595,"stars":22,"repoUrl":23,"updatedAt":606},"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},[596,599,602,603],{"name":597,"slug":598,"type":15},"Best Practices","best-practices",{"name":600,"slug":601,"type":15},"Engineering","engineering",{"name":587,"slug":588,"type":15},{"name":604,"slug":605,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":608,"name":608,"fn":609,"description":610,"org":611,"tags":612,"stars":22,"repoUrl":23,"updatedAt":622},"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},[613,616,619],{"name":614,"slug":615,"type":15},"Branding","branding",{"name":617,"slug":618,"type":15},"Design","design",{"name":620,"slug":621,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":624,"name":624,"fn":625,"description":626,"org":627,"tags":628,"stars":22,"repoUrl":23,"updatedAt":637},"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},[629,630,631,634],{"name":578,"slug":579,"type":15},{"name":617,"slug":618,"type":15},{"name":632,"slug":633,"type":15},"Images","images",{"name":635,"slug":636,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":22,"repoUrl":23,"updatedAt":656},"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},[644,647,650,653,654,655],{"name":645,"slug":646,"type":15},"CI\u002FCD","ci-cd",{"name":648,"slug":649,"type":15},"Containers","containers",{"name":651,"slug":652,"type":15},"Deployment","deployment",{"name":600,"slug":601,"type":15},{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},"2026-07-13T06:41:47.83899",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":22,"repoUrl":23,"updatedAt":673},"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},[663,666,669,672],{"name":664,"slug":665,"type":15},"Cloudflare","cloudflare",{"name":667,"slug":668,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":670,"slug":671,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":651,"slug":652,"type":15},"2026-07-17T06:04:42.853896",{"slug":675,"name":675,"fn":676,"description":677,"org":678,"tags":679,"stars":22,"repoUrl":23,"updatedAt":689},"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},[680,683,686],{"name":681,"slug":682,"type":15},"Automation","automation",{"name":684,"slug":685,"type":15},"Desktop","desktop",{"name":687,"slug":688,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":692,"total":817},[693,709,718,727,738,748,757,766,775,785,794,807],{"slug":694,"name":694,"fn":695,"description":696,"org":697,"tags":698,"stars":706,"repoUrl":707,"updatedAt":708},"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},[699,702,705],{"name":700,"slug":701,"type":15},"Architecture","architecture",{"name":703,"slug":704,"type":15},"Configuration","configuration",{"name":600,"slug":601,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":706,"repoUrl":707,"updatedAt":717},"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},[715,716],{"name":700,"slug":701,"type":15},{"name":600,"slug":601,"type":15},"2026-07-17T06:04:48.066901",{"slug":719,"name":719,"fn":720,"description":721,"org":722,"tags":723,"stars":706,"repoUrl":707,"updatedAt":726},"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},[724,725],{"name":700,"slug":701,"type":15},{"name":600,"slug":601,"type":15},"2026-07-13T06:45:21.757084",{"slug":728,"name":728,"fn":729,"description":730,"org":731,"tags":732,"stars":706,"repoUrl":707,"updatedAt":737},"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},[733,734],{"name":700,"slug":701,"type":15},{"name":735,"slug":736,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":739,"name":739,"fn":740,"description":741,"org":742,"tags":743,"stars":706,"repoUrl":707,"updatedAt":747},"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},[744],{"name":745,"slug":746,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":749,"name":749,"fn":750,"description":751,"org":752,"tags":753,"stars":706,"repoUrl":707,"updatedAt":756},"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},[754,755],{"name":617,"slug":618,"type":15},{"name":687,"slug":688,"type":15},"2026-07-23T05:41:56.638151",{"slug":758,"name":758,"fn":759,"description":760,"org":761,"tags":762,"stars":706,"repoUrl":707,"updatedAt":765},"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},[763,764],{"name":600,"slug":601,"type":15},{"name":687,"slug":688,"type":15},"2026-07-23T05:41:49.666535",{"slug":767,"name":767,"fn":768,"description":769,"org":770,"tags":771,"stars":706,"repoUrl":707,"updatedAt":774},"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},[772,773],{"name":700,"slug":701,"type":15},{"name":600,"slug":601,"type":15},"2026-07-13T06:44:59.507855",{"slug":776,"name":776,"fn":777,"description":778,"org":779,"tags":780,"stars":706,"repoUrl":707,"updatedAt":784},"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},[781,782,783],{"name":700,"slug":701,"type":15},{"name":735,"slug":736,"type":15},{"name":600,"slug":601,"type":15},"2026-07-17T06:06:58.042999",{"slug":786,"name":786,"fn":787,"description":788,"org":789,"tags":790,"stars":706,"repoUrl":707,"updatedAt":793},"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},[791,792],{"name":700,"slug":701,"type":15},{"name":600,"slug":601,"type":15},"2026-07-23T05:41:48.692899",{"slug":795,"name":795,"fn":796,"description":797,"org":798,"tags":799,"stars":706,"repoUrl":707,"updatedAt":806},"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},[800,803],{"name":801,"slug":802,"type":15},"Debugging","debugging",{"name":804,"slug":805,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":808,"name":808,"fn":809,"description":810,"org":811,"tags":812,"stars":706,"repoUrl":707,"updatedAt":816},"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},[813],{"name":814,"slug":815,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]