@cratis/pi 2.28.1 → 2.30.0

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

@@ -10,6 +10,17 @@ The two slice types that run without anyone pressing a button. A `capture` in a
 `Translate` slice turns outside data into events; a `reaction` in an `Automation`
 slice runs when something happens.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-captures-and-reactions/verification.json

@@ -3,6 +3,8 @@
   "input": "Translate external data into events and declare a reaction.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": ".cratis/screenplay/" },
+    { "kind": "skill-contains", "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`" },
     { "kind": "skill-contains", "value": "cannot be mixed in one clause" },
     { "kind": "skill-contains", "value": "`where` belongs to the reaction, not to one trigger" },
     { "kind": "skill-contains", "value": "Startup` and `Shutdown" }

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

@@ -10,6 +10,17 @@ Everything that changes the system: the `command` that expresses intent, the
 `event` it appends, the rules that can refuse it, and the strongly-typed values
 they are all built from.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-command-surface/verification.json

@@ -3,6 +3,14 @@
   "input": "Declare a Screenplay command with validation, authorization and concurrency.",
   "fixtures": [],
   "assertions": [
+    {
+      "kind": "skill-contains",
+      "value": ".cratis/screenplay/"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`"
+    },
     {
       "kind": "skill-contains",
       "value": "A second `identifier` on the same command is an error"

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

@@ -17,6 +17,17 @@ assumptions. Keep asking *"and then what happens?"* after every event, every
 command, every answer. Use business language. Do not discuss databases, APIs, or
 frameworks during modeling.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |
@@ -131,14 +142,24 @@ When one is found, ask the user to clarify, create the missing element, re-valid
    instances — ask *"can there be more than one of these at once?"* for each field.
 8. No cross-cutting infrastructure is modeled as a `Translate` slice.
 
-## One file, or a folder
+## Choose a file layout
+
+Treat `.cratis/screenplay/` as one application and choose the coarsest layout
+that keeps both the source and its diffs readable:
+
+- Keep one `application.play` while it stays readable top to bottom.
+- Use one file per module when modules are simple.
+- Use one file per feature when features have sub-features.
+- Use one file per slice when the model is large enough that a change must be
+  reviewable in isolation.
 
-Start with one file, read top to bottom. Reach for a folder when it stops being
-navigable — the invoicing sample is 981 lines with **one** module.
+Reviewability, not an arbitrary line count, triggers the next split. In a large
+model, one slice per file makes a scripted edit's blast radius visible in the
+diff instead of hiding cross-reference defects in a single enormous file.
 
-The folder layout mirrors the language, one folder per level: `application.play`
-at the root (`domain`, `import`, `concept`, `type`, `policy`, `persona`,
-`authentication`, `seed`), then `<Module>/<Module>.play`,
+At the most granular layout, folders mirror the language, one folder per level:
+`application.play` at the root (`domain`, `import`, `concept`, `type`, `policy`,
+`persona`, `authentication`, `seed`), then `<Module>/<Module>.play`,
 `<Module>/…/<Feature>/<Feature>.play`, and `<Module>/…/<Slice>/<Slice>.play` for
 one slice, whole. A slice file restates its `module` and `feature`; nothing is
 written twice.
@@ -155,7 +176,7 @@ and slices come back sorted by name. Never encode meaning in order.
 ## Verify
 
 ```shell
-screenplay path/to/model --warnaserror
+screenplay .cratis/screenplay/ --warnaserror
 ```
 
 - [ ] Zero errors **and zero warnings**. An unrecognized construct inside a slice

package/package/corpus/skills/cratis-screenplay-event-modeling/verification.json

@@ -3,6 +3,18 @@
   "input": "Facilitate an event modeling session and land the model as .play source.",
   "fixtures": [],
   "assertions": [
+    {
+      "kind": "skill-contains",
+      "value": ".cratis/screenplay/"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "Use one file per slice"
+    },
     {
       "kind": "skill-contains",
       "value": "expected StateChange, StateView, Automation or Translate"

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

@@ -18,6 +18,17 @@ application.** Nothing in it emits C#, TypeScript or any target artifact — tha
 is Stage's job, and Stage admits less than Screenplay parses. Author against that
 reality, not against the ecosystem diagram.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |
@@ -29,11 +40,32 @@ reality, not against the ecosystem diagram.
 Behavior below is read from the repository at tag `v4.12.1`. Reverify before
 claiming another version behaves the same.
 
+## Choose a file layout
+
+Treat `.cratis/screenplay/` as one application and choose the coarsest layout
+that keeps both the source and its diffs readable:
+
+- Keep one `application.play` while it stays readable top to bottom.
+- Use one file per module when modules are simple.
+- Use one file per feature when features have sub-features.
+- Use one file per slice when the model is large enough that a change must be
+  reviewable in isolation.
+
+Reviewability, not an arbitrary line count, triggers the next split. In a large
+model, one slice per file makes a scripted edit's blast radius visible in the
+diff instead of hiding cross-reference defects in a single enormous file.
+When files are split, restate their parent `module` and `feature`; the folder
+compiler merges declarations by name before resolving references.
+
+Always verify `.cratis/screenplay/` as a folder after a change. Verifying one
+split file alone produces false unknown-name diagnostics for declarations held
+in its siblings.
+
 ## Verify a model
 
 ```shell
 dotnet tool install -g Cratis.Screenplay.Tool
-screenplay                      # or: screenplay path/to/model
+screenplay .cratis/screenplay/ --warnaserror
 ```
 
 The tool takes **one positional argument** — a directory or a single `.play`

package/package/corpus/skills/cratis-screenplay-model-authoring/verification.json

@@ -0,0 +1,27 @@
+{
+  "skill": "cratis-screenplay-model-authoring",
+  "input": "Author and organize a Screenplay model in a repository.",
+  "fixtures": [],
+  "assertions": [
+    {
+      "kind": "skill-contains",
+      "value": ".cratis/screenplay/"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "source is the single flow model"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "Use one file per module"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "Use one file per slice"
+    }
+  ]
+}

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

@@ -10,6 +10,17 @@ A `projection` folds events into a read model. Its body is the **Projection
 Declaration Language**, an embedded sub-grammar with its own parser — not free
 text. This is half of every event model, and the half most easily got wrong.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-projections/verification.json

@@ -3,6 +3,8 @@
   "input": "Build a read model from events with the Projection Declaration Language.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": ".cratis/screenplay/" },
+    { "kind": "skill-contains", "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`" },
     { "kind": "skill-contains", "value": "AutoMap is on by default" },
     { "kind": "skill-contains", "value": "PLAY0191" },
     { "kind": "skill-contains", "value": "every event type in the system" },

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

@@ -9,6 +9,17 @@ license: MIT
 What the system can be asked, and what a user sees. The `readmodel` declares the
 shape, the `query` is the entry point, and the `screen` renders it.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-read-surface/verification.json

@@ -3,6 +3,8 @@
   "input": "Declare a Screenplay query and the screen that binds to it.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": ".cratis/screenplay/" },
+    { "kind": "skill-contains", "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`" },
     { "kind": "skill-contains", "value": "The tenant is the default and stays unstated" },
     { "kind": "skill-contains", "value": "belongs on a `from` parameter, never on a `filter`" },
     { "kind": "skill-contains", "value": "warnings, not errors" }

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

@@ -10,6 +10,17 @@ A `specification` is the acceptance criterion for a slice, written in the same
 document as the behavior it pins. Given/when/then, in business language, with
 concrete data.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-specifications/verification.json

@@ -3,6 +3,14 @@
   "input": "Write given/when/then specifications for a Screenplay slice.",
   "fixtures": [],
   "assertions": [
+    {
+      "kind": "skill-contains",
+      "value": ".cratis/screenplay/"
+    },
+    {
+      "kind": "skill-contains",
+      "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`"
+    },
     {
       "kind": "skill-contains",
       "value": "**`then` contains either events or an error \u2014 never both.**"

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

@@ -10,6 +10,17 @@ Event Modeling's wireframe step is a first-class part of the language. The shell
 the reusable shapes inside it, the forms bound to commands, and the navigation
 entries other modules contribute are all declared in the `.play` model.
 
+## Locate the model
+
+Look first in `.cratis/screenplay/` at the repository root. This is the
+conventional home for consumer-owned `.play` source; do not invent another
+location or search the whole repository before checking it.
+
+`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`. Never
+hand-copy Screenplay source between repositories. Keep Markdown that explains,
+questions or navigates the model in the repository's documentation; the `.play`
+source is the single flow model.
+
 ## Verified product sources
 
 | Package | Version | Purpose |

package/package/corpus/skills/cratis-screenplay-ui-composition/verification.json

@@ -3,6 +3,8 @@
   "input": "Declare the application shell, a screen template and a command form.",
   "fixtures": [],
   "assertions": [
+    { "kind": "skill-contains", "value": ".cratis/screenplay/" },
+    { "kind": "skill-contains", "value": "`cratis ai install` manages `.cratis/ai/`, not `.cratis/screenplay/`" },
     { "kind": "skill-contains", "value": "A form is discovered, not referenced" },
     { "kind": "skill-contains", "value": "declares no\n`fits slot`" },
     { "kind": "skill-contains", "value": "override-priority order" }

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

@@ -0,0 +1,93 @@
+---
+name: cratis-social-feed-post
+description: Write or review a short post for a social feed such as LinkedIn, where the opening has to survive the feed's truncation, the body is plain text with no markup, and the common formatting tricks cost accessibility and reach. Use when drafting, adapting or reviewing a feed post. Do not use for documentation pages, release notes, long-form articles, or anything rendered as Markdown.
+license: MIT
+---
+
+# Social feed post
+
+A feed post is not a short article. The feed shows a few lines and hides the rest behind a
+"see more" control, so the opening is not an introduction to the point — it is the entire
+advertisement for the post, and the decision to expand is itself a ranking signal.
+
+Everything below assumes a plain-text feed with no markup rendering. The character and line
+figures are unofficial approximations reported by third parties; no platform documents them,
+and they move with interface, font size and device width. Treat them as a target zone and
+re-check them against current official guidance rather than encoding them as durable rules.
+
+## The fold decides what the post is judged on
+
+On LinkedIn the cut is modelled two ways at once and lands on whichever runs out first:
+
+- a character budget of roughly 210 on desktop and 140 on mobile, and
+- a budget of about three rendered lines.
+
+**A blank line spends the line budget without spending characters.** A short opening on its
+own line is therefore cut *earlier* than the same words inside a paragraph. Putting the hook
+on its own line is usually still right, because it is what a scroller reads first, but it is
+a trade rather than a free improvement.
+
+## What the opening must do
+
+- **Finish a complete thought above the cut.** An opening severed mid-sentence has spent the
+  whole advertisement on half an idea.
+- **Stay short on purpose.** A brief opening sentence is a hook doing its job. Do not rewrite
+  one into a longer, smoother sentence for the sake of rhythm; that removes the
+  advertisement. This is the most common way a well-meaning editing pass makes a post worse.
+- **Earn the identifier before using it.** An opening that begins with a framework type or a
+  product name asks a scroller to care about a word they have no reason to recognize yet.
+  Name the friction first, then the mechanism.
+- **Skip the throat-clearing.** The first line is the point, not a preamble to it.
+
+Check the opening by reading only the first three lines and asking whether they are worth
+expanding. If the answer depends on the fourth line, the opening is wrong.
+
+## Never use Unicode pseudo-formatting
+
+Third-party tools offer pseudo-bold and pseudo-italic built from Mathematical Alphanumeric
+Symbols — the characters that look like `𝗕𝗼𝗹𝗱` and `𝘐𝘵𝘢𝘭𝘪𝘤`. Do not use them.
+
+- **Assistive technology cannot read them.** A screen-reader user hears "mathematical bold
+  capital T, mathematical bold small h" through an entire line, or hears nothing at all.
+- **They are not the letters they resemble.** Platform search and ranking index the actual
+  code points, so a styled keyword is no longer that keyword and the term is lost.
+
+Emphasis in a plain-text feed comes from sentence construction, line placement and what is
+said first. A point that needs visual weight belongs in an image with its own alt text.
+
+## Two things that cost reach outright
+
+- **No external link in the body.** Current ranking suppresses posts that carry one; the
+  convention is to put the link in a comment. Verify this at review rather than repeating it
+  as folklore, and never write the convention into the copy itself.
+- **No engagement bait.** "Repost if…", "Tag someone who…", "Agree?" are treated as spam
+  signals rather than as engagement. A genuinely answerable question that follows from the
+  argument is a different thing and is welcome.
+
+## Structure that survives a phone
+
+- One idea per post. A feed reader will not assemble two.
+- Short paragraphs, one to three sentences, and visibly different from each other in length.
+  A column of identically sized blocks reads as a generated template before it reads as an
+  argument.
+- Blank lines separate paragraphs and nothing else. Each one costs line budget above the fold.
+- No Markdown. The feed renders none of it, so `**bold**` and `# heading` reach the reader
+  as literal characters.
+- Hashtags on the last line only, never mid-sentence.
+- Every image needs alt text. A post whose point lives only in an unlabeled image has no
+  point for part of its audience.
+
+## Before publishing
+
+- The opening thought is complete above the fold on mobile as well as desktop.
+- No pseudo-formatted characters anywhere, including the hook.
+- No link in the body and no engagement bait in the close.
+- Every image carries alt text, and the post still makes sense with the images removed.
+- Every technical claim is one the underlying source actually supports, and any limitation
+  the post depends on is stated rather than implied.
+
+## Stop conditions
+
+Stop and ask when the account owner, the author's perspective, the evidence behind a claim,
+or an asset's permission is unresolved. Drafting a post is not authorization to publish,
+schedule, tag, mention or upload it.

package/package/corpus/skills/cratis-social-feed-post/verification.json

@@ -0,0 +1,14 @@
+{
+  "skill": "cratis-social-feed-post",
+  "input": "Draft a LinkedIn post about a framework feature and format it for the feed.",
+  "fixtures": [],
+  "assertions": [
+    { "kind": "skill-contains", "value": "A blank line spends the line budget without spending characters" },
+    { "kind": "skill-contains", "value": "Never use Unicode pseudo-formatting" },
+    { "kind": "skill-contains", "value": "Assistive technology cannot read them" },
+    { "kind": "skill-contains", "value": "A brief opening sentence is a hook doing its job" },
+    { "kind": "skill-contains", "value": "No external link in the body" },
+    { "kind": "skill-contains", "value": "No engagement bait" },
+    { "kind": "skill-contains", "value": "unofficial approximations" }
+  ]
+}

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

@@ -0,0 +1,99 @@
+---
+name: cratis-writing-voice-and-cadence
+description: Find and remove the sentence constructions and structural sameness that make written material read as machine-generated, across documentation, release notes, pull request descriptions, posts and reviews, without changing any technical claim. Use when reviewing or rewriting existing prose for voice. Do not use for technical accuracy review, for original drafting, or as a reason to touch approved copy without authorization.
+license: MIT
+---
+
+# Writing voice and cadence
+
+Material that is factually correct can still be unreadable in a way nobody can name. The
+usual diagnosis is "it sounds like AI wrote it", and the usual response is to rewrite by feel,
+which produces a second machine voice rather than a human one.
+
+The failure is measurable, and it has two halves. The smaller half is a set of sentence
+constructions used far past the density a person would use them. The larger half is
+structural sameness across a whole body of material: a reader meeting the second piece
+recognizes the format before reading a word of it.
+
+## The constructions
+
+None of these is wrong. One of any of them is a good sentence. What turns them into a tell is
+recurrence.
+
+| Construction | What it looks like |
+| --- | --- |
+| **Corrective tail** | "…, not a fresh count." The sentence ends by correcting itself |
+| **Balanced semicolon** | Two clauses of equal weight either side of a semicolon |
+| **"rather than"** | The same correction carried by a different connective |
+| **Em-dash pivot** | The dash used to swing into a closing clause |
+| **"That is what X is for"** | A pointer sentence standing in for an explanation |
+
+To measure rather than guess, count them. Searching for `, not a`, `; ` between two clauses,
+`rather than`, and an em-dash followed by a short closing clause takes a few minutes across a
+directory and turns an argument about taste into a number. Reading a draft aloud catches all
+of them faster than any tool.
+
+## Structural sameness is the more damaging half
+
+Look at ten pieces together, not one at a time:
+
+- **Every piece the same length and shape.** If most of them are three or four paragraphs
+  with the same paragraph weights, that is a template.
+  The fix for a template is not a better template.
+  Do not adopt a target shape: vary the paragraph count, and let paragraphs differ visibly
+  in weight.
+- **Every sentence the same length.** When sentence length barely varies within a piece, the
+  result is a monotone regardless of the words. Let it swing between four words and twenty-five.
+- **Every piece opening the same way.** An abstract noun phrase making a declarative
+  assertion — "A screen that needs…", "A registration test can…" — is one move. Alternate it
+  with a question, a direct address, a concrete moment, or a number.
+
+## Address somebody
+
+- **Say "you".** Material that tells a reader what to do should address that reader.
+- **Attributed writing should sound attributed.** Prose published under a person's name and
+  written entirely in the impersonal third person reads as documentation wearing a byline.
+  Opinion, judgement and preference belong to the named author and are theirs to give.
+- **First person is not a licence to invent.** Opinion is allowed; invented experience,
+  anecdotes that did not happen, and claimed observations the author did not make are not.
+  Where a named author owns the material, it stays blocked until that author reviews it.
+- **A question is allowed when the piece has earned it.** A question that follows from the
+  argument is not bait; one bolted on to harvest a response is.
+
+## Never trade a claim for a smoother sentence
+
+This is the part that makes a voice pass dangerous, and it is the reason to do one carefully
+rather than quickly.
+
+The risk is not an obvious rewrite. It is a hedge dissolving into nicer phrasing. "There is
+no need to" becomes "without needing to", and a limit quietly widens. "Not its meaning"
+becomes "and leaves its meaning alone", and a distinction softens. Both read better. Both
+changed what the text asserts.
+
+Before accepting any rewrite, confirm that:
+
+- every identifier and every number present before is still present, and none was invented;
+- every hedging word — not, never, only, may, unless, until — survives in substance;
+- every stated limitation survives, including one that reads as an awkward caveat, because it
+  is a caveat and it is deliberate;
+- the closing limitation or evidence statement is not thinned, relocated into a subordinate
+  clause, or dropped because it spoiled the ending.
+
+A mechanical check over identifiers, numbers and hedge counts catches most of this before a
+human reads a word, and is worth writing once for any corpus large enough to need a pass.
+
+## Work in tranches that can be read
+
+Rewriting is not a batch operation. Any body of material large enough to have a detectable
+voice is too large to rewrite in one pass with judgement, and a fast pass replaces one
+detectable format with another. Rewrite a tranche, read it, and only then continue.
+
+Where material carries a recorded approval, a rewrite invalidates it. Recording a fresh
+approval over copy nobody has read makes the record assert something false, after which every
+downstream check agrees with it. Size the tranche to what its owner will actually read.
+
+## Stop conditions
+
+Stop when a rewrite would change what the material claims, when the named author has not
+accepted a perspective being introduced on their behalf, or when the material is under an
+approval that the rewrite would invalidate without authorization to refresh it.

package/package/corpus/skills/cratis-writing-voice-and-cadence/verification.json

@@ -0,0 +1,13 @@
+{
+  "skill": "cratis-writing-voice-and-cadence",
+  "input": "This documentation reads like it was generated. Make it sound human without changing what it says.",
+  "fixtures": [],
+  "assertions": [
+    { "kind": "skill-contains", "value": "Never trade a claim for a smoother sentence" },
+    { "kind": "skill-contains", "value": "The fix for a template is not a better template" },
+    { "kind": "skill-contains", "value": "every hedging word" },
+    { "kind": "skill-contains", "value": "First person is not a licence to invent" },
+    { "kind": "skill-contains", "value": "Structural sameness is the more damaging half" },
+    { "kind": "skill-contains", "value": "Rewrite a tranche, read it, and only then continue" }
+  ]
+}

package/package/profile-catalog.json

@@ -43,6 +43,7 @@
         "cratis/cli",
         "cratis/cli/terminal-workbench",
         "cratis/components",
+        "cratis/content",
         "cratis/documentation",
         "cratis/full",
         "cratis/full/csharp",
@@ -559,10 +560,22 @@
         "typescript"
       ]
     },
+    {
+      "id": "cratis/content",
+      "availableTargets": [
+        "cratis-social-feed-post",
+        "cratis-writing-voice-and-cadence"
+      ],
+      "languages": [
+        "markdown",
+        "language-agnostic"
+      ]
+    },
     {
       "id": "cratis/documentation",
       "availableTargets": [
-        "cratis-documentation-writing"
+        "cratis-documentation-writing",
+        "cratis-writing-voice-and-cadence"
       ],
       "languages": [
         "markdown",

package/package.json

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