@cratis/pi 7.121.0 → 7.122.1

package/package/corpus/skills/cratis-screenplay-automations-and-translations/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-automations-and-translations
-description: "Model Screenplay Automation and Translate slices: when a reaction is warranted, todo-list work queues, produces versus invokes, the trusted actor behind caller-less invokes, termination, clock and trigger occurrences, outside facts via capture with correlation, dedup and enrich/ignore/infer, recovery ownership, and what once-only does not prove about external effects. Use when a model has or needs 'when X happens then ...', schedules, work queues, webhooks, API polls, message feeds or imported events. Not for: reaction, trigger or capture grammar (use `cratis-screenplay-captures-and-reactions`)."
+description: Use when deciding Screenplay event-driven work, schedules, queues or translation of outside facts and their recovery guarantees. Not for reaction, trigger or capture grammar alone; use cratis-screenplay-captures-and-reactions.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-captures-and-reactions
-description: Model the reactive edges of a Cratis Screenplay `.play` model — `capture` in the Change Data Capture Language for turning external data into events, and `reaction` plus `trigger` for work that runs when something happens, on a schedule, or on an integration signal. Use when integrating an external system, translating outside data into events, or declaring automatic follow-up work in a `.play` model. Do not use for commands, projections or screens.
+description: Use when writing Screenplay capture, reaction or trigger syntax for outside facts and automatic follow-up work. Not for deciding integration guarantees or declaring commands, projections and screens.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-command-surface/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-command-surface
-description: Write the write side of a Cratis Screenplay `.play` model — the `command` block and its `identifier`, `reads`, `validate`, `authorize`, `produces`, `handler` and `concurrency` clauses, plus `event`, `constraint`, `policy`, `persona`, `concept`, `type` and `seed`. Use when declaring or changing a command, an event shape, a validation or authorization rule, an append-time constraint, or a strongly-typed value in Screenplay. Do not use for projections, queries, screens, captures or reactions.
+description: Use when writing Screenplay command, event, constraint, authorization or strongly-typed value syntax. Not for deciding stream boundaries or declaring queries, screens, projections and reactive edges.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-delivery-planning/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-delivery-planning
-description: "Plan and estimate the delivery of an accepted Screenplay model by slices: count slices by type (StateChange, StateView, Automation, Translate), derive the slice dependency table from the model, split work in parallel along event contracts, track slice groups as GitHub issues with a closed status vocabulary, and turn the team's own completed-slice history into ranged estimates, capacity math and retrospective metrics. Use when asked how long a modeled scope will take, how to split it across people or agents, what to build first, or how to track and re-plan delivery. Not for: deciding what to model (use `cratis-screenplay-event-modeling`), rendering or gap-filling a slice (use `cratis-screenplay-render-and-gap-fill`), or reviewing the model (use `cratis-screenplay-model-review`)."
+description: Use when estimating an accepted Screenplay scope, ordering slice dependencies or dividing and tracking delivery across people or agents. Not for deciding model behavior, reviewing the model or rendering individual slices.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-discovery/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-discovery
-description: "Discover a domain and its event timeline by interview and live storming, landing results directly in `.play` as modules, personas with Does/Reads/Cannot, features and past-tense events with essential fields, in story order, with branches, way-outs and endings named. Use when starting a model, exploring a workflow, supporting a human workshop, or turning notes, tickets or documents into events. Not for: command or read-model design (use `cratis-screenplay-slice-design`), reviewing a finished model (use `cratis-screenplay-model-review`), or reverse-engineering code (use `cratis-screenplay-legacy-extraction`)."
+description: Use when discovering a domain's event timeline from interviews, workshops or process documents for a .play model. Not for command and view design, finished-model review or extracting behavior from existing code.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-event-modeling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-event-modeling
-description: "Entry point and router for model-first Cratis work: the short decision rule (model, or code), the nine-step workflow per behavior, the four slice types, the Cratis divergences from the generic method, the quick validation gate, file layout and what parsed-but-not-runnable means, then the phase skill to load next. Use when designing an information system, mapping a business process or information flow, deciding the event vocabulary or stream boundaries, turning a whiteboard model into `.play`, or when a request may change behavior in an application with a Screenplay model. Not for: Screenplay syntax and the compiler alone (use `cratis-screenplay-toolchain`), the lifecycle, verdicts and handoffs (use `cratis-screenplay-modeling-lifecycle`), or rendering a settled model (use `cratis-screenplay-render-and-gap-fill`)."
+description: Use when starting a Screenplay modeling task, mapping a business process or deciding where a modeled behavior change enters the workflow. Not for syntax-only questions, lifecycle verdicts or rendering a settled model.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-legacy-extraction/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-legacy-extraction
-description: "Turn an existing system into an evidence-backed, intentional Screenplay `.play` model: interview and freeze agreement, provider-coverage inventory, `cratis screenplay generate`, approval-gated Prologue capture and interpret, bounded UI walks, targeted code reads, an evidence table with exact path:start-end locators that keeps unknowns, keep / change / remove decisions, re-slicing by business decision, a loss report and expert verification. Use for brownfield understanding, documentation or migration. Not for: greenfield modeling (use `cratis-screenplay-discovery`), reviewing the candidate (use `cratis-screenplay-model-review`), running Chronicle systems (use `cratis-chronicle-cli-operations`)."
+description: Use when understanding an inherited system or deriving a candidate Screenplay model for brownfield documentation or migration. Not for greenfield discovery, reviewing the candidate or diagnosing a live Chronicle store.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-model-authoring/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-model-authoring
-description: Author, inspect, refactor and verify a Cratis Screenplay .play model through its typed AST and MCP workspace tools. Use for creating or changing model elements, navigating large split models, reviewing references/specifications, revision-checked screen/UI authoring proposals, or distinguishing source validity from executable/runtime readiness. Do not use for rendering a model into an application or hand-written Arc/Chronicle code.
+description: Use when inspecting or changing Screenplay model elements through typed AST proposals, navigating split models or recovering workspace state. Not for rendering the model or writing Arc and Chronicle application code.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-model-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-model-review
-description: "Critic-mode review of a Cratis Screenplay .play model, candidate, proposal or edit request: verdict evidence, element sweep, entity walk, field lineage, an 89-check phased checklist, anti-pattern signals, event-sourcing correctness and a PASS / PASS WITH WARNINGS / FAIL report pinned to declarations, plus a business-question pass and a read-only walkthrough that explains a feature or a planned change slice by slice. Use to review, audit, self-check or explain a model before acceptance or rendering. Never edits the model. Not for: writing the missing specifications (use `cratis-screenplay-scenario-coverage`), changing the model (use `cratis-screenplay-model-authoring`)."
+description: Use when reviewing, auditing, self-checking or explaining a Screenplay model or proposal read-only before acceptance or rendering. Not for editing the model, adding missing scenarios or reviewing rendered code.
 license: MIT
 ---
 
@@ -58,7 +58,7 @@ model's behalf.
    payload or generic verb is a signal to investigate: report it only when the name or payload
    hides the business reason or a consequence is shown (distinct facts that share a shape and
    earlier generations are not findings). A description, comment or spec name never excuses a flagged line.
-4. **Entity walk** (phase 2). Per kind of event source write the first fact, the allowed and the
+4. **Entity walk** (phase 2). Perform an entity walk per kind of event source: write the first fact, the allowed and the
    refused state changes, the final states; then walk cancel, fail, correct and expire paths. Each
    refused change needs a `then error` spec; each command missing from the table is investigated.
 5. **Lineage and completeness** (phase 3). Backward: every read-model field to an event field,
@@ -167,7 +167,7 @@ P5 uses a fresh reviewer who authored nothing in scope; record reviewer/author m
 The review is complete when every phase of the checklist has a status for every check, every
 sweep `NONE` and field-copy line is a finding or has a written domain reason, all five verdict
 lines are present (result or "not run: reason"), the three final questions are answered, and the
-verdict follows the rules in `references/report-template.md`.
+verdict follows the rules in `references/report-template.md`: PASS, PASS WITH WARNINGS or FAIL.
 
 ## Verify
 - Every finding has severity, kind, address and file:line, rule (with tier), consequence and fix;

package/package/corpus/skills/cratis-screenplay-modeling-lifecycle/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-modeling-lifecycle
-description: "Model first: load before any Cratis application work where a Screenplay `.play` model is, or should become, the source of truth. Holds the model-first decision rule, modes, independent verdicts V1-V5, the P0-P9 phases with Input / Carry-forward / Gate, stop-or-assume, identity ownership, approvals, untrusted content, session state and handoffs, then routes to ONE phase skill. Not for: Screenplay syntax or the compiler (use `cratis-screenplay-toolchain`), a single construct (use the `cratis-screenplay-*` construct skills), or Chronicle runtime diagnosis (use `cratis-chronicle-cli-operations`)."
+description: Use before application work to determine model-first obligations, or when selecting a Screenplay phase, verdict, approval or handoff. Not for construct syntax alone or Chronicle runtime diagnosis.
 license: MIT
 metadata:
   cratis-hint-paths: "**/*.play"

package/package/corpus/skills/cratis-screenplay-projections/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-projections
-description: Build a Cratis Screenplay read model with the Projection Declaration Language (PDL) — keys, `from`/`every`/`all`, property mapping and AutoMap, joins, children and nested objects, removal, arithmetic counters, and the reducer escape hatch. Use when declaring or changing how events become read-model state in a `.play` model, or when a projection does not populate what was expected. Use `cratis-chronicle-projection` instead for hand-written C# Chronicle projections.
+description: Use when declaring Screenplay event-to-state mappings or diagnosing a .play projection's keys, joins, children or lifecycle variants. Not for hand-written C# Chronicle projections or read-model query contracts.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-read-surface/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-read-surface
-description: Declare the read side of a Cratis Screenplay `.play` model — the `readmodel` shape, `query` with `by`/`filter`/`scoped to`/`observable`/`performer`, and `screen` at its three levels of detail, including the data/action contract that later component bindings, templates, forms, toolbars, routes and outlets consume. Use when adding or changing a query, a read-model shape, or a screen in a `.play` model, or when deciding what a caller may narrow a result by. Do not use for how events fill the read model, and do not use for layouts, templates or forms.
+description: Use when writing Screenplay read-model shapes, query filtering or screen data and action contracts. Not for event-to-state mappings or component layouts, templates and forms.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-render-and-gap-fill/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-render-and-gap-fill
-description: "Deliver an accepted Screenplay `.play` model as code: probe whether `cratis render` admits the whole model, publish, then report admission, publication, Debug build and Debug tests as separate results mapped to the generated specification classes; triage model fix versus capability gap; bounded `Customizations/` adapters; drift by manifest revision; and hand non-renderable scope to `slice-implementer` with the model as the contract. Use when an accepted model must become running code, when asking whether a model renders, or after a model change. Not for: changing the model (use `cratis-screenplay-slice-design`), Stage internals (use `cratis-stage-rendering-and-sandbox`), or checking hand-written code against its slice (use `cratis-application-slice-conformance`)."
+description: Use when probing whether an accepted Screenplay model renders, delivering admitted scope or triaging a renderer gap. Not for changing the model, Stage internals or auditing hand-written slice conformance.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-scenario-coverage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-scenario-coverage
-description: "Decide and write Screenplay specifications for slices: a coverage matrix before drafting, every applicable scenario type per command (rules, denial, duplicates and retries, competing claims, ordering, external failure, compensation, evolution), view lifecycle specs per read model, shared example data, spec forms per mode, and a workshop guide for scenario sessions. Use when writing or auditing given/when/then in a `.play` model. Not for: spec grammar and comparison semantics (use `cratis-screenplay-specifications`), C# specs (use `cratis-specifications-csharp`)."
+description: Use when deciding which Screenplay scenarios a slice needs or auditing its refusal, retry, race and view-lifecycle coverage. Not for specification grammar, comparison semantics or C# tests.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-slice-design/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-slice-design
-description: "Shape Screenplay slices from a discovered timeline: commands with reachable, authorized origins and traced inputs, rules placed by layer, a per-command refusal inventory, events-vs-views decisions, read models per screen component with queries that follow the business view, Level-1 screens, field lineage, state-transition tables, slice dependencies and the next slice. Use when designing slices after discovery, adding a capability or deciding command inputs, rule placement, read-model shape or screen data. Not for: stream boundaries or invariants across streams (use `cratis-screenplay-streams-and-consistency`), reactions and captures (use `cratis-screenplay-automations-and-translations`), which scenarios to write (use `cratis-screenplay-scenario-coverage`), or auditing a finished model (use `cratis-screenplay-model-review`)."
+description: Use when turning a discovered Screenplay timeline into commands, views and screens, or deciding inputs, refusal rules and field lineage. Not for stream identity, automation guarantees, scenario coverage or a finished-model audit.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-specifications/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-specifications
-description: Pin behavior in a Cratis Screenplay `.play` model with given/when/then `specification` blocks — prior events and read-model state, the caller, the command or appended event under test, expected events, read-model state, query results, rejections and denials, plus what the reference execution actually runs. Use when writing acceptance criteria for a slice, specifying a rejection or an authorization denial, or deciding whether a rule belongs in a specification or in the type system. Do not use for C# or TypeScript test code.
+description: Use when writing Screenplay specification syntax or checking fixture, outcome-comparison, rejection and denial semantics. Not for choosing scenario coverage or writing C# and TypeScript tests.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-streams-and-consistency/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-streams-and-consistency
-description: "Decide Screenplay stream identity and consistency: one business identity per event source, where each invariant is enforced atomically, constraints versus recorded state-dependent rules, races, retries and dedup scope, event granularity, evolution (generations, id pins, new events) and module or team boundaries. Use for identifier/for, constraints, splitting streams or modules, ownership of interfaces, or changing persisted events. Not for: projection or query syntax (use `cratis-screenplay-projections`), reactions and captures (use `cratis-screenplay-automations-and-translations`)."
+description: Use when deciding Screenplay stream identities, invariant boundaries, races, retry scope or persisted-event evolution. Not for projection syntax or choosing automation and capture behavior.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-toolchain/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-toolchain
-description: "How to run and check Cratis Screenplay `.play` models: locating the model, choosing the standalone `screenplay` tool or the `cratis` CLI, the exact command behind each verdict V1 to V5 and what a pass looks like, the executable and renderable subsets, reading PLAY, STAGE and CLI-RENDER diagnostics, traps, and a compiled cheat-sheet. Use when choosing a compiler, running or reading a verdict, fixing a diagnostic, or deciding whether syntax binds or renders. Not for: what to model or the phase workflow (use `cratis-screenplay-modeling-lifecycle`), the MCP editing loop (use `cratis-screenplay-model-authoring`), rendering workflow (use `cratis-screenplay-render-and-gap-fill`)."
+description: Use when selecting a Screenplay compiler, running verdict checks or interpreting PLAY, STAGE and CLI diagnostics. Not for modeling phase decisions, AST editing proposals or the end-to-end rendering workflow.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-screenplay-ui-composition/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-screenplay-ui-composition
-description: Compose the user interface of a Cratis Screenplay `.play` model — `layout` and responsive `arrangement`, screen/dialog templates, component data-context bindings, exposed template configuration, command forms and columns, navigation contributions, application navigation regions (topbar/sidebar, module inherit/extend/override), toolbar slice buttons, blueprint template references, sample data packs, hierarchical outlets/routes, toolbar dialogs, package/icon selection, interaction `behavior`/`on`/`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/package configuration, command forms, navigation/toolbars, click or submit behavior, or theming. Do not use for a screen's own data and actions.
+description: Use when declaring Screenplay shells, reusable templates, forms, navigation, interaction wiring or themes. Not for a screen's own query data and action contract; use cratis-screenplay-read-surface.
 license: MIT
 ---
 
@@ -40,8 +40,8 @@ Every construct on this page is deferred from the executable model with
 information `PLAY0269`: it never blocks binding, and it is not evidence that a
 target renders it.
 
-The screens-release surface adds component data-context bindings, exposed template
-configuration, package/icon catalogs, manual form columns, hierarchical outlets,
+The screens-release surface adds component data-context bindings,
+exposed template configuration, package/icon catalogs, manual form columns, hierarchical outlets,
 routes, toolbars and dialog destinations, each with a separate support level
 (authoring accepted, executable admitted, runtime implemented). Discover the
 installed shape through MCP `syntax-schema`; details:
@@ -202,6 +202,9 @@ capability gap, never a flat-list fallback; Studio production proof is separate.
 
 ## The application shell: regions, slice buttons, blueprint references, sample data
 
+This covers application navigation regions (topbar/sidebar, module inherit/extend/override)
+and toolbar slice buttons alongside blueprint references and sample data.
+
 The shell's navigation is declared in the `layout` (`navigation topbar` / `navigation sidebar`, with `logo` and nested
 `item` lines) and each `module` states how it relates to a region: **inherit** (the default), **extend** (the
 application's items plus its own) or **override** (its own only). Toolbars gain `button <id> title "<text>" slice

package/package/corpus/skills/cratis-security-review/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-security-review
-description: Perform a focused security review of changed code in a Cratis application — injection, authentication and authorization, data exposure, secrets, event-sourcing-specific exposure, and the frontend — and report findings by risk. Use when asked for a security review or audit. Do not use to implement authentication and do not report a policy preference as a framework contract.
+description: Use when auditing a Cratis application change for security, especially permissions, untrusted input, secrets or permanent event-log exposure. Not for implementing authentication or general style review.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-social-feed-post/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-social-feed-post
-description: Write or review a short post for a social feed such as LinkedIn, where only the opening shows before "see more", the body is plain text with no markup, posts lead with media that carries the Cratis mark, and formatting tricks cost accessibility. Use when drafting, adapting or reviewing a feed post, choosing its media, or adapting it for another channel. Do not use for documentation pages, release notes, long-form articles, or anything rendered as Markdown, and hand length, voice and distribution questions to their own skills.
+description: Use when drafting, adapting or reviewing a short social-feed post or choosing its media. Not for documentation, release notes, long-form articles or Markdown content; length, voice and distribution have separate skills.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-specification-by-example/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-specification-by-example
-description: Structure and name executable specifications the Cratis way — one behavior per specification, a for_/when_/and_ path that reads as an English sentence, layered given/ contexts, and an explicit decision about what is not worth specifying. Use when deciding how to organize, name, or scope specifications in any language. Do not use for language mechanics; route to the C# or TypeScript specification skill for those.
+description: Use when deciding how to name, organize or scope Cratis executable specifications in any language. Not for C# or TypeScript fixture and assertion mechanics; use the language-specific sibling.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-specifications-csharp/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-specifications-csharp
-description: Write C# specifications with Cratis.Specifications using the Establish/Because/should_ pattern and the for_/when_/and_ folder hierarchy. Use when adding or restructuring C# specs in any Cratis repository, choosing between an isolated unit spec and an in-process scenario spec, or building reusable given/ contexts. Do not use for TypeScript or React specs, and do not use it to decide what a command, projection, or reactor should do.
+description: Use when adding or restructuring C# specifications, choosing their fixture surface or extracting reusable contexts in a Cratis repository. Not for TypeScript tests or deciding production behavior.
 license: MIT
 metadata:
   cratis-hint-paths: "**/for_*/**/*.cs"

package/package/corpus/skills/cratis-specifications-typescript/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-specifications-typescript
-description: Write TypeScript specifications in the Cratis BDD style using the given() helper, reusable context classes, Sinon stubbing, and the Chai .should fluent interface. Use when adding or restructuring TypeScript specifications, building a given/ context class, or laying out a for_/when_ specification folder. Do not use for C# specifications, and do not use it to decide what the code under specification should do.
+description: Use when adding or restructuring Cratis framework TypeScript specifications, given contexts or BDD folders. Not for C# tests, application React scenario selection or deciding production behavior.
 license: MIT
 metadata:
   cratis-hint-paths: "**/for_*/**/*.ts **/for_*/**/*.tsx"

package/package/corpus/skills/cratis-stage-rendering-and-sandbox/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-stage-rendering-and-sandbox
-description: "What Cratis Stage and `cratis render` do with a Screenplay `.play` model: the model shape Stage admits and refuses (`STAGE-ESM-*`, `PLAY0268` render refusals), what it emits (C# Arc/Chronicle backend, React/Vite scaffold with Arc `CommandForm` shell emission over Scene typed bindings, Debug specifications), managed publication, `--force`, recovery, scoped renders (`--scope`) and `--check`, authored-UI omission/parity checks, the unmanaged `Customizations/` seam, and the `cratis/stage` sandbox and `cratis/stage-specrunner` job. Use when deciding whether Stage can render a model, reading a blocked render, re-rendering safely, checking generated/runtime screen parity, or running the sandbox. Not for: authoring the model (use `cratis-screenplay-model-authoring`) or the render and gap-fill workflow (use `cratis-screenplay-render-and-gap-fill`)."
+description: Use when diagnosing Stage admission or blocked renders, checking screen parity, re-rendering safely or running its sandbox. Not for model authoring or the accepted-model delivery workflow.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-studio-mcp-safety-guidance/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-studio-mcp-safety-guidance
-description: Classify Studio MCP requests and interpret already-redacted output without discovering or invoking operations. Use whenever a user asks an agent to inspect, query, change, navigate, or automate Studio through MCP, or asks whether a Studio MCP operation is safe. No Studio MCP implementation authority is admitted, so every operation remains evidence-blocked.
+description: Use when classifying a Studio MCP request, interpreting already-redacted output or asking whether an operation is safe. Not for discovering, configuring or invoking Studio operations; their effects remain evidence-blocked.
 license: MIT
 ---
 

package/package/corpus/skills/cratis-technical-examples/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-technical-examples
-description: Design and verify developer-facing code samples, tutorial projects, and documentation snippets against real Cratis APIs. Use when adding or reviewing a runnable example, multi-client snippet, sample app, command/output pair, or migration before/after code. Do not invent API shapes or treat rendering as a compilation check.
+description: Use when adding or reviewing runnable Cratis examples, tutorial projects, multi-client snippets or command/output pairs. Not for page placement, release notes or treating rendering as compilation proof.
 license: MIT
 metadata:
   cratis-hint-paths: "**/Samples/**/*.{cs,ts,tsx}"

package/package/corpus/skills/cratis-writing-voice-and-cadence/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: cratis-writing-voice-and-cadence
-description: Review and revise existing prose so it reads as written by a person, by finding overused constructions and stock phrasing in one piece and structural sameness across a batch, then fixing both with specifics instead of injected variety, without changing any technical claim. Flags are editing prompts and never a verdict on who wrote something. Use when reviewing or rewriting documentation, release notes, pull request descriptions, posts or reviews for voice. Do not use for technical accuracy review, original drafting, authorship detection, or as a reason to touch approved copy without authorization.
+description: Use when revising existing prose for stock phrasing, voice or structural sameness across a batch. Not for original drafting, technical accuracy review, authorship detection or unauthorized edits to approved copy.
 license: MIT
 ---
 

package/package/corpus/skills/csharp-refactoring/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: csharp-refactoring
-description: 'Safely refactors C#/.NET code without changing behavior: rename, move, extract, inline, merge, consolidate, deduplicate, split, or modernize, including partial or generated declarations, public APIs, serialization and reflection names, friend assemblies, conditional compilation, and multi-targeted projects. Use when a request asks for a refactor, or calls a feature, bug fix, upgrade, or public nullability change a refactor and the behavior-changing part must be separated or declined. Not for ordinary feature or bug fixes, standalone framework or package upgrades, adding tests, or formatting-only work.'
+description: Use when restructuring C# code without changing behavior or separating a requested refactor from behavioral changes. Not for ordinary features, bug fixes, dependency upgrades, test additions or formatting alone.
 license: MIT
 ---
 

package/package/corpus/skills/directory-build-organization/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: directory-build-organization
-description: 'Organizes shared MSBuild policy across Directory.Build.props, Directory.Build.targets, Directory.Build.rsp, and Directory.Packages.props: centralizing repeated properties, targets, and package versions, hierarchy and import structure, props-versus-targets placement, and folder or project exceptions. Use when two or more projects repeat MSBuild policy, or an existing Directory.Build hierarchy has an import, placement, or layering defect, even if only one project is affected. Not for a one-project repo without a Directory.Build file, property value or condition semantics, legacy-to-SDK migration, or non-MSBuild systems.'
+description: Use when projects repeat MSBuild policy or an existing Directory.Build hierarchy has import, placement or layering defects. Not for isolated property semantics, legacy migration or a lone project without shared build files.
 license: MIT
 ---
 

package/package/corpus/skills/dotnet-aot-compat/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dotnet-aot-compat
-description: 'Makes .NET projects compatible with Native AOT and trimming by resolving IL trim and AOT analyzer warnings. Use when making a project AOT-compatible, fixing trimming warnings, resolving IL2026, IL2067, IL2070, IL2072, or IL3050, adding DynamicallyAccessedMembers annotations, or enabling IsAotCompatible. Not for publishing native AOT binaries, optimizing binary size, replacing reflection-heavy libraries, or .NET Framework projects.'
+description: Use when resolving .NET trim or AOT analyzer warnings, annotating reflection or enabling IsAotCompatible. Not for native binary publication, size optimization, library replacement or .NET Framework.
 license: MIT
 ---
 

package/package/corpus/skills/dotnet-trace-collect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dotnet-trace-collect
-description: 'Guides capturing diagnostic artifacts to diagnose production .NET performance problems: choosing tools, collecting performance data, and understanding trade-offs across Windows and Linux, .NET Framework and modern .NET, and container and non-container environments. Use when the user needs help choosing a diagnostic tool or collecting performance data for a .NET process. Not for crash dumps (use dump-collect), repository-level profiling workflows (use profiling), or analyzing collected traces.'
+description: Use when choosing a diagnostic tool or collecting .NET performance data for a particular runtime, OS or container environment. Not for trace analysis, crash dumps or a repository-wide profiling workflow.
 license: MIT
 ---
 

package/package/corpus/skills/dump-collect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: dump-collect
-description: 'Configures and collects crash dumps for modern .NET applications: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running processes, setting up collection in Docker or Kubernetes, and using dotnet-dump collect or createdump. Use when a crash dump must be enabled or captured. Not for analyzing or debugging dumps (lldb, windbg, dotnet-dump analyze), profiling or tracing (use dotnet-trace-collect), or .NET Framework processes.'
+description: Use when enabling or capturing crash dumps for CoreCLR or NativeAOT, including container deployments. Not for opening or analyzing dumps, performance tracing or .NET Framework processes.
 license: MIT
 ---
 

package/package/corpus/skills/eliminate-redundant-restores/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: eliminate-redundant-restores
-description: 'Removes repeated NuGet restores from multi-step .NET builds safely, including Directory.Build.rsp with -restore and safe restore suppression. Use when separate build, test, or publish steps each restore, or when NETSDK1004 or NETSDK1047 appears after --no-restore. Not for a slow first restore, a build with only one restore, version or lock-file errors, or general build slowness without a measured baseline (use the msbuild skill).'
+description: Use when multiple .NET build steps repeat NuGet restore or suppressing restore causes NETSDK1004 or NETSDK1047. Not for a slow first restore, version conflicts, lock-file errors or general build slowness.
 license: MIT
 ---
 

package/package/corpus/skills/extension-points/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: extension-points
-description: 'Owns MSBuild import and hook discovery: CustomBefore and CustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build and buildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. Use when imports or hooks do not run, run in the wrong order, or are overwritten. Not for a verdict on whether one Import needs an Exists guard (use the msbuild skill''s antipatterns reference), target Inputs/Outputs or incremental skipping (use target-authoring), or props-versus-targets placement (use directory-build-organization).'
+description: Use when MSBuild imports or hooks are missing, ordered incorrectly or overwritten, including NuGet build assets. Not for a single Import guard, target incrementality or props-versus-targets placement.
 license: MIT
 ---
 

package/package/corpus/skills/filter-syntax/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: filter-syntax
-description: 'Reference-only filter syntax for VSTest and Microsoft Testing Platform (MTP) with MSTest, NUnit, xUnit v3, and TUnit. Use when run-tests needs to create or translate a test filter after the platform and framework are known. Not for unfiltered runs or platform detection (use platform-detection); loaded by run-tests, never invoked directly.'
+description: Use when run-tests needs a filter translated after the .NET test platform and framework are known. Not for direct invocation, unfiltered runs or platform detection.
 license: MIT
 metadata:
   user-invocable: 'false'

package/package/corpus/skills/guiding-refactoring-with-code-health/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: guiding-refactoring-with-code-health
-description: Improve unhealthy code incrementally using measured Code Health feedback. Use when planning structural refactoring steps for complexity, size, cohesion or nesting and comparing each step with a baseline. Requires an opted-in cratis/codescene profile and available CodeScene MCP tools; otherwise skip. Do not use for a pre-commit change gate (use safeguarding-ai-generated-code) or portfolio debt ranking (use prioritizing-technical-debt).
+description: Use when planning measured structural refactoring for complexity, size, cohesion or nesting in a CodeScene-enabled, opted-in repository. Not for pre-commit safeguards or portfolio debt ranking.
 license: Apache-2.0
 ---
 

package/package/corpus/skills/including-generated-files/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: including-generated-files
-description: 'Owns MSBuild generated-artifact integration: a target that creates source, Content, None, or another physical file that is missing from compilation or output, target timing, evaluation-time glob misses, IntermediateOutputPath placement, and FileWrites clean tracking. Use when a generated file is missing from the build even if the prompt does not name the producing task. Not for general Include/Remove/Update semantics, item metadata or batching, duplicate declarations, Roslyn source-generator internals, or non-MSBuild systems.'
+description: Use when a file generated during MSBuild is missing from compilation or output because of target timing, globs or item registration. Not for general item semantics, duplicate declarations or Roslyn generator internals.
 license: MIT
 ---
 

package/package/corpus/skills/microbenchmarking/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: microbenchmarking
-description: 'Designs, configures, runs, and reviews BenchmarkDotNet (BDN) benchmarks, including project setup, efficient runs, and side-by-side performance comparisons. Use when BenchmarkDotNet is involved, or a .NET performance question needs measurement and BenchmarkDotNet is the likely tool. Not for profiling or tracing (use profiling or dotnet-trace-collect), production telemetry, or load and stress testing.'
+description: Use when authoring or reviewing BenchmarkDotNet benchmarks or comparing .NET code paths with controlled microbenchmarks. Not for runtime profiling, production telemetry or load and stress tests.
 license: MIT
 ---
 

package/package/corpus/skills/msbuild/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: msbuild
-description: 'Investigates MSBuild build failures, diagnoses build performance, and reviews build XML and extension contracts using binary logs. Use for failing dotnet build, restore, pack, or publish; .binlog capture and replay; project, props, and targets conditions; custom-target inputs/outputs; Import/Exists hooks and packed NuGet imports; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Not for legacy or non-SDK project migration, framework or package upgrades, SDK installation, C# refactoring, runtime profiling, assertions after a successful build, or non-MSBuild builds.'
+description: Use when troubleshooting MSBuild failures, slow builds or build-authoring contracts from project files and binary logs. Not for SDK installation, package upgrades, legacy migration, C# refactoring or runtime profiling.
 license: MIT
 ---
 

package/package/corpus/skills/orleans/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orleans
-description: '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.'
+description: Use when an Orleans task requires choosing state ownership, communication, scheduling or hosting guarantees against failure. Not for other actor stacks, relational-only CRUD or Cratis.Orleans job implementation.
 license: MIT
 ---
 

package/package/corpus/skills/platform-detection/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-detection
-description: '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/MTP 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.'
+description: Use when identifying a .NET test framework, VSTest versus MTP or conflicting runner configuration. Not for executing or filtering tests, command errors, dumps or migration; use run-tests for execution.
 license: MIT
 ---
 

package/package/corpus/skills/profiling/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: profiling
-description: '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).'
+description: Use when investigating a .NET application's CPU, GC, allocation, exception or contention behavior through runtime profiling. Not for crash dumps, benchmark design or replacing realistic load tests with ad-hoc traces.
 compatibility: Requires a .NET app or process to inspect; respects the repo's `AGENTS.md` commands first.
 license: MIT
 ---

package/package/corpus/skills/run-tests/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: run-tests
-description: '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.'
+description: Use before running .NET tests or choosing test commands, flags and filters, including command failures and dump collection. Not for platform identification alone, test authoring or interpreting coverage reports.
 license: MIT
 metadata:
   portability: portable

package/package/corpus/skills/safeguarding-ai-generated-code/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: safeguarding-ai-generated-code
-description: Gate AI-touched changes against Code Health regressions. Use when reviewing a staged diff or branch before commit, handoff or pull request with pre_commit_code_health_safeguard or analyze_change_set. Requires an opted-in cratis/codescene profile and available CodeScene MCP tools; otherwise skip. Do not use for a structural refactoring workflow (use guiding-refactoring-with-code-health) or risk-based test selection (use risk-based-testing-with-code-health).
+description: Use before committing or handing off an AI-touched diff in a CodeScene-enabled, opted-in repository. Not for structural refactoring steps, portfolio debt ranking or risk-based test selection.
 license: Apache-2.0
 ---
 

package/package/corpus/skills/target-authoring/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: target-authoring
-description: '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/Outputs 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.'
+description: Use when writing or fixing custom MSBuild target chains, dependency extension, returns or cleanup contracts. Not for general build-performance tuning, import discovery or non-MSBuild systems.
 license: MIT
 ---
 

package/package/corpus/skills/vectorization/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: vectorization
-description: '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.'
+description: Use when vectorizing a .NET scalar loop or reviewing SIMD behavior, memory safety, tails and fallbacks. Not for performance work unrelated to SIMD.
 license: MIT
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cratis/pi",
-  "version": "7.121.0",
+  "version": "7.122.1",
   "description": "Configuration-aware Cratis AI integration for Pi",
   "type": "module",
   "files": [