[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-schema-migration-planner":3,"mdc-m74deb-key":36,"related-repo-jetbrains-schema-migration-planner":512,"related-org-jetbrains-schema-migration-planner":634},{"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},"schema-migration-planner","plan database schema migrations","Plan safe database schema evolution and zero-downtime change rollout for Kotlin plus Spring systems using Flyway, Liquibase, or equivalent migration tooling. Use when changing tables, columns, constraints, indexes, or data shape in systems with live traffic, rolling deploys, large datasets, or backward-compatibility requirements between old and new application versions.",{"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},"Spring","spring",{"name":20,"slug":21,"type":15},"Database","database",{"name":23,"slug":24,"type":15},"Migration","migration",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:40:59.733077",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\u002Fschema-migration-planner","---\nname: schema-migration-planner\ndescription: Plan safe database schema evolution and zero-downtime change rollout for Kotlin plus Spring systems using Flyway, Liquibase, or equivalent migration tooling. Use when changing tables, columns, constraints, indexes, or data shape in systems with live traffic, rolling deploys, large datasets, or backward-compatibility requirements between old and new application versions.\nmetadata:\n  short-description: \"Evolve schemas without breaking deploys\"\n  author: Kotlin\n  source: https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fschema-migration-planner\n---\n\n# Schema Migration Planner\n\nSource mapping: Tier 3 specialized skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-11`).\n\n## Mission\n\nChange schema without breaking live traffic, deployment order, or rollback safety.\nTreat schema evolution as a multi-step compatibility exercise, not a single DDL statement.\n\n## Read First\n\n- Current schema and the desired target shape.\n- Current code path, target code path, and deployment model.\n- Table sizes, traffic pattern, lock sensitivity, and replication or CDC constraints.\n- The actual migration tool and dialect in use.\n- Backfill capability, rollout windows, and rollback expectations.\n\n## Planning Workflow\n\n1. Identify whether the change is additive, destructive, semantic, or data-moving.\n2. Determine whether old and new application versions must coexist.\n3. Plan the rollout in phases:\n   - expand\n   - dual write or compatibility layer\n   - backfill\n   - switch reads\n   - contract\n4. Decide whether rollback is realistic or whether roll-forward is the safer operational model.\n5. Define smoke checks, validation queries, and observability around the migration.\n\n## Core Migration Rules\n\n- Add before remove.\n- Make old code tolerate new schema before making new code require it.\n- Backfill separately from latency-sensitive request paths whenever possible.\n- Use explicit indexes and constraints as part of the migration design, not as an afterthought.\n- Keep migration scripts deterministic and rerunnable according to the tool's expectations.\n\n## Advanced Migration Traps\n\n- Adding a non-null column with a default may rewrite or lock a large table depending on database and version. Small DDL can still be operationally expensive.\n- Unique constraints, index builds, and foreign-key validation can be more disruptive than column adds.\n- Backfills can saturate replicas, queue workers, caches, and downstream CDC consumers even when primary write latency looks fine.\n- Rolling deploys mean old and new code may both write for a while. Dual-write compatibility must be explicit.\n- Renames are usually additive-copy-switch-drop plans in disguise. Treat them that way.\n- Destructive clean-up should happen only after proving no old readers, writers, or reports still depend on the legacy shape.\n- Trigger-based compatibility shims can help but add operational complexity and hidden coupling. Use them knowingly.\n- Migration idempotency in tooling does not automatically mean business safety. Backfill scripts and data corrections need their own idempotency story.\n\n## Data Evolution Nuances\n\n- Type changes such as numeric widening, timezone reinterpretation, enum reshaping, or JSON-structure evolution can be more dangerous than simple adds and drops.\n- `NOT NULL` and uniqueness enforcement often need a staged approach: detect violations, clean data, validate constraint, then enforce strictly.\n- Backfill chunk size, ordering, pause or resume semantics, and checkpointing are part of the migration design for large tables.\n- Dual-read or shadow-read phases may be safer than immediate read switching when data transformation logic is non-trivial.\n- Online schema change tools or shadow-table strategies may be necessary when ordinary DDL locking is too expensive for the workload.\n- Replication lag and CDC downstream consumers can become the real bottleneck during backfill even when primary database metrics look acceptable.\n\n## Dialect And Tool Nuances\n\n- Online index creation, concurrent index build, and lock behavior are vendor-specific. Plan by dialect, not by generic SQL intuition.\n- Flyway and Liquibase have different strengths for rollback modeling, checksum handling, and branching workflows. Fit the plan to the tool already in use.\n- Some schema tools treat checksum drift and edited history harshly. Never rewrite applied migrations casually.\n- Partitioned tables, sharded systems, and CDC pipelines require migration plans that account for topology, not only DDL syntax.\n\n## Expert Heuristics\n\n- Prefer roll-forward designs over rollback fantasies when data shape already changed in production.\n- If the table is large or business-critical, separate compatibility change, data movement, and cleanup into different releases.\n- If a migration changes query shape, validate execution plans as part of the migration, not only schema correctness.\n- If zero downtime matters, prove compatibility between adjacent deploy versions explicitly.\n- Treat cleanup as a separate project step with an explicit proof threshold, not a footnote in the initial rollout plan.\n- Validate constraints against real production-shaped data before assuming the schema is enforceable.\n- If data correctness matters more than release speed, prefer longer coexistence windows over aggressive cleanup.\n- Make the migration observable: counters for rows backfilled, lag, retries, validation failures, and cutover readiness should exist before the dangerous step begins.\n\n## Output Contract\n\nReturn these sections:\n\n- `Schema change type`: additive, destructive, semantic, or data-moving.\n- `Phased migration plan`: the exact expand\u002Fcontract sequence.\n- `Compatibility story`: how old and new code coexist safely.\n- `Operational risks`: locks, backfill load, replication, CDC, or indexing risk.\n- `Verification`: SQL checks, smoke checks, and rollout checkpoints.\n- `Cleanup phase`: what can be removed later and under what proof.\n\n## Guardrails\n\n- Do not recommend direct destructive DDL on live systems without a phased plan.\n- Do not assume rollback is safe once data has been transformed.\n- Do not couple request latency to large backfills unless no other option exists.\n- Do not edit historical applied migrations casually.\n\n## Quality Bar\n\nA good run of this skill gives the team a deployable, compatibility-safe migration sequence with operational awareness.\nA bad run writes correct SQL that is still dangerous to run on a live system.\n",{"data":37,"body":41},{"name":4,"description":6,"metadata":38},{"short-description":39,"author":13,"source":40},"Evolve schemas without breaking deploys","https:\u002F\u002Fgithub.com\u002FKotlin\u002Fkotlin-backend-agent-skills\u002Ftree\u002Fmain\u002F.agents\u002Fskills\u002Fschema-migration-planner",{"type":42,"children":43},"root",[44,52,75,82,87,93,123,129,186,192,220,226,269,275,314,320,343,349,392,398,403,472,478,501,507],{"type":45,"tag":46,"props":47,"children":48},"element","h1",{"id":4},[49],{"type":50,"value":51},"text","Schema Migration Planner",{"type":45,"tag":53,"props":54,"children":55},"p",{},[56,58,65,67,73],{"type":50,"value":57},"Source mapping: Tier 3 specialized 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-11",{"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},"Change schema without breaking live traffic, deployment order, or rollback safety.\nTreat schema evolution as a multi-step compatibility exercise, not a single DDL statement.",{"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,103,108,113,118],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101],{"type":50,"value":102},"Current schema and the desired target shape.",{"type":45,"tag":98,"props":104,"children":105},{},[106],{"type":50,"value":107},"Current code path, target code path, and deployment model.",{"type":45,"tag":98,"props":109,"children":110},{},[111],{"type":50,"value":112},"Table sizes, traffic pattern, lock sensitivity, and replication or CDC constraints.",{"type":45,"tag":98,"props":114,"children":115},{},[116],{"type":50,"value":117},"The actual migration tool and dialect in use.",{"type":45,"tag":98,"props":119,"children":120},{},[121],{"type":50,"value":122},"Backfill capability, rollout windows, and rollback expectations.",{"type":45,"tag":76,"props":124,"children":126},{"id":125},"planning-workflow",[127],{"type":50,"value":128},"Planning Workflow",{"type":45,"tag":130,"props":131,"children":132},"ol",{},[133,138,143,176,181],{"type":45,"tag":98,"props":134,"children":135},{},[136],{"type":50,"value":137},"Identify whether the change is additive, destructive, semantic, or data-moving.",{"type":45,"tag":98,"props":139,"children":140},{},[141],{"type":50,"value":142},"Determine whether old and new application versions must coexist.",{"type":45,"tag":98,"props":144,"children":145},{},[146,148],{"type":50,"value":147},"Plan the rollout in phases:\n",{"type":45,"tag":94,"props":149,"children":150},{},[151,156,161,166,171],{"type":45,"tag":98,"props":152,"children":153},{},[154],{"type":50,"value":155},"expand",{"type":45,"tag":98,"props":157,"children":158},{},[159],{"type":50,"value":160},"dual write or compatibility layer",{"type":45,"tag":98,"props":162,"children":163},{},[164],{"type":50,"value":165},"backfill",{"type":45,"tag":98,"props":167,"children":168},{},[169],{"type":50,"value":170},"switch reads",{"type":45,"tag":98,"props":172,"children":173},{},[174],{"type":50,"value":175},"contract",{"type":45,"tag":98,"props":177,"children":178},{},[179],{"type":50,"value":180},"Decide whether rollback is realistic or whether roll-forward is the safer operational model.",{"type":45,"tag":98,"props":182,"children":183},{},[184],{"type":50,"value":185},"Define smoke checks, validation queries, and observability around the migration.",{"type":45,"tag":76,"props":187,"children":189},{"id":188},"core-migration-rules",[190],{"type":50,"value":191},"Core Migration Rules",{"type":45,"tag":94,"props":193,"children":194},{},[195,200,205,210,215],{"type":45,"tag":98,"props":196,"children":197},{},[198],{"type":50,"value":199},"Add before remove.",{"type":45,"tag":98,"props":201,"children":202},{},[203],{"type":50,"value":204},"Make old code tolerate new schema before making new code require it.",{"type":45,"tag":98,"props":206,"children":207},{},[208],{"type":50,"value":209},"Backfill separately from latency-sensitive request paths whenever possible.",{"type":45,"tag":98,"props":211,"children":212},{},[213],{"type":50,"value":214},"Use explicit indexes and constraints as part of the migration design, not as an afterthought.",{"type":45,"tag":98,"props":216,"children":217},{},[218],{"type":50,"value":219},"Keep migration scripts deterministic and rerunnable according to the tool's expectations.",{"type":45,"tag":76,"props":221,"children":223},{"id":222},"advanced-migration-traps",[224],{"type":50,"value":225},"Advanced Migration Traps",{"type":45,"tag":94,"props":227,"children":228},{},[229,234,239,244,249,254,259,264],{"type":45,"tag":98,"props":230,"children":231},{},[232],{"type":50,"value":233},"Adding a non-null column with a default may rewrite or lock a large table depending on database and version. Small DDL can still be operationally expensive.",{"type":45,"tag":98,"props":235,"children":236},{},[237],{"type":50,"value":238},"Unique constraints, index builds, and foreign-key validation can be more disruptive than column adds.",{"type":45,"tag":98,"props":240,"children":241},{},[242],{"type":50,"value":243},"Backfills can saturate replicas, queue workers, caches, and downstream CDC consumers even when primary write latency looks fine.",{"type":45,"tag":98,"props":245,"children":246},{},[247],{"type":50,"value":248},"Rolling deploys mean old and new code may both write for a while. Dual-write compatibility must be explicit.",{"type":45,"tag":98,"props":250,"children":251},{},[252],{"type":50,"value":253},"Renames are usually additive-copy-switch-drop plans in disguise. Treat them that way.",{"type":45,"tag":98,"props":255,"children":256},{},[257],{"type":50,"value":258},"Destructive clean-up should happen only after proving no old readers, writers, or reports still depend on the legacy shape.",{"type":45,"tag":98,"props":260,"children":261},{},[262],{"type":50,"value":263},"Trigger-based compatibility shims can help but add operational complexity and hidden coupling. Use them knowingly.",{"type":45,"tag":98,"props":265,"children":266},{},[267],{"type":50,"value":268},"Migration idempotency in tooling does not automatically mean business safety. Backfill scripts and data corrections need their own idempotency story.",{"type":45,"tag":76,"props":270,"children":272},{"id":271},"data-evolution-nuances",[273],{"type":50,"value":274},"Data Evolution Nuances",{"type":45,"tag":94,"props":276,"children":277},{},[278,283,294,299,304,309],{"type":45,"tag":98,"props":279,"children":280},{},[281],{"type":50,"value":282},"Type changes such as numeric widening, timezone reinterpretation, enum reshaping, or JSON-structure evolution can be more dangerous than simple adds and drops.",{"type":45,"tag":98,"props":284,"children":285},{},[286,292],{"type":45,"tag":59,"props":287,"children":289},{"className":288},[],[290],{"type":50,"value":291},"NOT NULL",{"type":50,"value":293}," and uniqueness enforcement often need a staged approach: detect violations, clean data, validate constraint, then enforce strictly.",{"type":45,"tag":98,"props":295,"children":296},{},[297],{"type":50,"value":298},"Backfill chunk size, ordering, pause or resume semantics, and checkpointing are part of the migration design for large tables.",{"type":45,"tag":98,"props":300,"children":301},{},[302],{"type":50,"value":303},"Dual-read or shadow-read phases may be safer than immediate read switching when data transformation logic is non-trivial.",{"type":45,"tag":98,"props":305,"children":306},{},[307],{"type":50,"value":308},"Online schema change tools or shadow-table strategies may be necessary when ordinary DDL locking is too expensive for the workload.",{"type":45,"tag":98,"props":310,"children":311},{},[312],{"type":50,"value":313},"Replication lag and CDC downstream consumers can become the real bottleneck during backfill even when primary database metrics look acceptable.",{"type":45,"tag":76,"props":315,"children":317},{"id":316},"dialect-and-tool-nuances",[318],{"type":50,"value":319},"Dialect And Tool Nuances",{"type":45,"tag":94,"props":321,"children":322},{},[323,328,333,338],{"type":45,"tag":98,"props":324,"children":325},{},[326],{"type":50,"value":327},"Online index creation, concurrent index build, and lock behavior are vendor-specific. Plan by dialect, not by generic SQL intuition.",{"type":45,"tag":98,"props":329,"children":330},{},[331],{"type":50,"value":332},"Flyway and Liquibase have different strengths for rollback modeling, checksum handling, and branching workflows. Fit the plan to the tool already in use.",{"type":45,"tag":98,"props":334,"children":335},{},[336],{"type":50,"value":337},"Some schema tools treat checksum drift and edited history harshly. Never rewrite applied migrations casually.",{"type":45,"tag":98,"props":339,"children":340},{},[341],{"type":50,"value":342},"Partitioned tables, sharded systems, and CDC pipelines require migration plans that account for topology, not only DDL syntax.",{"type":45,"tag":76,"props":344,"children":346},{"id":345},"expert-heuristics",[347],{"type":50,"value":348},"Expert Heuristics",{"type":45,"tag":94,"props":350,"children":351},{},[352,357,362,367,372,377,382,387],{"type":45,"tag":98,"props":353,"children":354},{},[355],{"type":50,"value":356},"Prefer roll-forward designs over rollback fantasies when data shape already changed in production.",{"type":45,"tag":98,"props":358,"children":359},{},[360],{"type":50,"value":361},"If the table is large or business-critical, separate compatibility change, data movement, and cleanup into different releases.",{"type":45,"tag":98,"props":363,"children":364},{},[365],{"type":50,"value":366},"If a migration changes query shape, validate execution plans as part of the migration, not only schema correctness.",{"type":45,"tag":98,"props":368,"children":369},{},[370],{"type":50,"value":371},"If zero downtime matters, prove compatibility between adjacent deploy versions explicitly.",{"type":45,"tag":98,"props":373,"children":374},{},[375],{"type":50,"value":376},"Treat cleanup as a separate project step with an explicit proof threshold, not a footnote in the initial rollout plan.",{"type":45,"tag":98,"props":378,"children":379},{},[380],{"type":50,"value":381},"Validate constraints against real production-shaped data before assuming the schema is enforceable.",{"type":45,"tag":98,"props":383,"children":384},{},[385],{"type":50,"value":386},"If data correctness matters more than release speed, prefer longer coexistence windows over aggressive cleanup.",{"type":45,"tag":98,"props":388,"children":389},{},[390],{"type":50,"value":391},"Make the migration observable: counters for rows backfilled, lag, retries, validation failures, and cutover readiness should exist before the dangerous step begins.",{"type":45,"tag":76,"props":393,"children":395},{"id":394},"output-contract",[396],{"type":50,"value":397},"Output Contract",{"type":45,"tag":53,"props":399,"children":400},{},[401],{"type":50,"value":402},"Return these sections:",{"type":45,"tag":94,"props":404,"children":405},{},[406,417,428,439,450,461],{"type":45,"tag":98,"props":407,"children":408},{},[409,415],{"type":45,"tag":59,"props":410,"children":412},{"className":411},[],[413],{"type":50,"value":414},"Schema change type",{"type":50,"value":416},": additive, destructive, semantic, or data-moving.",{"type":45,"tag":98,"props":418,"children":419},{},[420,426],{"type":45,"tag":59,"props":421,"children":423},{"className":422},[],[424],{"type":50,"value":425},"Phased migration plan",{"type":50,"value":427},": the exact expand\u002Fcontract sequence.",{"type":45,"tag":98,"props":429,"children":430},{},[431,437],{"type":45,"tag":59,"props":432,"children":434},{"className":433},[],[435],{"type":50,"value":436},"Compatibility story",{"type":50,"value":438},": how old and new code coexist safely.",{"type":45,"tag":98,"props":440,"children":441},{},[442,448],{"type":45,"tag":59,"props":443,"children":445},{"className":444},[],[446],{"type":50,"value":447},"Operational risks",{"type":50,"value":449},": locks, backfill load, replication, CDC, or indexing risk.",{"type":45,"tag":98,"props":451,"children":452},{},[453,459],{"type":45,"tag":59,"props":454,"children":456},{"className":455},[],[457],{"type":50,"value":458},"Verification",{"type":50,"value":460},": SQL checks, smoke checks, and rollout checkpoints.",{"type":45,"tag":98,"props":462,"children":463},{},[464,470],{"type":45,"tag":59,"props":465,"children":467},{"className":466},[],[468],{"type":50,"value":469},"Cleanup phase",{"type":50,"value":471},": what can be removed later and under what proof.",{"type":45,"tag":76,"props":473,"children":475},{"id":474},"guardrails",[476],{"type":50,"value":477},"Guardrails",{"type":45,"tag":94,"props":479,"children":480},{},[481,486,491,496],{"type":45,"tag":98,"props":482,"children":483},{},[484],{"type":50,"value":485},"Do not recommend direct destructive DDL on live systems without a phased plan.",{"type":45,"tag":98,"props":487,"children":488},{},[489],{"type":50,"value":490},"Do not assume rollback is safe once data has been transformed.",{"type":45,"tag":98,"props":492,"children":493},{},[494],{"type":50,"value":495},"Do not couple request latency to large backfills unless no other option exists.",{"type":45,"tag":98,"props":497,"children":498},{},[499],{"type":50,"value":500},"Do not edit historical applied migrations casually.",{"type":45,"tag":76,"props":502,"children":504},{"id":503},"quality-bar",[505],{"type":50,"value":506},"Quality Bar",{"type":45,"tag":53,"props":508,"children":509},{},[510],{"type":50,"value":511},"A good run of this skill gives the team a deployable, compatibility-safe migration sequence with operational awareness.\nA bad run writes correct SQL that is still dangerous to run on a live system.",{"items":513,"total":633},[514,533,550,566,581,600,617],{"slug":515,"name":515,"fn":516,"description":517,"org":518,"tags":519,"stars":25,"repoUrl":26,"updatedAt":532},"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},[520,523,526,529],{"name":521,"slug":522,"type":15},"Creative","creative",{"name":524,"slug":525,"type":15},"Generative Art","generative-art",{"name":527,"slug":528,"type":15},"Graphics","graphics",{"name":530,"slug":531,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":534,"name":534,"fn":535,"description":536,"org":537,"tags":538,"stars":25,"repoUrl":26,"updatedAt":549},"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},[539,542,545,546],{"name":540,"slug":541,"type":15},"Best Practices","best-practices",{"name":543,"slug":544,"type":15},"Engineering","engineering",{"name":530,"slug":531,"type":15},{"name":547,"slug":548,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":25,"repoUrl":26,"updatedAt":565},"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},[556,559,562],{"name":557,"slug":558,"type":15},"Branding","branding",{"name":560,"slug":561,"type":15},"Design","design",{"name":563,"slug":564,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":567,"name":567,"fn":568,"description":569,"org":570,"tags":571,"stars":25,"repoUrl":26,"updatedAt":580},"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},[572,573,574,577],{"name":521,"slug":522,"type":15},{"name":560,"slug":561,"type":15},{"name":575,"slug":576,"type":15},"Images","images",{"name":578,"slug":579,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":582,"name":582,"fn":583,"description":584,"org":585,"tags":586,"stars":25,"repoUrl":26,"updatedAt":599},"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},[587,590,593,596,597,598],{"name":588,"slug":589,"type":15},"CI\u002FCD","ci-cd",{"name":591,"slug":592,"type":15},"Containers","containers",{"name":594,"slug":595,"type":15},"Deployment","deployment",{"name":543,"slug":544,"type":15},{"name":13,"slug":14,"type":15},{"name":17,"slug":18,"type":15},"2026-07-13T06:41:47.83899",{"slug":601,"name":601,"fn":602,"description":603,"org":604,"tags":605,"stars":25,"repoUrl":26,"updatedAt":616},"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},[606,609,612,615],{"name":607,"slug":608,"type":15},"Cloudflare","cloudflare",{"name":610,"slug":611,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":613,"slug":614,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":594,"slug":595,"type":15},"2026-07-17T06:04:42.853896",{"slug":618,"name":618,"fn":619,"description":620,"org":621,"tags":622,"stars":25,"repoUrl":26,"updatedAt":632},"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},[623,626,629],{"name":624,"slug":625,"type":15},"Automation","automation",{"name":627,"slug":628,"type":15},"Desktop","desktop",{"name":630,"slug":631,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":635,"total":758},[636,652,661,670,681,691,700,709,718,728,737,748],{"slug":637,"name":637,"fn":638,"description":639,"org":640,"tags":641,"stars":649,"repoUrl":650,"updatedAt":651},"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},[642,645,648],{"name":643,"slug":644,"type":15},"Architecture","architecture",{"name":646,"slug":647,"type":15},"Configuration","configuration",{"name":543,"slug":544,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":653,"name":653,"fn":654,"description":655,"org":656,"tags":657,"stars":649,"repoUrl":650,"updatedAt":660},"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},[658,659],{"name":643,"slug":644,"type":15},{"name":543,"slug":544,"type":15},"2026-07-17T06:04:48.066901",{"slug":662,"name":662,"fn":663,"description":664,"org":665,"tags":666,"stars":649,"repoUrl":650,"updatedAt":669},"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},[667,668],{"name":643,"slug":644,"type":15},{"name":543,"slug":544,"type":15},"2026-07-13T06:45:21.757084",{"slug":671,"name":671,"fn":672,"description":673,"org":674,"tags":675,"stars":649,"repoUrl":650,"updatedAt":680},"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},[676,677],{"name":643,"slug":644,"type":15},{"name":678,"slug":679,"type":15},"Code Analysis","code-analysis","2026-07-23T05:41:33.639365",{"slug":682,"name":682,"fn":683,"description":684,"org":685,"tags":686,"stars":649,"repoUrl":650,"updatedAt":690},"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},[687],{"name":688,"slug":689,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":692,"name":692,"fn":693,"description":694,"org":695,"tags":696,"stars":649,"repoUrl":650,"updatedAt":699},"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},[697,698],{"name":560,"slug":561,"type":15},{"name":630,"slug":631,"type":15},"2026-07-23T05:41:56.638151",{"slug":701,"name":701,"fn":702,"description":703,"org":704,"tags":705,"stars":649,"repoUrl":650,"updatedAt":708},"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},[706,707],{"name":543,"slug":544,"type":15},{"name":630,"slug":631,"type":15},"2026-07-23T05:41:49.666535",{"slug":710,"name":710,"fn":711,"description":712,"org":713,"tags":714,"stars":649,"repoUrl":650,"updatedAt":717},"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},[715,716],{"name":643,"slug":644,"type":15},{"name":543,"slug":544,"type":15},"2026-07-13T06:44:59.507855",{"slug":719,"name":719,"fn":720,"description":721,"org":722,"tags":723,"stars":649,"repoUrl":650,"updatedAt":727},"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},[724,725,726],{"name":643,"slug":644,"type":15},{"name":678,"slug":679,"type":15},{"name":543,"slug":544,"type":15},"2026-07-17T06:06:58.042999",{"slug":729,"name":729,"fn":730,"description":731,"org":732,"tags":733,"stars":649,"repoUrl":650,"updatedAt":736},"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},[734,735],{"name":643,"slug":644,"type":15},{"name":543,"slug":544,"type":15},"2026-07-23T05:41:48.692899",{"slug":738,"name":738,"fn":739,"description":740,"org":741,"tags":742,"stars":649,"repoUrl":650,"updatedAt":747},"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},[743,746],{"name":744,"slug":745,"type":15},"Debugging","debugging",{"name":23,"slug":24,"type":15},"2026-07-13T06:45:20.372122",{"slug":749,"name":749,"fn":750,"description":751,"org":752,"tags":753,"stars":649,"repoUrl":650,"updatedAt":757},"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},[754],{"name":755,"slug":756,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]