[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78C930XWDPYCKXSFEKK8RNF":3,"skill-same:01M78C930XWDPYCKXSFEKK8RNF":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78C930XWDPYCKXSFEKK8RNF","cratis-screenplay-ui-composition",null,"Compose the user interface of a Cratis Screenplay `.play` model — `layout` and responsive `arrangement`, screen\u002Fdialog templates, component data-context bindings, exposed template configuration, command forms and columns, navigation contributions, application navigation regions (topbar\u002Fsidebar, module inherit\u002Fextend\u002Foverride), toolbar slice buttons, blueprint template references, sample data packs, hierarchical outlets\u002Froutes, toolbar dialogs, package\u002Ficon selection, interaction `behavior`\u002F`on`\u002F`uses` wiring, `ui profile` (root template, shell options, appearance, new screens default), `theme`, localized `$strings`, and `file` references. Use when declaring the application shell, reusable screen shapes, component\u002Fpackage configuration, command forms, navigation\u002Ftoolbars, click or submit behavior, or theming. Do not use for a screen's own data and actions.","Cratis\u002FPrologue","Cratis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16456213?v=4","01M6BXRH290K4C8RS4PTKK3HXQ","01M78C1YXTSPZGP4G1K2ZM6J1N",0,"MIT","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cratis-screenplay-ui-composition\ndescription: Compose the user interface of a Cratis Screenplay `.play` model — `layout` and responsive `arrangement`, screen\u002Fdialog templates, component data-context bindings, exposed template configuration, command forms and columns, navigation contributions, application navigation regions (topbar\u002Fsidebar, module inherit\u002Fextend\u002Foverride), toolbar slice buttons, blueprint template references, sample data packs, hierarchical outlets\u002Froutes, toolbar dialogs, package\u002Ficon selection, interaction `behavior`\u002F`on`\u002F`uses` wiring, `ui profile` (root template, shell options, appearance, new screens default), `theme`, localized `$strings`, and `file` references. Use when declaring the application shell, reusable screen shapes, component\u002Fpackage configuration, command forms, navigation\u002Ftoolbars, click or submit behavior, or theming. Do not use for a screen's own data and actions.\nlicense: MIT\n---\n\u003C!-- cratis-ai-managed: skills\u002Fcratis-screenplay-ui-composition\u002FSKILL.md -->\n\n# UI composition in Screenplay\n\nRead [preferred syntax](..\u002Fcratis-screenplay-toolchain\u002Freferences\u002Fpreferred-syntax.md) when writing or reviewing `.play`.\n\nEvent Modeling's wireframe step is a first-class part of the language. The shell,\nthe reusable shapes inside it, the forms bound to commands, and the navigation\nentries other modules contribute are all declared in the `.play` model.\n\n⚠️ `file \u003CIdentifier>` is read as a **property** named `file`, not a directive —\nthe type-reference shape wins the tie. `file Invoices\u002FRegister.cs` is a directive;\n`file Attachment` is a property. In a `trigger` body the directive always wins, so\na trigger value named `file` is written `@file`.\n\n## Locate the model\n\nLook first for the project's existing `.play` files: their folder is the model.\nFor a new model, check `Source\u002F` or `src\u002F`, else use `Screenplay\u002F` at the repository\nroot. Never put a model under `.cratis\u002F` or hand-copy it between repositories.\n`cratis ai install` manages `.cratis\u002Fai\u002F`, never model files. Keep explanatory\nMarkdown in project documentation; `.play` is the single flow model.\n\n## Product sources\n\nTool versions: toolchain `SKILL.md`. UI statements come from Screenplay\n`screens.md`, `contributions.md`, `navigation.md`, `sample-data.md`, `forms.md`, `templates.md`, `ui-profile.md`,\n`fixtures\u002Fscreen-release-ui.play`, `layout-arrangement.md`, `interactions.md`, `theme.md`,\n`internationalization.md` and `file-references.md` under `Documentation\u002Fscreenplay\u002F`. Scene\nruntime sources: scaffold Scene tag, `Source\u002FJavaScript\u002F**`. This guidance does not verify\nUI rendering.\n\nEvery construct on this page is deferred from the executable model with\ninformation `PLAY0269`: it never blocks binding, and it is not evidence that a\ntarget renders it.\n\nThe screens-release surface adds component data-context bindings, exposed template\nconfiguration, package\u002Ficon catalogs, manual form columns, hierarchical outlets,\nroutes, toolbars and dialog destinations, each with a separate support level\n(authoring accepted, executable admitted, runtime implemented). Discover the\ninstalled shape through MCP `syntax-schema`; details:\n`references\u002Fscreen-composition-contract.md`.\n\nAbsent editor highlighting is never evidence that a construct is wrong: check `screenplay`, not the editor (see [references\u002Fscreen-composition-contract.md](references\u002Fscreen-composition-contract.md)).\n\n\n## Compose in this order\n\nDecide what every screen is for before deciding how any of it is laid out. Layout\nwork on a screen whose purpose is unsettled is rework.\n\n1. **Level 1 for every screen in the flow first** (`cratis-screenplay-read-surface`:\n   `data` plus `action`). Read the whole set, not one screen at a time.\n2. **Review the flow before adding layout.** Walk it screen by screen as text\n   (format in `references\u002Fflow-review.md`). When the host advertises the MCP-Apps\n   extension for the `screenplay` MCP server, `visualize-model` (a `proposalId` or a `sketch`) can also show it on\n   a board; that is optional, and the text review is enough. Do not\n   use the Stage sandbox as the review: it renders only part of a screen, and\n   nothing here establishes that Stage renders an authored screen faithfully.\n   A behavior walk of what commands change is a separate, optional check owned by\n   `cratis-stage-rendering-and-sandbox`.\n3. **Add structure only to screens whose Level 1 is agreed**: template, sections,\n   forms, `on`\u002F`uses`. Use Level 3 inline code last, only where Level 2 cannot\n   say it.\n4. **Trace every field.** Each `form` `field` is a property of the form's command.\n   A prefilled value comes from `populate` or `from`; a derived one from\n   `compose using`. Each `summary` or `column` field is a property of the\n   screen's read model. A value with no origin means the command or read model is\n   missing it: fix the slice, never invent the value in the screen.\n5. **Read before editing.** Open the existing screen (or `read-workspace` \u002F\n   `declaration-details` through the `screenplay` MCP server) and change only the directives that were asked\n   for. Adding `layout` must not rewrite the Level-1 intent beneath it.\n6. **Report each screen in two or three sentences**: what it shows and what the\n   user can do. Not everyone reviewing can see a board.\n\nRead `references\u002Fworked-flow.md` when a complete example is needed before composing a flow; it contains two Level-1 screens, their command, read model and form, with the field trace.\n\n## `layout` — the application shell\n\nOne or more per application, declared at the top level; a `ui profile` selects the shell with `root template \u003CName>`.\nA complete example:\n\n```screenplay\nlayout AppShell\n  category application\n  topbar\n  navigation contributes Navigation\n  content\n  footer\n\n  arrangement flow\n    column\n      topbar height 56\n      row\n        navigation width 240\n        content grow\n      footer height 32\n```\n\nA slot is declared once by name, optionally marked\n`contributes \u003CContributionPoint>` to make it a contribution target.\n\n## `arrangement` — responsive `flow` or pixel-precise `freeform`\n\nA `when width\u002Fheight \u003Cclass>` variant replaces the entire tree for that condition, never a partial override. Read [references\u002Flayout-arrangement.md](references\u002Flayout-arrangement.md) when writing `flow` containers, `freeform` variants or `place` lines.\n\n## `screen template` and `dialog template`\n\nDeclared at module level, referenced by screens. Excerpt, inside a `module`:\n\n```screenplay excerpt\nscreen template MasterDetail\n  fits slot content\n  sidebar\n  main\n  arrangement flow\n    row gap 16\n      sidebar width 280\n      main grow\n\ndialog template RegisterInvoiceDialog\n  body\n  actions\n```\n\n`fits slot \u003Cname>` says which slot of its parent the template fills. **A dialog\ntemplate is a screen template in everything but one respect: it declares no\n`fits slot`, because a dialog occupies no slot of the structure it opens over** —\nwriting one is an error.\n\nA screen fills a template by naming it and providing slot bodies; a dialog is\nfilled exactly the same way, because from the screen's side there is no\ndifference. See `cratis-screenplay-read-surface` for the directives that go inside.\n\n## `form` — bound to a command\n\nExcerpt, inside a `module`; the command, query and screen are declared in its\nslices.\n\n```screenplay excerpt\nform RegisterInvoiceForm for RegisterInvoice\n  populate via query GetInvoiceDefaults by customerId\n  field invoiceNumber label \"Invoice #\"\n  field customerId    from item\n  field total         compose using TotalCalculator\n  on submit navigate to InvoiceList\n```\n\n- At most one `populate` — `populate via query \u003CQuery> [by \u003Cparam>]` or\n  `populate from item`.\n- `field \u003Cproperty>` takes at most one of `from \u003Csource>` or `compose using\n  \u003CCallback>`, plus an optional `label`.\n- At most one `on submit navigate to \u003CScreen> [by \u003Cparam>]`, the one-line form.\n  Any other `on` in a form body is a behavior attached to the form.\n\n⚠️ **A form is discovered, not referenced.** It never appears in a screen's\ndirective tree the way a `table` or `summary` does — it is found by its\n`for \u003CCommand>` binding wherever that command is invoked. A form sits at module\nlevel, so it disambiguates by module rather than by feature or slice.\n\n## `contribute`, toolbars, outlets and routes — navigation from elsewhere\n\nExcerpt, inside a `module` or `feature`; `Navigation` is the contribution point\nthe layout above declares.\n\n```screenplay excerpt\ncontribute to Navigation\n  navigate to InvoiceList\n  label \"Invoices\"\n  order 20\n```\n\nAll three directives are optional and appear at most once each.\n\n**Resolution walks outward:** a contribution first looks for a\n`contributes \u003CContributionPoint>` slot among its **own module's** templates, then\noutward to the nearest enclosing structure that declares a matching point. Three\ntiers exist — application-wide (the layout declares the point), cross-module, and\nmodule-level.\n\n`navigate to \u003CScreen> by \u003Cparam>` is **not** string interpolation; it reuses the\nsame typed navigate binding a screen action uses.\n\n⚠️ A navigation contribution also carries `id`, `icon`, `presentation`, `group` and\n`destination outlet \u003Cname> | dialog \u003CDialogTemplate> | external \"\u003Croute>\"`; its `navigate to` takes\n`route`, `outlet` and `parameter` lines, and an undeclared outlet or dialog target is `PLAY0654`\n(`contributions.md`).\n\nRequires Screenplay 4.133.0 or later (`screenplay --version`) for `PLAY0654` on an undeclared outlet or dialog target.\n\nAn explicit override for when nearest-enclosing is not the point you mean is\nnot in the language. The screens-release vector\n(canonical `ScreenComposition` corpus v1) adds typed screen composition; a\nrenderer that admits it renders it and passes the browser run. Report a refused form as a\ncapability gap, never a flat-list fallback; Studio production proof is separate.\n\n## The application shell: regions, slice buttons, blueprint references, sample data\n\nThe shell's navigation is declared in the `layout` (`navigation topbar` \u002F `navigation sidebar`, with `logo` and nested\n`item` lines) and each `module` states how it relates to a region: **inherit** (the default), **extend** (the\napplication's items plus its own) or **override** (its own only). Toolbars gain `button \u003Cid> title \"\u003Ctext>\" slice\n\u003CModule>.\u003CFeature>.\u003CSlice>`, which opens a **State Change** slice as a dialog (a State View or Automation slice is\n`PLAY0762`). A screen takes a template from a blueprint with `template blueprint \u003CBlueprint> \u003CName> version \"\u003Crange>\"`,\nand the `ui profile` selects the one active sample data pack (design and preview only, never in production).\n\n```screenplay\nlayout AppShell\n  category application\n  content\n\n  navigation sidebar\n    item sales title \"Sales\" target Sales\n      item orders title \"Orders\" target Sales.Orders\n\nmodule Sales\n  navigation sidebar extends\n    item customers title \"Customers\" target Sales.Customers\n\n  feature Orders\n  feature Customers\n```\n\nRead [references\u002Fapplication-shell.md](references\u002Fapplication-shell.md) before writing any of it: the inherit\u002Fextend\u002Foverride\nchoice, item target and slot, the module-only target rule (`PLAY0750`), buttons, feature and module toolbars (`toolbar` in a\n`feature` or `module`, `confirm`), blueprint ranges, sample data, MCP editing\nand the review checklist. `contribute to Navigation` stays the flat contribution; a new application uses regions.\n\n## Interactions — what a click does\n\nAn interaction wires an `on \u003Cthing>` trigger to actions, inline or through named\n`behavior` + `uses`. This is closed UI wiring, not scripting; validation stays on\nthe command. Trigger\u002Faction syntax is in [interaction example](references\u002Finteraction-example.md)\nand [guarded interactions](references\u002Fguarded-interactions.md).\n\nGuarded alternatives and `where` deprecation:\n[guarded interactions](references\u002Fguarded-interactions.md).\n\nRead [interaction example](references\u002Finteraction-example.md) when wiring a\nnamed confirmation behavior and an inline refresh to the same screen.\nScalar\u002Fnamed `returns` bind and reference-execute (ESM v7).\nRenderer generation\u002Fresponse limits: command-surface `references\u002Fgenerated-values-and-responses.md`.\nScreenplay resolves response names in form submit and execute success (Requires Screenplay 4.148.0 or later);\nown failure use is PLAY0685. No ESM change; Scene runtime binding remains downstream.\nAn existing success continuation does not imply a response contract.\nRead [response continuations](references\u002Fresponse-continuations.md) for scope,\nprecedence, PLAY0485 and examples.\n\n- Write the one-off case inline; name it with `behavior` when several places need\n  the same wiring. A `uses` site must supply exactly the declared parameters\n  (`PLAY0337`, `PLAY0338`).\n- `on`\u002F`uses` attach at every level — `layout`, `module`, `feature`, templates,\n  `form`, `screen`, `section`, slot, `table` — and are **additive**: outer\n  attachments run first unless a behavior declares `order`.\n- `on success`\u002F`on failure` belong only on actions that can fail (`execute`,\n  `refresh`, `confirm`, `open dialog`, `raise`); `on result` only on `open dialog`.\n  A continuation on `navigate`, `notify`, `set` or `close dialog` is an error\n  (`PLAY0320`). Actions after an unconditional `navigate` are unreachable\n  (`PLAY0339`).\n- Unknown commands, screens, queries, dialogs and behaviors are warnings, like\n  every other reference (`PLAY0330`–`PLAY0336`).\n- **A declared `trigger` is not a UI event.** Use `on click`, not `trigger`, for a\n  button. `on \u003CTrigger>` observes an application trigger and `raise \u003CTrigger>`\n  fires one; that is where the two meet.\n\n## `ui profile` and `theme`\n\nA `ui profile` selects the application shell with `root template` (an own layout or application-scope screen template, or `blueprint \u003CB> \u003CName>` with an optional `version` pin), its shell `option` lines, an `appearance` block (`color scheme`, `accent`), the template new screens start from (`new screens use template`), the theme and the `packages`, listed in override-priority order (a later package shadows an earlier one); `target platform` and `target size` accept any identifier, so a typo is silent. The legacy `layout \u003CName>` line inside a profile still reads but warns `PLAY0791`: write `root template`. `PLAY0790` to `PLAY0799` check the shell. Read [references\u002Fui-profile-and-theme.md](references\u002Fui-profile-and-theme.md) when writing a profile or theme, or fixing a shell diagnostic.\n\n## Localized strings\n\nLocalized text lives in companion `.strings` files and is referenced unquoted as `$strings.\u003Cdotted.key>`. Read [references\u002Flocalized-strings.md](references\u002Flocalized-strings.md) when localizing messages, labels or titles.\n\n## `file` — implementation or provenance, never a substitute\n\n`file` is a backend attachment, a screen realization file or declaration provenance; use repository-relative paths (`PLAY0264`) and never let it replace the declaration. **Loaded is not run.** Read [references\u002Ffile-references.md](references\u002Ffile-references.md) when attaching or checking a `file`, or diagnosing `PLAY0430`–`PLAY0434`.\n\n## Verify\n\n- [ ] `screenplay \u003Cmodel> --warnaserror` (standalone) reports zero errors and zero\n      warnings; `cratis screenplay validate --warnings-as-errors` says the same when its bundled\n      compiler matches (versions: `cratis-screenplay-toolchain`\n      `SKILL.md`).\n- [ ] Every screen in the flow has Level 1 reviewed before any layout, and every\n      form field and screen field traces to a command or read-model property.\n- [ ] Every slot a `contribute` targets is declared `contributes \u003CPoint>` somewhere\n      that encloses it.\n- [ ] No `dialog template` declares `fits slot`.\n- [ ] Each `ui profile` names its shell with `root template`, not the legacy `layout` line (`PLAY0791`); a blueprint shell is listed under `packages` and its `version` pin is deliberate.\n- [ ] `packages` are ordered deliberately — later shadows earlier.\n- [ ] Every theme a profile selects is `compatible with` one of its packages.\n- [ ] `target platform` and `target size` values are spelled correctly; nothing\n      checks them.\n- [ ] User-visible text is `$strings.` where the application is localized.\n- [ ] No `file` reference is doing work the declaration should be doing.\n- [ ] Every click, submit and screen entry that does something has an `on` or\n      `uses`; continuations sit only on actions that can fail.\n- [ ] Navigation regions, slice buttons, blueprint references and sample data follow `references\u002Fapplication-shell.md`: each module's mode is deliberate, no module item targets another module, every button names a State Change slice, buttons shared by a feature's screens sit in a feature `toolbar` linked to its commands (`confirm` on destructive ones), every template has a `category`, and the active sample data pack is chosen once in the `ui profile`.\n- [ ] Component bindings, exposed template values, manual form columns, toolbar items, outlets and routes all trace to typed data; no runtime fallback counts as delivery. Report authoring acceptance, executable admission and runtime\n      implementation separately.\n\n## Route near misses\n\n- A screen's own data, actions and name resolution: `cratis-screenplay-read-surface`.\n- Revision-checked MCP edits `cratis-screenplay-model-authoring` (`references\u002Fscreen-authoring-workflow.md`).\n- Application triggers and reactions: `cratis-screenplay-captures-and-reactions`.\n- Reviewing the whole flow's design: `cratis-screenplay-model-review`.\n- Deriving wireframes from the model (step 4): `cratis-screenplay-event-modeling`.\n- Rendering\u002Fomissions: `cratis-stage-rendering-and-sandbox`, `cratis-screenplay-render-and-gap-fill`.\n- Building the actual React application: `cratis-arc-react-page`, `cratis-components-styling`.\n\n## Lineage\n\nRead `references\u002Fprovenance.md` when checking source attribution or adaptation permissions.\n","\u003C!-- cratis-ai-managed: skills\u002Fcratis-screenplay-ui-composition\u002FSKILL.md -->\n\n# UI composition in Screenplay\n\nRead [preferred syntax](..\u002Fcratis-screenplay-toolchain\u002Freferences\u002Fpreferred-syntax.md) when writing or reviewing `.play`.\n\nEvent Modeling's wireframe step is a first-class part of the language. The shell,\nthe reusable shapes inside it, the forms bound to commands, and the navigation\nentries other modules contribute are all declared in the `.play` model.\n\n⚠️ `file \u003CIdentifier>` is read as a **property** named `file`, not a directive —\nthe type-reference shape wins the tie. `file Invoices\u002FRegister.cs` is a directive;\n`file Attachment` is a property. In a `trigger` body the directive always wins, so\na trigger value named `file` is written `@file`.\n\n## Locate the model\n\nLook first for the project's existing `.play` files: their folder is the model.\nFor a new model, check `Source\u002F` or `src\u002F`, else use `Screenplay\u002F` at the repository\nroot. Never put a model under `.cratis\u002F` or hand-copy it between repositories.\n`cratis ai install` manages `.cratis\u002Fai\u002F`, never model files. Keep explanatory\nMarkdown in project documentation; `.play` is the single flow model.\n\n## Product sources\n\nTool versions: toolchain `SKILL.md`. UI statements come from Screenplay\n`screens.md`, `contributions.md`, `navigation.md`, `sample-data.md`, `forms.md`, `templates.md`, `ui-profile.md`,\n`fixtures\u002Fscreen-release-ui.play`, `layout-arrangement.md`, `interactions.md`, `theme.md`,\n`internationalization.md` and `file-references.md` under `Documentation\u002Fscreenplay\u002F`. Scene\nruntime sources: scaffold Scene tag, `Source\u002FJavaScript\u002F**`. This guidance does not verify\nUI rendering.\n\nEvery construct on this page is deferred from the executable model with\ninformation `PLAY0269`: it never blocks binding, and it is not evidence that a\ntarget renders it.\n\nThe screens-release surface adds component data-context bindings, exposed template\nconfiguration, package\u002Ficon catalogs, manual form columns, hierarchical outlets,\nroutes, toolbars and dialog destinations, each with a separate support level\n(authoring accepted, executable admitted, runtime implemented). Discover the\ninstalled shape through MCP `syntax-schema`; details:\n`references\u002Fscreen-composition-contract.md`.\n\nAbsent editor highlighting is never evidence that a construct is wrong: check `screenplay`, not the editor (see [references\u002Fscreen-composition-contract.md](references\u002Fscreen-composition-contract.md)).\n\n\n## Compose in this order\n\nDecide what every screen is for before deciding how any of it is laid out. Layout\nwork on a screen whose purpose is unsettled is rework.\n\n1. **Level 1 for every screen in the flow first** (`cratis-screenplay-read-surface`:\n   `data` plus `action`). Read the whole set, not one screen at a time.\n2. **Review the flow before adding layout.** Walk it screen by screen as text\n   (format in `references\u002Fflow-review.md`). When the host advertises the MCP-Apps\n   extension for the `screenplay` MCP server, `visualize-model` (a `proposalId` or a `sketch`) can also show it on\n   a board; that is optional, and the text review is enough. Do not\n   use the Stage sandbox as the review: it renders only part of a screen, and\n   nothing here establishes that Stage renders an authored screen faithfully.\n   A behavior walk of what commands change is a separate, optional check owned by\n   `cratis-stage-rendering-and-sandbox`.\n3. **Add structure only to screens whose Level 1 is agreed**: template, sections,\n   forms, `on`\u002F`uses`. Use Level 3 inline code last, only where Level 2 cannot\n   say it.\n4. **Trace every field.** Each `form` `field` is a property of the form's command.\n   A prefilled value comes from `populate` or `from`; a derived one from\n   `compose using`. Each `summary` or `column` field is a property of the\n   screen's read model. A value with no origin means the command or read model is\n   missing it: fix the slice, never invent the value in the screen.\n5. **Read before editing.** Open the existing screen (or `read-workspace` \u002F\n   `declaration-details` through the `screenplay` MCP server) and change only the directives that were asked\n   for. Adding `layout` must not rewrite the Level-1 intent beneath it.\n6. **Report each screen in two or three sentences**: what it shows and what the\n   user can do. Not everyone reviewing can see a board.\n\nRead `references\u002Fworked-flow.md` when a complete example is needed before composing a flow; it contains two Level-1 screens, their command, read model and form, with the field trace.\n\n## `layout` — the application shell\n\nOne or more per application, declared at the top level; a `ui profile` selects the shell with `root template \u003CName>`.\nA complete example:\n\n```screenplay\nlayout AppShell\n  category application\n  topbar\n  navigation contributes Navigation\n  content\n  footer\n\n  arrangement flow\n    column\n      topbar height 56\n      row\n        navigation width 240\n        content grow\n      footer height 32\n```\n\nA slot is declared once by name, optionally marked\n`contributes \u003CContributionPoint>` to make it a contribution target.\n\n## `arrangement` — responsive `flow` or pixel-precise `freeform`\n\nA `when width\u002Fheight \u003Cclass>` variant replaces the entire tree for that condition, never a partial override. Read [references\u002Flayout-arrangement.md](references\u002Flayout-arrangement.md) when writing `flow` containers, `freeform` variants or `place` lines.\n\n## `screen template` and `dialog template`\n\nDeclared at module level, referenced by screens. Excerpt, inside a `module`:\n\n```screenplay excerpt\nscreen template MasterDetail\n  fits slot content\n  sidebar\n  main\n  arrangement flow\n    row gap 16\n      sidebar width 280\n      main grow\n\ndialog template RegisterInvoiceDialog\n  body\n  actions\n```\n\n`fits slot \u003Cname>` says which slot of its parent the template fills. **A dialog\ntemplate is a screen template in everything but one respect: it declares no\n`fits slot`, because a dialog occupies no slot of the structure it opens over** —\nwriting one is an error.\n\nA screen fills a template by naming it and providing slot bodies; a dialog is\nfilled exactly the same way, because from the screen's side there is no\ndifference. See `cratis-screenplay-read-surface` for the directives that go inside.\n\n## `form` — bound to a command\n\nExcerpt, inside a `module`; the command, query and screen are declared in its\nslices.\n\n```screenplay excerpt\nform RegisterInvoiceForm for RegisterInvoice\n  populate via query GetInvoiceDefaults by customerId\n  field invoiceNumber label \"Invoice #\"\n  field customerId    from item\n  field total         compose using TotalCalculator\n  on submit navigate to InvoiceList\n```\n\n- At most one `populate` — `populate via query \u003CQuery> [by \u003Cparam>]` or\n  `populate from item`.\n- `field \u003Cproperty>` takes at most one of `from \u003Csource>` or `compose using\n  \u003CCallback>`, plus an optional `label`.\n- At most one `on submit navigate to \u003CScreen> [by \u003Cparam>]`, the one-line form.\n  Any other `on` in a form body is a behavior attached to the form.\n\n⚠️ **A form is discovered, not referenced.** It never appears in a screen's\ndirective tree the way a `table` or `summary` does — it is found by its\n`for \u003CCommand>` binding wherever that command is invoked. A form sits at module\nlevel, so it disambiguates by module rather than by feature or slice.\n\n## `contribute`, toolbars, outlets and routes — navigation from elsewhere\n\nExcerpt, inside a `module` or `feature`; `Navigation` is the contribution point\nthe layout above declares.\n\n```screenplay excerpt\ncontribute to Navigation\n  navigate to InvoiceList\n  label \"Invoices\"\n  order 20\n```\n\nAll three directives are optional and appear at most once each.\n\n**Resolution walks outward:** a contribution first looks for a\n`contributes \u003CContributionPoint>` slot among its **own module's** templates, then\noutward to the nearest enclosing structure that declares a matching point. Three\ntiers exist — application-wide (the layout declares the point), cross-module, and\nmodule-level.\n\n`navigate to \u003CScreen> by \u003Cparam>` is **not** string interpolation; it reuses the\nsame typed navigate binding a screen action uses.\n\n⚠️ A navigation contribution also carries `id`, `icon`, `presentation`, `group` and\n`destination outlet \u003Cname> | dialog \u003CDialogTemplate> | external \"\u003Croute>\"`; its `navigate to` takes\n`route`, `outlet` and `parameter` lines, and an undeclared outlet or dialog target is `PLAY0654`\n(`contributions.md`).\n\nRequires Screenplay 4.133.0 or later (`screenplay --version`) for `PLAY0654` on an undeclared outlet or dialog target.\n\nAn explicit override for when nearest-enclosing is not the point you mean is\nnot in the language. The screens-release vector\n(canonical `ScreenComposition` corpus v1) adds typed screen composition; a\nrenderer that admits it renders it and passes the browser run. Report a refused form as a\ncapability gap, never a flat-list fallback; Studio production proof is separate.\n\n## The application shell: regions, slice buttons, blueprint references, sample data\n\nThe shell's navigation is declared in the `layout` (`navigation topbar` \u002F `navigation sidebar`, with `logo` and nested\n`item` lines) and each `module` states how it relates to a region: **inherit** (the default), **extend** (the\napplication's items plus its own) or **override** (its own only). Toolbars gain `button \u003Cid> title \"\u003Ctext>\" slice\n\u003CModule>.\u003CFeature>.\u003CSlice>`, which opens a **State Change** slice as a dialog (a State View or Automation slice is\n`PLAY0762`). A screen takes a template from a blueprint with `template blueprint \u003CBlueprint> \u003CName> version \"\u003Crange>\"`,\nand the `ui profile` selects the one active sample data pack (design and preview only, never in production).\n\n```screenplay\nlayout AppShell\n  category application\n  content\n\n  navigation sidebar\n    item sales title \"Sales\" target Sales\n      item orders title \"Orders\" target Sales.Orders\n\nmodule Sales\n  navigation sidebar extends\n    item customers title \"Customers\" target Sales.Customers\n\n  feature Orders\n  feature Customers\n```\n\nRead [references\u002Fapplication-shell.md](references\u002Fapplication-shell.md) before writing any of it: the inherit\u002Fextend\u002Foverride\nchoice, item target and slot, the module-only target rule (`PLAY0750`), buttons, feature and module toolbars (`toolbar` in a\n`feature` or `module`, `confirm`), blueprint ranges, sample data, MCP editing\nand the review checklist. `contribute to Navigation` stays the flat contribution; a new application uses regions.\n\n## Interactions — what a click does\n\nAn interaction wires an `on \u003Cthing>` trigger to actions, inline or through named\n`behavior` + `uses`. This is closed UI wiring, not scripting; validation stays on\nthe command. Trigger\u002Faction syntax is in [interaction example](references\u002Finteraction-example.md)\nand [guarded interactions](references\u002Fguarded-interactions.md).\n\nGuarded alternatives and `where` deprecation:\n[guarded interactions](references\u002Fguarded-interactions.md).\n\nRead [interaction example](references\u002Finteraction-example.md) when wiring a\nnamed confirmation behavior and an inline refresh to the same screen.\nScalar\u002Fnamed `returns` bind and reference-execute (ESM v7).\nRenderer generation\u002Fresponse limits: command-surface `references\u002Fgenerated-values-and-responses.md`.\nScreenplay resolves response names in form submit and execute success (Requires Screenplay 4.148.0 or later);\nown failure use is PLAY0685. No ESM change; Scene runtime binding remains downstream.\nAn existing success continuation does not imply a response contract.\nRead [response continuations](references\u002Fresponse-continuations.md) for scope,\nprecedence, PLAY0485 and examples.\n\n- Write the one-off case inline; name it with `behavior` when several places need\n  the same wiring. A `uses` site must supply exactly the declared parameters\n  (`PLAY0337`, `PLAY0338`).\n- `on`\u002F`uses` attach at every level — `layout`, `module`, `feature`, templates,\n  `form`, `screen`, `section`, slot, `table` — and are **additive**: outer\n  attachments run first unless a behavior declares `order`.\n- `on success`\u002F`on failure` belong only on actions that can fail (`execute`,\n  `refresh`, `confirm`, `open dialog`, `raise`); `on result` only on `open dialog`.\n  A continuation on `navigate`, `notify`, `set` or `close dialog` is an error\n  (`PLAY0320`). Actions after an unconditional `navigate` are unreachable\n  (`PLAY0339`).\n- Unknown commands, screens, queries, dialogs and behaviors are warnings, like\n  every other reference (`PLAY0330`–`PLAY0336`).\n- **A declared `trigger` is not a UI event.** Use `on click`, not `trigger`, for a\n  button. `on \u003CTrigger>` observes an application trigger and `raise \u003CTrigger>`\n  fires one; that is where the two meet.\n\n## `ui profile` and `theme`\n\nA `ui profile` selects the application shell with `root template` (an own layout or application-scope screen template, or `blueprint \u003CB> \u003CName>` with an optional `version` pin), its shell `option` lines, an `appearance` block (`color scheme`, `accent`), the template new screens start from (`new screens use template`), the theme and the `packages`, listed in override-priority order (a later package shadows an earlier one); `target platform` and `target size` accept any identifier, so a typo is silent. The legacy `layout \u003CName>` line inside a profile still reads but warns `PLAY0791`: write `root template`. `PLAY0790` to `PLAY0799` check the shell. Read [references\u002Fui-profile-and-theme.md](references\u002Fui-profile-and-theme.md) when writing a profile or theme, or fixing a shell diagnostic.\n\n## Localized strings\n\nLocalized text lives in companion `.strings` files and is referenced unquoted as `$strings.\u003Cdotted.key>`. Read [references\u002Flocalized-strings.md](references\u002Flocalized-strings.md) when localizing messages, labels or titles.\n\n## `file` — implementation or provenance, never a substitute\n\n`file` is a backend attachment, a screen realization file or declaration provenance; use repository-relative paths (`PLAY0264`) and never let it replace the declaration. **Loaded is not run.** Read [references\u002Ffile-references.md](references\u002Ffile-references.md) when attaching or checking a `file`, or diagnosing `PLAY0430`–`PLAY0434`.\n\n## Verify\n\n- [ ] `screenplay \u003Cmodel> --warnaserror` (standalone) reports zero errors and zero\n      warnings; `cratis screenplay validate --warnings-as-errors` says the same when its bundled\n      compiler matches (versions: `cratis-screenplay-toolchain`\n      `SKILL.md`).\n- [ ] Every screen in the flow has Level 1 reviewed before any layout, and every\n      form field and screen field traces to a command or read-model property.\n- [ ] Every slot a `contribute` targets is declared `contributes \u003CPoint>` somewhere\n      that encloses it.\n- [ ] No `dialog template` declares `fits slot`.\n- [ ] Each `ui profile` names its shell with `root template`, not the legacy `layout` line (`PLAY0791`); a blueprint shell is listed under `packages` and its `version` pin is deliberate.\n- [ ] `packages` are ordered deliberately — later shadows earlier.\n- [ ] Every theme a profile selects is `compatible with` one of its packages.\n- [ ] `target platform` and `target size` values are spelled correctly; nothing\n      checks them.\n- [ ] User-visible text is `$strings.` where the application is localized.\n- [ ] No `file` reference is doing work the declaration should be doing.\n- [ ] Every click, submit and screen entry that does something has an `on` or\n      `uses`; continuations sit only on actions that can fail.\n- [ ] Navigation regions, slice buttons, blueprint references and sample data follow `references\u002Fapplication-shell.md`: each module's mode is deliberate, no module item targets another module, every button names a State Change slice, buttons shared by a feature's screens sit in a feature `toolbar` linked to its commands (`confirm` on destructive ones), every template has a `category`, and the active sample data pack is chosen once in the `ui profile`.\n- [ ] Component bindings, exposed template values, manual form columns, toolbar items, outlets and routes all trace to typed data; no runtime fallback counts as delivery. Report authoring acceptance, executable admission and runtime\n      implementation separately.\n\n## Route near misses\n\n- A screen's own data, actions and name resolution: `cratis-screenplay-read-surface`.\n- Revision-checked MCP edits `cratis-screenplay-model-authoring` (`references\u002Fscreen-authoring-workflow.md`).\n- Application triggers and reactions: `cratis-screenplay-captures-and-reactions`.\n- Reviewing the whole flow's design: `cratis-screenplay-model-review`.\n- Deriving wireframes from the model (step 4): `cratis-screenplay-event-modeling`.\n- Rendering\u002Fomissions: `cratis-stage-rendering-and-sandbox`, `cratis-screenplay-render-and-gap-fill`.\n- Building the actual React application: `cratis-arc-react-page`, `cratis-components-styling`.\n\n## Lineage\n\nRead `references\u002Fprovenance.md` when checking source attribution or adaptation permissions.\n",{"name":5,"license":14,"description":7},"main","feed400071bf3f9f4410a956d73413daa6e1b334",".cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue","https:\u002F\u002Fwww.cratis.io\u002Fprologue\u002F","https:\u002F\u002Fgithub.com\u002FCratis","https:\u002F\u002Fwww.cratis.io","Open-source (MIT) event sourcing and CQRS for .NET and beyond: Chronicle, Arc, Components and Screenplay.","2026-11-14 06:37:10",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Cratis\u002FPrologue --skill cratis-screenplay-ui-composition",{"tool":39,"command":40},"bunx","bunx skills add Cratis\u002FPrologue --skill cratis-screenplay-ui-composition",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Cratis\u002FPrologue --skill cratis-screenplay-ui-composition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002FSKILL.md",true,[47,51,57,61,65,69,73,77,81,85,89,93,97],{"path":48,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":15},"LICENSE","许可证",576,{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fapplication-shell.md","REFERENCE","参考文档",17066,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fapplication-shell.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ffile-references.md",2580,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Ffile-references.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fflow-review.md",2389,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fflow-review.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fguarded-interactions.md",3505,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fguarded-interactions.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Finteraction-example.md",2139,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Finteraction-example.md",{"path":74,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Flayout-arrangement.md",1371,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Flayout-arrangement.md",{"path":78,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Flocalized-strings.md",851,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Flocalized-strings.md",{"path":82,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fprovenance.md",1428,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fprovenance.md",{"path":86,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fresponse-continuations.md",4282,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fresponse-continuations.md",{"path":90,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fscreen-composition-contract.md",17839,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fscreen-composition-contract.md",{"path":94,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fui-profile-and-theme.md",8379,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fui-profile-and-theme.md",{"path":98,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fworked-flow.md",3306,"https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fcratis-screenplay-ui-composition\u002Freferences\u002Fworked-flow.md",[102,110,118,126,134,142],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M78CCRM9594FCYFMCY5W137G","vectorization","Designs, implements, optimizes, and reviews SIMD code in .NET: vectorizing scalar loops with TensorPrimitives, Vector64, Vector128, Vector256, Vector512, or hardware intrinsics, and reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. Use when a .NET loop or SIMD routine is being written or reviewed. Not for performance work unrelated to SIMD.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fvectorization\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fvectorization\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M78CCJKGDNSDNCMA92PV8GCR","target-authoring","Canonical patterns for writing custom MSBuild targets: DependsOnTargets versus BeforeTargets and AfterTargets, the Build-to-CoreBuild three-level pattern, and the XxxDependsOn chain-extension pattern. Use when diagnosing or fixing custom-target anti-patterns: Directory.Build.targets redefining SDK targets, targets that replace CompileDependsOn instead of extending it, Outputs versus Returns misuse that returns stale results, missing Inputs\u002FOutputs causing needless rebuilds, or missing FileWrites registration. Not for incremental build tuning or general anti-pattern review (use the msbuild skill), or non-MSBuild build systems.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Ftarget-authoring\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Ftarget-authoring\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M78CCCWS16JZA36AGB5YVMAN","run-tests","Chooses and runs the repository-compatible .NET test command: classic, VSTest, bridged MTP, or native MTP syntax for MSTest, xUnit, NUnit, and TUnit. Use before running .NET tests or answering with a test command or flags: run the tests, one test, class, category, trait or target framework, combined filters, --filter-query, --no-build, --diag, TRX, coverage collection, crash or hang dumps, filter errors, or unrecognized options. Not for platform identification alone (use platform-detection), writing or debugging test code, interpreting a coverage report (use coverage-analysis), CI investigation, migration, or a persistent hot-reload loop.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Frun-tests\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Frun-tests\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M78CC6VC08Y3WTN4T784DYDY","profiling","Uses the free official .NET diagnostics CLI tools for profiling and runtime investigation in a repository: CPU, GC pressure, allocation growth, exception storms, lock contention, and slow code. Use when a .NET application needs performance or runtime profiling. Not for replacing realistic performance or load tests with ad-hoc tracing, production heap collection without a pause-risk plan, crash dumps (use dump-collect), or benchmark design (use microbenchmarking).","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fprofiling\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fprofiling\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M78CC14WNAP1Y77ZMM4VD29A","platform-detection","Identifies a .NET project's test platform, framework, command mode, and SDK-style versus classic project system, resolving global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest, xUnit, NUnit, and TUnit. Use when asking \"which test platform or framework?\", \"VSTest or MTP?\", or \"what runner does this project use?\", including bridge settings, UseVSTest opt-outs, and conflicting VSTest\u002FMTP configuration. Not for running or filtering tests, commands, flags, TRX, dumps, or test-command errors (use run-tests), or for hot-reload or migration requests.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Fplatform-detection\u002FSKILL.md",[],[],{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":19},"01M78CBVQKQZ6C9VZAD48GB8AC","orleans","Designs Microsoft Orleans systems from each primitive's purpose and failure model: grains, digital twins, state versus databases, transactions, messaging, streams, timers, reminders, Durable Jobs, stateless workers, grain services, startup, and hosting. Use when a task needs an Orleans design decision: inspect version and topology, choose the primitive, implement, and validate. Not for other actor stacks, batch processing, relational-only CRUD, or advice without an Orleans decision.","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FCratis\u002FPrologue\u002Fblob\u002Fmain\u002F.cratis\u002Fai\u002Fskills\u002Forleans\u002FSKILL.md",[],[]]