[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-configuration-properties-profiles-kotlin-safe":3,"mdc--tskyl-key":36,"related-repo-jetbrains-configuration-properties-profiles-kotlin-safe":566,"related-org-jetbrains-configuration-properties-profiles-kotlin-safe":686},{"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},"configuration-properties-profiles-kotlin-safe","configure Spring properties for Kotlin applications","Design and diagnose Spring configuration, profiles, and `@ConfigurationProperties` binding for Kotlin applications. Use when property binding fails, environment-specific overrides behave unexpectedly, profile layering is confusing, secrets or defaults are modeled unsafely, or Kotlin nullability and constructor binding semantics make configuration errors hard to detect.",{"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},"Configuration","configuration",{"name":20,"slug":21,"type":15},"Spring","spring",{"name":23,"slug":24,"type":15},"Engineering","engineering",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:41:54.748966",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\u002Fconfiguration-properties-profiles-kotlin-safe","---\nname: configuration-properties-profiles-kotlin-safe\ndescription: Design and diagnose Spring configuration, profiles, and `@ConfigurationProperties` binding for Kotlin applications. Use when property binding fails, environment-specific overrides behave unexpectedly, profile layering is confusing, secrets or defaults are modeled unsafely, or Kotlin nullability and constructor binding semantics make configuration errors hard to detect.\nmetadata:\n  short-description: \"Make Kotlin Spring config predictable\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguration-properties-profiles-kotlin-safe\n---\n\n# Configuration Properties Profiles Kotlin Safe\n\nSource mapping: Tier 2 high-value skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-16`).\n\n## Mission\n\nMake configuration predictable across local, test, staging, and production environments.\nTreat configuration as typed application input, not as unstructured text.\n\n## Read First\n\n- `application.yml`, `application.properties`, and profile-specific files.\n- `@ConfigurationProperties` classes and how they are registered.\n- Environment variable names, Helm values, Config Server or Vault usage, and test overrides.\n- Active profile configuration and profile groups.\n- Any custom converters, property placeholders, or late-bound secret conventions.\n\n## Diagnose In This Order\n\n1. Verify source precedence:\n   - default config file\n   - profile-specific file\n   - environment variables\n   - `SPRING_APPLICATION_JSON`\n   - external config systems\n2. Verify prefix mapping and key shape.\n3. Verify constructor binding, defaults, and nullability.\n4. Verify collection, map, nested object, duration, and data-size binding.\n5. Verify profile activation and profile merge behavior.\n6. Verify whether the bug exists only in tests or only in deployment templates.\n\n## Kotlin-Safe Modeling Rules\n\n- Model genuinely required properties as required constructor parameters or validated fields.\n- Use defaults only when the default is semantically safe, not merely convenient.\n- Use nullable only when the application can handle absence explicitly.\n- Keep properties classes small and focused by feature or external dependency.\n- Prefer type-safe wrappers such as `Duration`, `URI`, or enums when they clarify the contract.\n\n## Advanced Configuration Traps\n\n- Profile files merge; they do not behave like full replacement documents. Partial overrides can leave stale sibling values in place.\n- Empty string is not the same as missing value. Many runtime failures come from \"configured but blank\" secrets.\n- Nested objects can be partially bound, which may produce a shape that looks non-null but is still semantically invalid.\n- Environment-variable translation from `kebab-case` to uppercase underscore is easy to misread, especially for nested maps and lists.\n- `ignoreUnknownFields` or overly permissive binding can hide deployment drift.\n- A property that fails only in one environment may really be a templating or secret-injection problem, not a Spring binding problem.\n- Test overrides can mask missing production defaults if tests define properties more generously than runtime.\n- Dynamic refresh or cloud config introduces lifecycle questions: startup validation alone may not be enough if config can change after boot.\n\n## Spring Config Data Nuances\n\n- `spring.config.import`, profile groups, and `spring.config.activate.on-profile` can reshape the final config graph in ways that are not obvious from file names alone.\n- List replacement and map merge behavior differ. A partial override may replace a whole list while only merging a map subtree.\n- Placeholder resolution timing matters. A property can appear bound yet still fail later if it depends on an unavailable placeholder or secret source.\n- Deprecating or renaming configuration keys is a migration problem. If compatibility matters, plan aliases or a staged rollout instead of a hard rename.\n- Overusing `@Profile` on beans can make environment behavior harder to reason about than using one typed configuration model with feature flags or explicit toggles.\n\n## Expert Heuristics\n\n- Prefer one typed configuration class per external dependency or feature slice. Giant omnibus config classes become impossible to validate and evolve safely.\n- When the same property is set in several layers, document the intended owner. Hidden \"last writer wins\" behavior becomes operational debt fast.\n- If a config issue appears only after deploy, compare rendered manifests or effective environment variables before editing Kotlin classes.\n- If startup must fail on bad config, prove that with a test or smoke check. Teams often think they fail fast when they actually fail on first traffic.\n\n## Design Rules\n\n- Validate required configuration at startup whenever possible.\n- Keep secrets out of committed config examples unless obviously fake and explicitly marked.\n- Model profile intent explicitly: local developer convenience, test isolation, operational environments, and feature toggles are different concerns.\n- Prefer one source of truth for a property family. Duplicated definitions across profiles create drift fast.\n\n## Output Contract\n\nReturn these sections:\n\n- `Binding model`: how the properties should be represented in Kotlin.\n- `Source precedence`: where the effective value should come from.\n- `Root cause`: exact mismatch in key, type, profile, or source.\n- `Minimal fix`: the smallest safe file, code, or env change.\n- `Startup validation`: what must fail fast at boot.\n- `Verification`: how to prove the resolved config in the target environment.\n\n## Guardrails\n\n- Do not hardcode secrets.\n- Do not default required credentials to empty strings.\n- Do not use nullable everywhere just to make the binder happy.\n- Do not assume profile-specific files replace base config wholesale.\n- Do not fix a binding symptom while ignoring the underlying precedence or environment problem.\n\n## Quality Bar\n\nA good run of this skill leaves the configuration model easier to reason about across environments.\nA bad run \"fixes\" one YAML key while leaving nullability, precedence, and startup validation ambiguous.\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Make Kotlin Spring config predictable","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fconfiguration-properties-profiles-kotlin-safe",{"type":42,"children":43},"root",[44,52,75,82,87,93,143,149,215,221,264,270,327,333,383,389,412,418,441,447,452,521,527,555,561],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Configuration Properties Profiles Kotlin Safe",{"type":45,"tag":53,"props":54,"children":55},"p",{},[56,58,65,67,73],{"type":50,"value":57},"Source mapping: Tier 2 high-value 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-16",{"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},"Make configuration predictable across local, test, staging, and production environments.\nTreat configuration as typed application input, not as unstructured text.",{"type":45,"tag":76,"props":88,"children":90},{"id":89},"read-first",[91],{"type":50,"value":92},"Read First",{"type":45,"tag":94,"props":95,"children":96},"ul",{},[97,117,128,133,138],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101,107,109,115],{"type":45,"tag":59,"props":102,"children":104},{"className":103},[],[105],{"type":50,"value":106},"application.yml",{"type":50,"value":108},", ",{"type":45,"tag":59,"props":110,"children":112},{"className":111},[],[113],{"type":50,"value":114},"application.properties",{"type":50,"value":116},", and profile-specific files.",{"type":45,"tag":98,"props":118,"children":119},{},[120,126],{"type":45,"tag":59,"props":121,"children":123},{"className":122},[],[124],{"type":50,"value":125},"@ConfigurationProperties",{"type":50,"value":127}," classes and how they are registered.",{"type":45,"tag":98,"props":129,"children":130},{},[131],{"type":50,"value":132},"Environment variable names, Helm values, Config Server or Vault usage, and test overrides.",{"type":45,"tag":98,"props":134,"children":135},{},[136],{"type":50,"value":137},"Active profile configuration and profile groups.",{"type":45,"tag":98,"props":139,"children":140},{},[141],{"type":50,"value":142},"Any custom converters, property placeholders, or late-bound secret conventions.",{"type":45,"tag":76,"props":144,"children":146},{"id":145},"diagnose-in-this-order",[147],{"type":50,"value":148},"Diagnose In This Order",{"type":45,"tag":150,"props":151,"children":152},"ol",{},[153,190,195,200,205,210],{"type":45,"tag":98,"props":154,"children":155},{},[156,158],{"type":50,"value":157},"Verify source precedence:\n",{"type":45,"tag":94,"props":159,"children":160},{},[161,166,171,176,185],{"type":45,"tag":98,"props":162,"children":163},{},[164],{"type":50,"value":165},"default config file",{"type":45,"tag":98,"props":167,"children":168},{},[169],{"type":50,"value":170},"profile-specific file",{"type":45,"tag":98,"props":172,"children":173},{},[174],{"type":50,"value":175},"environment variables",{"type":45,"tag":98,"props":177,"children":178},{},[179],{"type":45,"tag":59,"props":180,"children":182},{"className":181},[],[183],{"type":50,"value":184},"SPRING_APPLICATION_JSON",{"type":45,"tag":98,"props":186,"children":187},{},[188],{"type":50,"value":189},"external config systems",{"type":45,"tag":98,"props":191,"children":192},{},[193],{"type":50,"value":194},"Verify prefix mapping and key shape.",{"type":45,"tag":98,"props":196,"children":197},{},[198],{"type":50,"value":199},"Verify constructor binding, defaults, and nullability.",{"type":45,"tag":98,"props":201,"children":202},{},[203],{"type":50,"value":204},"Verify collection, map, nested object, duration, and data-size binding.",{"type":45,"tag":98,"props":206,"children":207},{},[208],{"type":50,"value":209},"Verify profile activation and profile merge behavior.",{"type":45,"tag":98,"props":211,"children":212},{},[213],{"type":50,"value":214},"Verify whether the bug exists only in tests or only in deployment templates.",{"type":45,"tag":76,"props":216,"children":218},{"id":217},"kotlin-safe-modeling-rules",[219],{"type":50,"value":220},"Kotlin-Safe Modeling Rules",{"type":45,"tag":94,"props":222,"children":223},{},[224,229,234,239,244],{"type":45,"tag":98,"props":225,"children":226},{},[227],{"type":50,"value":228},"Model genuinely required properties as required constructor parameters or validated fields.",{"type":45,"tag":98,"props":230,"children":231},{},[232],{"type":50,"value":233},"Use defaults only when the default is semantically safe, not merely convenient.",{"type":45,"tag":98,"props":235,"children":236},{},[237],{"type":50,"value":238},"Use nullable only when the application can handle absence explicitly.",{"type":45,"tag":98,"props":240,"children":241},{},[242],{"type":50,"value":243},"Keep properties classes small and focused by feature or external dependency.",{"type":45,"tag":98,"props":245,"children":246},{},[247,249,255,256,262],{"type":50,"value":248},"Prefer type-safe wrappers such as ",{"type":45,"tag":59,"props":250,"children":252},{"className":251},[],[253],{"type":50,"value":254},"Duration",{"type":50,"value":108},{"type":45,"tag":59,"props":257,"children":259},{"className":258},[],[260],{"type":50,"value":261},"URI",{"type":50,"value":263},", or enums when they clarify the contract.",{"type":45,"tag":76,"props":265,"children":267},{"id":266},"advanced-configuration-traps",[268],{"type":50,"value":269},"Advanced Configuration Traps",{"type":45,"tag":94,"props":271,"children":272},{},[273,278,283,288,301,312,317,322],{"type":45,"tag":98,"props":274,"children":275},{},[276],{"type":50,"value":277},"Profile files merge; they do not behave like full replacement documents. Partial overrides can leave stale sibling values in place.",{"type":45,"tag":98,"props":279,"children":280},{},[281],{"type":50,"value":282},"Empty string is not the same as missing value. Many runtime failures come from \"configured but blank\" secrets.",{"type":45,"tag":98,"props":284,"children":285},{},[286],{"type":50,"value":287},"Nested objects can be partially bound, which may produce a shape that looks non-null but is still semantically invalid.",{"type":45,"tag":98,"props":289,"children":290},{},[291,293,299],{"type":50,"value":292},"Environment-variable translation from ",{"type":45,"tag":59,"props":294,"children":296},{"className":295},[],[297],{"type":50,"value":298},"kebab-case",{"type":50,"value":300}," to uppercase underscore is easy to misread, especially for nested maps and lists.",{"type":45,"tag":98,"props":302,"children":303},{},[304,310],{"type":45,"tag":59,"props":305,"children":307},{"className":306},[],[308],{"type":50,"value":309},"ignoreUnknownFields",{"type":50,"value":311}," or overly permissive binding can hide deployment drift.",{"type":45,"tag":98,"props":313,"children":314},{},[315],{"type":50,"value":316},"A property that fails only in one environment may really be a templating or secret-injection problem, not a Spring binding problem.",{"type":45,"tag":98,"props":318,"children":319},{},[320],{"type":50,"value":321},"Test overrides can mask missing production defaults if tests define properties more generously than runtime.",{"type":45,"tag":98,"props":323,"children":324},{},[325],{"type":50,"value":326},"Dynamic refresh or cloud config introduces lifecycle questions: startup validation alone may not be enough if config can change after boot.",{"type":45,"tag":76,"props":328,"children":330},{"id":329},"spring-config-data-nuances",[331],{"type":50,"value":332},"Spring Config Data Nuances",{"type":45,"tag":94,"props":334,"children":335},{},[336,355,360,365,370],{"type":45,"tag":98,"props":337,"children":338},{},[339,345,347,353],{"type":45,"tag":59,"props":340,"children":342},{"className":341},[],[343],{"type":50,"value":344},"spring.config.import",{"type":50,"value":346},", profile groups, and ",{"type":45,"tag":59,"props":348,"children":350},{"className":349},[],[351],{"type":50,"value":352},"spring.config.activate.on-profile",{"type":50,"value":354}," can reshape the final config graph in ways that are not obvious from file names alone.",{"type":45,"tag":98,"props":356,"children":357},{},[358],{"type":50,"value":359},"List replacement and map merge behavior differ. A partial override may replace a whole list while only merging a map subtree.",{"type":45,"tag":98,"props":361,"children":362},{},[363],{"type":50,"value":364},"Placeholder resolution timing matters. A property can appear bound yet still fail later if it depends on an unavailable placeholder or secret source.",{"type":45,"tag":98,"props":366,"children":367},{},[368],{"type":50,"value":369},"Deprecating or renaming configuration keys is a migration problem. If compatibility matters, plan aliases or a staged rollout instead of a hard rename.",{"type":45,"tag":98,"props":371,"children":372},{},[373,375,381],{"type":50,"value":374},"Overusing ",{"type":45,"tag":59,"props":376,"children":378},{"className":377},[],[379],{"type":50,"value":380},"@Profile",{"type":50,"value":382}," on beans can make environment behavior harder to reason about than using one typed configuration model with feature flags or explicit toggles.",{"type":45,"tag":76,"props":384,"children":386},{"id":385},"expert-heuristics",[387],{"type":50,"value":388},"Expert Heuristics",{"type":45,"tag":94,"props":390,"children":391},{},[392,397,402,407],{"type":45,"tag":98,"props":393,"children":394},{},[395],{"type":50,"value":396},"Prefer one typed configuration class per external dependency or feature slice. Giant omnibus config classes become impossible to validate and evolve safely.",{"type":45,"tag":98,"props":398,"children":399},{},[400],{"type":50,"value":401},"When the same property is set in several layers, document the intended owner. Hidden \"last writer wins\" behavior becomes operational debt fast.",{"type":45,"tag":98,"props":403,"children":404},{},[405],{"type":50,"value":406},"If a config issue appears only after deploy, compare rendered manifests or effective environment variables before editing Kotlin classes.",{"type":45,"tag":98,"props":408,"children":409},{},[410],{"type":50,"value":411},"If startup must fail on bad config, prove that with a test or smoke check. Teams often think they fail fast when they actually fail on first traffic.",{"type":45,"tag":76,"props":413,"children":415},{"id":414},"design-rules",[416],{"type":50,"value":417},"Design Rules",{"type":45,"tag":94,"props":419,"children":420},{},[421,426,431,436],{"type":45,"tag":98,"props":422,"children":423},{},[424],{"type":50,"value":425},"Validate required configuration at startup whenever possible.",{"type":45,"tag":98,"props":427,"children":428},{},[429],{"type":50,"value":430},"Keep secrets out of committed config examples unless obviously fake and explicitly marked.",{"type":45,"tag":98,"props":432,"children":433},{},[434],{"type":50,"value":435},"Model profile intent explicitly: local developer convenience, test isolation, operational environments, and feature toggles are different concerns.",{"type":45,"tag":98,"props":437,"children":438},{},[439],{"type":50,"value":440},"Prefer one source of truth for a property family. Duplicated definitions across profiles create drift fast.",{"type":45,"tag":76,"props":442,"children":444},{"id":443},"output-contract",[445],{"type":50,"value":446},"Output Contract",{"type":45,"tag":53,"props":448,"children":449},{},[450],{"type":50,"value":451},"Return these sections:",{"type":45,"tag":94,"props":453,"children":454},{},[455,466,477,488,499,510],{"type":45,"tag":98,"props":456,"children":457},{},[458,464],{"type":45,"tag":59,"props":459,"children":461},{"className":460},[],[462],{"type":50,"value":463},"Binding model",{"type":50,"value":465},": how the properties should be represented in Kotlin.",{"type":45,"tag":98,"props":467,"children":468},{},[469,475],{"type":45,"tag":59,"props":470,"children":472},{"className":471},[],[473],{"type":50,"value":474},"Source precedence",{"type":50,"value":476},": where the effective value should come from.",{"type":45,"tag":98,"props":478,"children":479},{},[480,486],{"type":45,"tag":59,"props":481,"children":483},{"className":482},[],[484],{"type":50,"value":485},"Root cause",{"type":50,"value":487},": exact mismatch in key, type, profile, or source.",{"type":45,"tag":98,"props":489,"children":490},{},[491,497],{"type":45,"tag":59,"props":492,"children":494},{"className":493},[],[495],{"type":50,"value":496},"Minimal fix",{"type":50,"value":498},": the smallest safe file, code, or env change.",{"type":45,"tag":98,"props":500,"children":501},{},[502,508],{"type":45,"tag":59,"props":503,"children":505},{"className":504},[],[506],{"type":50,"value":507},"Startup validation",{"type":50,"value":509},": what must fail fast at boot.",{"type":45,"tag":98,"props":511,"children":512},{},[513,519],{"type":45,"tag":59,"props":514,"children":516},{"className":515},[],[517],{"type":50,"value":518},"Verification",{"type":50,"value":520},": how to prove the resolved config in the target environment.",{"type":45,"tag":76,"props":522,"children":524},{"id":523},"guardrails",[525],{"type":50,"value":526},"Guardrails",{"type":45,"tag":94,"props":528,"children":529},{},[530,535,540,545,550],{"type":45,"tag":98,"props":531,"children":532},{},[533],{"type":50,"value":534},"Do not hardcode secrets.",{"type":45,"tag":98,"props":536,"children":537},{},[538],{"type":50,"value":539},"Do not default required credentials to empty strings.",{"type":45,"tag":98,"props":541,"children":542},{},[543],{"type":50,"value":544},"Do not use nullable everywhere just to make the binder happy.",{"type":45,"tag":98,"props":546,"children":547},{},[548],{"type":50,"value":549},"Do not assume profile-specific files replace base config wholesale.",{"type":45,"tag":98,"props":551,"children":552},{},[553],{"type":50,"value":554},"Do not fix a binding symptom while ignoring the underlying precedence or environment problem.",{"type":45,"tag":76,"props":556,"children":558},{"id":557},"quality-bar",[559],{"type":50,"value":560},"Quality Bar",{"type":45,"tag":53,"props":562,"children":563},{},[564],{"type":50,"value":565},"A good run of this skill leaves the configuration model easier to reason about across environments.\nA bad run \"fixes\" one YAML key while leaving nullability, precedence, and startup validation ambiguous.",{"items":567,"total":685},[568,587,602,618,633,652,669],{"slug":569,"name":569,"fn":570,"description":571,"org":572,"tags":573,"stars":25,"repoUrl":26,"updatedAt":586},"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},[574,577,580,583],{"name":575,"slug":576,"type":15},"Creative","creative",{"name":578,"slug":579,"type":15},"Generative Art","generative-art",{"name":581,"slug":582,"type":15},"Graphics","graphics",{"name":584,"slug":585,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":588,"name":588,"fn":589,"description":590,"org":591,"tags":592,"stars":25,"repoUrl":26,"updatedAt":601},"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},[593,596,597,598],{"name":594,"slug":595,"type":15},"Best Practices","best-practices",{"name":23,"slug":24,"type":15},{"name":584,"slug":585,"type":15},{"name":599,"slug":600,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":603,"name":603,"fn":604,"description":605,"org":606,"tags":607,"stars":25,"repoUrl":26,"updatedAt":617},"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},[608,611,614],{"name":609,"slug":610,"type":15},"Branding","branding",{"name":612,"slug":613,"type":15},"Design","design",{"name":615,"slug":616,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":619,"name":619,"fn":620,"description":621,"org":622,"tags":623,"stars":25,"repoUrl":26,"updatedAt":632},"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},[624,625,626,629],{"name":575,"slug":576,"type":15},{"name":612,"slug":613,"type":15},{"name":627,"slug":628,"type":15},"Images","images",{"name":630,"slug":631,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":634,"name":634,"fn":635,"description":636,"org":637,"tags":638,"stars":25,"repoUrl":26,"updatedAt":651},"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},[639,642,645,648,649,650],{"name":640,"slug":641,"type":15},"CI\u002FCD","ci-cd",{"name":643,"slug":644,"type":15},"Containers","containers",{"name":646,"slug":647,"type":15},"Deployment","deployment",{"name":23,"slug":24,"type":15},{"name":13,"slug":14,"type":15},{"name":20,"slug":21,"type":15},"2026-07-13T06:41:47.83899",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":25,"repoUrl":26,"updatedAt":668},"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},[658,661,664,667],{"name":659,"slug":660,"type":15},"Cloudflare","cloudflare",{"name":662,"slug":663,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":665,"slug":666,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":646,"slug":647,"type":15},"2026-07-17T06:04:42.853896",{"slug":670,"name":670,"fn":671,"description":672,"org":673,"tags":674,"stars":25,"repoUrl":26,"updatedAt":684},"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},[675,678,681],{"name":676,"slug":677,"type":15},"Automation","automation",{"name":679,"slug":680,"type":15},"Desktop","desktop",{"name":682,"slug":683,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":687,"total":810},[688,702,711,720,731,741,750,759,768,778,787,800],{"slug":689,"name":689,"fn":690,"description":691,"org":692,"tags":693,"stars":699,"repoUrl":700,"updatedAt":701},"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},[694,697,698],{"name":695,"slug":696,"type":15},"Architecture","architecture",{"name":17,"slug":18,"type":15},{"name":23,"slug":24,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":703,"name":703,"fn":704,"description":705,"org":706,"tags":707,"stars":699,"repoUrl":700,"updatedAt":710},"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},[708,709],{"name":695,"slug":696,"type":15},{"name":23,"slug":24,"type":15},"2026-07-17T06:04:48.066901",{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":699,"repoUrl":700,"updatedAt":719},"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},[717,718],{"name":695,"slug":696,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:45:21.757084",{"slug":721,"name":721,"fn":722,"description":723,"org":724,"tags":725,"stars":699,"repoUrl":700,"updatedAt":730},"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},[726,727],{"name":695,"slug":696,"type":15},{"name":728,"slug":729,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":732,"name":732,"fn":733,"description":734,"org":735,"tags":736,"stars":699,"repoUrl":700,"updatedAt":740},"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},[737],{"name":738,"slug":739,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":742,"name":742,"fn":743,"description":744,"org":745,"tags":746,"stars":699,"repoUrl":700,"updatedAt":749},"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},[747,748],{"name":612,"slug":613,"type":15},{"name":682,"slug":683,"type":15},"2026-07-23T05:41:56.638151",{"slug":751,"name":751,"fn":752,"description":753,"org":754,"tags":755,"stars":699,"repoUrl":700,"updatedAt":758},"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},[756,757],{"name":23,"slug":24,"type":15},{"name":682,"slug":683,"type":15},"2026-07-23T05:41:49.666535",{"slug":760,"name":760,"fn":761,"description":762,"org":763,"tags":764,"stars":699,"repoUrl":700,"updatedAt":767},"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},[765,766],{"name":695,"slug":696,"type":15},{"name":23,"slug":24,"type":15},"2026-07-13T06:44:59.507855",{"slug":769,"name":769,"fn":770,"description":771,"org":772,"tags":773,"stars":699,"repoUrl":700,"updatedAt":777},"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},[774,775,776],{"name":695,"slug":696,"type":15},{"name":728,"slug":729,"type":15},{"name":23,"slug":24,"type":15},"2026-07-17T06:06:58.042999",{"slug":779,"name":779,"fn":780,"description":781,"org":782,"tags":783,"stars":699,"repoUrl":700,"updatedAt":786},"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},[784,785],{"name":695,"slug":696,"type":15},{"name":23,"slug":24,"type":15},"2026-07-23T05:41:48.692899",{"slug":788,"name":788,"fn":789,"description":790,"org":791,"tags":792,"stars":699,"repoUrl":700,"updatedAt":799},"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},[793,796],{"name":794,"slug":795,"type":15},"Debugging","debugging",{"name":797,"slug":798,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":801,"name":801,"fn":802,"description":803,"org":804,"tags":805,"stars":699,"repoUrl":700,"updatedAt":809},"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},[806],{"name":807,"slug":808,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]