[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-jetbrains-security-threat-model":3,"mdc--f0cl0o-key":33,"related-repo-jetbrains-security-threat-model":430,"related-org-jetbrains-security-threat-model":556},{"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},"security-threat-model","perform repository-grounded security threat modeling","Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.",{"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},"Security","security","tag",{"name":17,"slug":18,"type":15},"Threat Modeling","threat-modeling",{"name":20,"slug":21,"type":15},"Code Analysis","code-analysis",252,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002Fskills","2026-07-13T06:42:55.192758",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\u002Fsecurity-threat-model","---\nname: \"security-threat-model\"\ndescription: \"Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats\u002Fabuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.\"\nmetadata:\n  short-description: \"Repo-grounded threat modeling and abuse-path analysis\"\n  author: OpenAI\n  source: https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002F.curated\u002Fsecurity-threat-model\n---\n\n# Threat Model Source Code Repo\n\nDeliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.\n\n## Quick start\n\n1) Collect (or infer) inputs:\n- Repo root path and any in-scope paths.\n- Intended usage, deployment model, internet exposure, and auth expectations (if known).\n- Any existing repository summary or architecture spec.\n- Use prompts in `references\u002Fprompt-template.md` to generate a repository summary.\n- Follow the required output contract in `references\u002Fprompt-template.md`. Use it verbatim when possible.\n\n## Workflow\n\n### 1) Scope and extract the system model\n- Identify primary components, data stores, and external integrations from the repo summary.\n- Identify how the system runs (server, CLI, library, worker) and its entrypoints.\n- Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.\n- Map the in-scope locations to those components and exclude out-of-scope items explicitly.\n- Do not claim components, flows, or controls without evidence.\n\n### 2) Derive boundaries, assets, and entry points\n- Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.\n- List assets that drive risk (data, credentials, models, config, compute resources, audit logs).\n- Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).\n\n### 3) Calibrate assets and attacker capabilities\n- List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).\n- Describe realistic attacker capabilities based on exposure and intended usage.\n- Explicitly note non-capabilities to avoid inflated severity.\n\n\n### 4) Enumerate threats as abuse paths\n- Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).\n- Classify each threat and tie it to impacted assets.\n- Keep the number of threats small but high quality.\n\n### 5) Prioritize with explicit likelihood and impact reasoning\n- Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.\n- Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.\n- State which assumptions most influence the ranking.\n\n### 6) Validate service context and assumptions with the user\n- Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.\n- Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).\n- Pause and wait for user feedback before producing the final report.\n- If the user declines or can’t answer, state which assumptions remain and how they influence priority.\n\n### 7) Recommend mitigations and focus paths\n- Distinguish existing mitigations (with evidence) from recommended mitigations.\n- Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).\n- Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").\n- Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.\n\n### 8) Run a quality check before finalizing\n- Confirm all discovered entrypoints are covered.\n- Confirm each trust boundary is represented in threats.\n- Confirm runtime vs CI\u002Fdev separation.\n- Confirm user clarifications (or explicit non-responses) are reflected.\n- Confirm assumptions and open questions are explicit.\n- Confirm that the format of the report matches closely the required output format defined in prompt template: `references\u002Fprompt-template.md`\n- Write the final Markdown to a file named `\u003Crepo-or-dir-name>-threat-model.md` (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).\n\n\n## Risk prioritization guidance (illustrative, not exhaustive)\n- High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.\n- Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.\n- Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.\n\n## References\n\n- Output contract and full prompt template: `references\u002Fprompt-template.md`\n- Optional controls\u002Fasset list: `references\u002Fsecurity-controls-and-assets.md`\n\nOnly load the reference files you need. Keep the final result concise, grounded, and reviewable.\n",{"data":34,"body":39},{"name":4,"description":6,"metadata":35},{"short-description":36,"author":37,"source":38},"Repo-grounded threat modeling and abuse-path analysis","OpenAI","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002F.curated\u002Fsecurity-threat-model",{"type":40,"children":41},"root",[42,51,57,64,74,119,125,132,160,166,184,190,208,214,232,238,256,262,285,291,314,320,371,377,395,401,425],{"type":43,"tag":44,"props":45,"children":47},"element","h1",{"id":46},"threat-model-source-code-repo",[48],{"type":49,"value":50},"text","Threat Model Source Code Repo",{"type":43,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"Deliver an actionable AppSec-grade threat model that is specific to the repository or a project path, not a generic checklist. Anchor every architectural claim to evidence in the repo and keep assumptions explicit. Prioritizing realistic attacker goals and concrete impacts over generic checklists.",{"type":43,"tag":58,"props":59,"children":61},"h2",{"id":60},"quick-start",[62],{"type":49,"value":63},"Quick start",{"type":43,"tag":65,"props":66,"children":67},"ol",{},[68],{"type":43,"tag":69,"props":70,"children":71},"li",{},[72],{"type":49,"value":73},"Collect (or infer) inputs:",{"type":43,"tag":75,"props":76,"children":77},"ul",{},[78,83,88,93,107],{"type":43,"tag":69,"props":79,"children":80},{},[81],{"type":49,"value":82},"Repo root path and any in-scope paths.",{"type":43,"tag":69,"props":84,"children":85},{},[86],{"type":49,"value":87},"Intended usage, deployment model, internet exposure, and auth expectations (if known).",{"type":43,"tag":69,"props":89,"children":90},{},[91],{"type":49,"value":92},"Any existing repository summary or architecture spec.",{"type":43,"tag":69,"props":94,"children":95},{},[96,98,105],{"type":49,"value":97},"Use prompts in ",{"type":43,"tag":99,"props":100,"children":102},"code",{"className":101},[],[103],{"type":49,"value":104},"references\u002Fprompt-template.md",{"type":49,"value":106}," to generate a repository summary.",{"type":43,"tag":69,"props":108,"children":109},{},[110,112,117],{"type":49,"value":111},"Follow the required output contract in ",{"type":43,"tag":99,"props":113,"children":115},{"className":114},[],[116],{"type":49,"value":104},{"type":49,"value":118},". Use it verbatim when possible.",{"type":43,"tag":58,"props":120,"children":122},{"id":121},"workflow",[123],{"type":49,"value":124},"Workflow",{"type":43,"tag":126,"props":127,"children":129},"h3",{"id":128},"_1-scope-and-extract-the-system-model",[130],{"type":49,"value":131},"1) Scope and extract the system model",{"type":43,"tag":75,"props":133,"children":134},{},[135,140,145,150,155],{"type":43,"tag":69,"props":136,"children":137},{},[138],{"type":49,"value":139},"Identify primary components, data stores, and external integrations from the repo summary.",{"type":43,"tag":69,"props":141,"children":142},{},[143],{"type":49,"value":144},"Identify how the system runs (server, CLI, library, worker) and its entrypoints.",{"type":43,"tag":69,"props":146,"children":147},{},[148],{"type":49,"value":149},"Separate runtime behavior from CI\u002Fbuild\u002Fdev tooling and from tests\u002Fexamples.",{"type":43,"tag":69,"props":151,"children":152},{},[153],{"type":49,"value":154},"Map the in-scope locations to those components and exclude out-of-scope items explicitly.",{"type":43,"tag":69,"props":156,"children":157},{},[158],{"type":49,"value":159},"Do not claim components, flows, or controls without evidence.",{"type":43,"tag":126,"props":161,"children":163},{"id":162},"_2-derive-boundaries-assets-and-entry-points",[164],{"type":49,"value":165},"2) Derive boundaries, assets, and entry points",{"type":43,"tag":75,"props":167,"children":168},{},[169,174,179],{"type":43,"tag":69,"props":170,"children":171},{},[172],{"type":49,"value":173},"Enumerate trust boundaries as concrete edges between components, noting protocol, auth, encryption, validation, and rate limiting.",{"type":43,"tag":69,"props":175,"children":176},{},[177],{"type":49,"value":178},"List assets that drive risk (data, credentials, models, config, compute resources, audit logs).",{"type":43,"tag":69,"props":180,"children":181},{},[182],{"type":49,"value":183},"Identify entry points (endpoints, upload surfaces, parsers\u002Fdecoders, job triggers, admin tooling, logging\u002Ferror sinks).",{"type":43,"tag":126,"props":185,"children":187},{"id":186},"_3-calibrate-assets-and-attacker-capabilities",[188],{"type":49,"value":189},"3) Calibrate assets and attacker capabilities",{"type":43,"tag":75,"props":191,"children":192},{},[193,198,203],{"type":43,"tag":69,"props":194,"children":195},{},[196],{"type":49,"value":197},"List the assets that drive risk (credentials, PII, integrity-critical state, availability-critical components, build artifacts).",{"type":43,"tag":69,"props":199,"children":200},{},[201],{"type":49,"value":202},"Describe realistic attacker capabilities based on exposure and intended usage.",{"type":43,"tag":69,"props":204,"children":205},{},[206],{"type":49,"value":207},"Explicitly note non-capabilities to avoid inflated severity.",{"type":43,"tag":126,"props":209,"children":211},{"id":210},"_4-enumerate-threats-as-abuse-paths",[212],{"type":49,"value":213},"4) Enumerate threats as abuse paths",{"type":43,"tag":75,"props":215,"children":216},{},[217,222,227],{"type":43,"tag":69,"props":218,"children":219},{},[220],{"type":49,"value":221},"Prefer attacker goals that map to assets and boundaries (exfiltration, privilege escalation, integrity compromise, denial of service).",{"type":43,"tag":69,"props":223,"children":224},{},[225],{"type":49,"value":226},"Classify each threat and tie it to impacted assets.",{"type":43,"tag":69,"props":228,"children":229},{},[230],{"type":49,"value":231},"Keep the number of threats small but high quality.",{"type":43,"tag":126,"props":233,"children":235},{"id":234},"_5-prioritize-with-explicit-likelihood-and-impact-reasoning",[236],{"type":49,"value":237},"5) Prioritize with explicit likelihood and impact reasoning",{"type":43,"tag":75,"props":239,"children":240},{},[241,246,251],{"type":43,"tag":69,"props":242,"children":243},{},[244],{"type":49,"value":245},"Use qualitative likelihood and impact (low\u002Fmedium\u002Fhigh) with short justifications.",{"type":43,"tag":69,"props":247,"children":248},{},[249],{"type":49,"value":250},"Set overall priority (critical\u002Fhigh\u002Fmedium\u002Flow) using likelihood x impact, adjusted for existing controls.",{"type":43,"tag":69,"props":252,"children":253},{},[254],{"type":49,"value":255},"State which assumptions most influence the ranking.",{"type":43,"tag":126,"props":257,"children":259},{"id":258},"_6-validate-service-context-and-assumptions-with-the-user",[260],{"type":49,"value":261},"6) Validate service context and assumptions with the user",{"type":43,"tag":75,"props":263,"children":264},{},[265,270,275,280],{"type":43,"tag":69,"props":266,"children":267},{},[268],{"type":49,"value":269},"Summarize key assumptions that materially affect threat ranking or scope, then ask the user to confirm or correct them.",{"type":43,"tag":69,"props":271,"children":272},{},[273],{"type":49,"value":274},"Ask 1–3 targeted questions to resolve missing context (service owner and environment, scale\u002Fusers, deployment model, authn\u002Fauthz, internet exposure, data sensitivity, multi-tenancy).",{"type":43,"tag":69,"props":276,"children":277},{},[278],{"type":49,"value":279},"Pause and wait for user feedback before producing the final report.",{"type":43,"tag":69,"props":281,"children":282},{},[283],{"type":49,"value":284},"If the user declines or can’t answer, state which assumptions remain and how they influence priority.",{"type":43,"tag":126,"props":286,"children":288},{"id":287},"_7-recommend-mitigations-and-focus-paths",[289],{"type":49,"value":290},"7) Recommend mitigations and focus paths",{"type":43,"tag":75,"props":292,"children":293},{},[294,299,304,309],{"type":43,"tag":69,"props":295,"children":296},{},[297],{"type":49,"value":298},"Distinguish existing mitigations (with evidence) from recommended mitigations.",{"type":43,"tag":69,"props":300,"children":301},{},[302],{"type":49,"value":303},"Tie mitigations to concrete locations (component, boundary, or entry point) and control types (authZ checks, input validation, schema enforcement, sandboxing, rate limits, secrets isolation, audit logging).",{"type":43,"tag":69,"props":305,"children":306},{},[307],{"type":49,"value":308},"Prefer specific implementation hints over generic advice (e.g., \"enforce schema at gateway for upload payloads\" vs \"validate inputs\").",{"type":43,"tag":69,"props":310,"children":311},{},[312],{"type":49,"value":313},"Base recommendations on validated user context; if assumptions remain unresolved, mark recommendations as conditional.",{"type":43,"tag":126,"props":315,"children":317},{"id":316},"_8-run-a-quality-check-before-finalizing",[318],{"type":49,"value":319},"8) Run a quality check before finalizing",{"type":43,"tag":75,"props":321,"children":322},{},[323,328,333,338,343,348,358],{"type":43,"tag":69,"props":324,"children":325},{},[326],{"type":49,"value":327},"Confirm all discovered entrypoints are covered.",{"type":43,"tag":69,"props":329,"children":330},{},[331],{"type":49,"value":332},"Confirm each trust boundary is represented in threats.",{"type":43,"tag":69,"props":334,"children":335},{},[336],{"type":49,"value":337},"Confirm runtime vs CI\u002Fdev separation.",{"type":43,"tag":69,"props":339,"children":340},{},[341],{"type":49,"value":342},"Confirm user clarifications (or explicit non-responses) are reflected.",{"type":43,"tag":69,"props":344,"children":345},{},[346],{"type":49,"value":347},"Confirm assumptions and open questions are explicit.",{"type":43,"tag":69,"props":349,"children":350},{},[351,353],{"type":49,"value":352},"Confirm that the format of the report matches closely the required output format defined in prompt template: ",{"type":43,"tag":99,"props":354,"children":356},{"className":355},[],[357],{"type":49,"value":104},{"type":43,"tag":69,"props":359,"children":360},{},[361,363,369],{"type":49,"value":362},"Write the final Markdown to a file named ",{"type":43,"tag":99,"props":364,"children":366},{"className":365},[],[367],{"type":49,"value":368},"\u003Crepo-or-dir-name>-threat-model.md",{"type":49,"value":370}," (use the basename of the repo root, or the in-scope directory if you were asked to model a subpath).",{"type":43,"tag":58,"props":372,"children":374},{"id":373},"risk-prioritization-guidance-illustrative-not-exhaustive",[375],{"type":49,"value":376},"Risk prioritization guidance (illustrative, not exhaustive)",{"type":43,"tag":75,"props":378,"children":379},{},[380,385,390],{"type":43,"tag":69,"props":381,"children":382},{},[383],{"type":49,"value":384},"High: pre-auth RCE, auth bypass, cross-tenant access, sensitive data exfiltration, key or token theft, model or config integrity compromise, sandbox escape.",{"type":43,"tag":69,"props":386,"children":387},{},[388],{"type":49,"value":389},"Medium: targeted DoS of critical components, partial data exposure, rate-limit bypass with measurable impact, log\u002Fmetrics poisoning that affects detection.",{"type":43,"tag":69,"props":391,"children":392},{},[393],{"type":49,"value":394},"Low: low-sensitivity info leaks, noisy DoS with easy mitigation, issues requiring unlikely preconditions.",{"type":43,"tag":58,"props":396,"children":398},{"id":397},"references",[399],{"type":49,"value":400},"References",{"type":43,"tag":75,"props":402,"children":403},{},[404,414],{"type":43,"tag":69,"props":405,"children":406},{},[407,409],{"type":49,"value":408},"Output contract and full prompt template: ",{"type":43,"tag":99,"props":410,"children":412},{"className":411},[],[413],{"type":49,"value":104},{"type":43,"tag":69,"props":415,"children":416},{},[417,419],{"type":49,"value":418},"Optional controls\u002Fasset list: ",{"type":43,"tag":99,"props":420,"children":422},{"className":421},[],[423],{"type":49,"value":424},"references\u002Fsecurity-controls-and-assets.md",{"type":43,"tag":52,"props":426,"children":427},{},[428],{"type":49,"value":429},"Only load the reference files you need. Keep the final result concise, grounded, and reviewable.",{"items":431,"total":555},[432,451,468,484,499,522,539],{"slug":433,"name":433,"fn":434,"description":435,"org":436,"tags":437,"stars":22,"repoUrl":23,"updatedAt":450},"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},[438,441,444,447],{"name":439,"slug":440,"type":15},"Creative","creative",{"name":442,"slug":443,"type":15},"Generative Art","generative-art",{"name":445,"slug":446,"type":15},"Graphics","graphics",{"name":448,"slug":449,"type":15},"JavaScript","javascript","2026-07-13T06:41:35.540127",{"slug":452,"name":452,"fn":453,"description":454,"org":455,"tags":456,"stars":22,"repoUrl":23,"updatedAt":467},"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},[457,460,463,464],{"name":458,"slug":459,"type":15},"Best Practices","best-practices",{"name":461,"slug":462,"type":15},"Engineering","engineering",{"name":448,"slug":449,"type":15},{"name":465,"slug":466,"type":15},"TypeScript","typescript","2026-07-13T06:43:13.153309",{"slug":469,"name":469,"fn":470,"description":471,"org":472,"tags":473,"stars":22,"repoUrl":23,"updatedAt":483},"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},[474,477,480],{"name":475,"slug":476,"type":15},"Branding","branding",{"name":478,"slug":479,"type":15},"Design","design",{"name":481,"slug":482,"type":15},"Typography","typography","2026-07-13T06:43:06.077629",{"slug":485,"name":485,"fn":486,"description":487,"org":488,"tags":489,"stars":22,"repoUrl":23,"updatedAt":498},"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},[490,491,492,495],{"name":439,"slug":440,"type":15},{"name":478,"slug":479,"type":15},{"name":493,"slug":494,"type":15},"Images","images",{"name":496,"slug":497,"type":15},"PDF","pdf","2026-07-13T06:39:58.803113",{"slug":500,"name":500,"fn":501,"description":502,"org":503,"tags":504,"stars":22,"repoUrl":23,"updatedAt":521},"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},[505,508,511,514,515,518],{"name":506,"slug":507,"type":15},"CI\u002FCD","ci-cd",{"name":509,"slug":510,"type":15},"Containers","containers",{"name":512,"slug":513,"type":15},"Deployment","deployment",{"name":461,"slug":462,"type":15},{"name":516,"slug":517,"type":15},"Kotlin","kotlin",{"name":519,"slug":520,"type":15},"Spring","spring","2026-07-13T06:41:47.83899",{"slug":523,"name":523,"fn":524,"description":525,"org":526,"tags":527,"stars":22,"repoUrl":23,"updatedAt":538},"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},[528,531,534,537],{"name":529,"slug":530,"type":15},"Cloudflare","cloudflare",{"name":532,"slug":533,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":535,"slug":536,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":512,"slug":513,"type":15},"2026-07-17T06:04:42.853896",{"slug":540,"name":540,"fn":541,"description":542,"org":543,"tags":544,"stars":22,"repoUrl":23,"updatedAt":554},"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},[545,548,551],{"name":546,"slug":547,"type":15},"Automation","automation",{"name":549,"slug":550,"type":15},"Desktop","desktop",{"name":552,"slug":553,"type":15},"UI Components","ui-components","2026-07-13T06:40:38.798626",128,{"items":557,"total":680},[558,574,583,592,601,611,620,629,638,648,657,670],{"slug":559,"name":559,"fn":560,"description":561,"org":562,"tags":563,"stars":571,"repoUrl":572,"updatedAt":573},"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},[564,567,570],{"name":565,"slug":566,"type":15},"Architecture","architecture",{"name":568,"slug":569,"type":15},"Configuration","configuration",{"name":461,"slug":462,"type":15},1650,"https:\u002F\u002Fgithub.com\u002FJetBrains\u002FMPS","2026-07-17T06:06:57.311661",{"slug":575,"name":575,"fn":576,"description":577,"org":578,"tags":579,"stars":571,"repoUrl":572,"updatedAt":582},"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},[580,581],{"name":565,"slug":566,"type":15},{"name":461,"slug":462,"type":15},"2026-07-17T06:04:48.066901",{"slug":584,"name":584,"fn":585,"description":586,"org":587,"tags":588,"stars":571,"repoUrl":572,"updatedAt":591},"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},[589,590],{"name":565,"slug":566,"type":15},{"name":461,"slug":462,"type":15},"2026-07-13T06:45:21.757084",{"slug":593,"name":593,"fn":594,"description":595,"org":596,"tags":597,"stars":571,"repoUrl":572,"updatedAt":600},"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},[598,599],{"name":565,"slug":566,"type":15},{"name":20,"slug":21,"type":15},"2026-07-23T05:41:33.639365",{"slug":602,"name":602,"fn":603,"description":604,"org":605,"tags":606,"stars":571,"repoUrl":572,"updatedAt":610},"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},[607],{"name":608,"slug":609,"type":15},"Data Analysis","data-analysis","2026-07-13T06:45:19.114674",{"slug":612,"name":612,"fn":613,"description":614,"org":615,"tags":616,"stars":571,"repoUrl":572,"updatedAt":619},"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},[617,618],{"name":478,"slug":479,"type":15},{"name":552,"slug":553,"type":15},"2026-07-23T05:41:56.638151",{"slug":621,"name":621,"fn":622,"description":623,"org":624,"tags":625,"stars":571,"repoUrl":572,"updatedAt":628},"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},[626,627],{"name":461,"slug":462,"type":15},{"name":552,"slug":553,"type":15},"2026-07-23T05:41:49.666535",{"slug":630,"name":630,"fn":631,"description":632,"org":633,"tags":634,"stars":571,"repoUrl":572,"updatedAt":637},"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},[635,636],{"name":565,"slug":566,"type":15},{"name":461,"slug":462,"type":15},"2026-07-13T06:44:59.507855",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":571,"repoUrl":572,"updatedAt":647},"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},[644,645,646],{"name":565,"slug":566,"type":15},{"name":20,"slug":21,"type":15},{"name":461,"slug":462,"type":15},"2026-07-17T06:06:58.042999",{"slug":649,"name":649,"fn":650,"description":651,"org":652,"tags":653,"stars":571,"repoUrl":572,"updatedAt":656},"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},[654,655],{"name":565,"slug":566,"type":15},{"name":461,"slug":462,"type":15},"2026-07-23T05:41:48.692899",{"slug":658,"name":658,"fn":659,"description":660,"org":661,"tags":662,"stars":571,"repoUrl":572,"updatedAt":669},"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},[663,666],{"name":664,"slug":665,"type":15},"Debugging","debugging",{"name":667,"slug":668,"type":15},"Migration","migration","2026-07-13T06:45:20.372122",{"slug":671,"name":671,"fn":672,"description":673,"org":674,"tags":675,"stars":571,"repoUrl":572,"updatedAt":679},"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},[676],{"name":677,"slug":678,"type":15},"Data Modeling","data-modeling","2026-07-23T05:41:30.705975",188]