@kensio/skills 1.15.0 → 1.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kensio/skills",
-  "version": "1.15.0",
+  "version": "1.16.0",
   "description": "Install Kensio agent skills into any agent that reads SKILL.md.",
   "keywords": [
     "agent-skills",

package/skills/dynamodb-single-table/SKILL.md

@@ -3,7 +3,7 @@ name: dynamodb-single-table
 description: Model data in Amazon DynamoDB as one table by default, reading the current AWS guidance before committing to a schema, writing the access patterns down before any keys exist, holding every entity type in one table, overloading generic partition and sort keys across those types, overloading and sparsifying secondary indexes, and splitting items by write rate. Use when designing or reviewing a DynamoDB schema, when a CDK stack is about to gain a second table, when an entity needs a query it has no key for, when application code fetches from two tables to assemble one response, when a Scan or a filter expression appears, when a partition runs hot or a write throttles, and when asked how to model users, orders, events or tenants in DynamoDB.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Single-table design in DynamoDB

package/skills/github-issue-drafting/SKILL.md

@@ -3,7 +3,7 @@ name: github-issue-drafting
 description: Draft a GitHub issue from a short note or a rough idea, grounding every claim about the code in the repository the issue will be filed against, splitting work that is really two issues, and filing it with `gh` once the user has approved the draft. Use when turning a to-do item, a Slack message, a code TODO, a failing test or a bug report into an issue, when asked to "write up an issue for" something, to "raise", "file" or "open an issue", when asked whether something should be one issue or several, and when tidying the titles, types or labels of issues that already exist.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # GitHub issue drafting

package/skills/isolated-testing-style/SKILL.md

@@ -3,7 +3,7 @@ name: isolated-testing-style
 description: Write tests that start from given/when/then, use real collaborators through simulation rather than stubs and mocks, take their isolation from randomised data rather than shared setup and teardown, and assert behaviour rather than call counts. Use when writing or reviewing tests, when a test needs a collaborator faked, when reaching for a mock, spy, `toHaveBeenCalledWith`, `beforeEach`/`afterEach` fixtures or a hardcoded expected hash, when test setup has grown tangled, and when asked "how should I test this?".
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Isolated testing style

package/skills/pangram-check/SKILL.md

@@ -4,7 +4,7 @@ description: Send the prose of a finished document to Pangram, a commercial AI-t
 license: Apache-2.0
 compatibility: Needs a Pangram API key and network access. Every run is billed.
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 disable-model-invocation: true
 ---
 

package/skills/part-factory-test-data/SKILL.md

@@ -3,7 +3,7 @@ name: part-factory-test-data
 description: Build test data with @kensio/part-factory, keeping in the factory everything a test does not care about, passing dependencies at call time so factories stay independent, and choosing between StaticFactory, DynamicFactory, VariantFactory, MappedFactory and AsyncMappedFactory. Use when writing test fixtures or builders, when a test file is full of object literals, when a shared event, message or payload shape is being hand-written, when a required field is about to be made optional to ease test setup, and when tempted to wrap a factory in a helper function that applies overrides.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Building test data with Part Factory

package/skills/skill-template/SKILL.md

@@ -3,7 +3,7 @@ name: skill-template
 description: Scaffold a new agent skill, writing the SKILL.md and its frontmatter to the Agent Skills specification, then wrapping it as a plugin in this repo with package.json, plugin.json and a marketplace entry. Use when the user asks to "add a new skill", "create a skill", "write a SKILL.md" or "start a new plugin", and when checking whether an existing skill is portable between agents.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Skill template

package/skills/technical-prose-style/SKILL.md

@@ -3,7 +3,7 @@ name: technical-prose-style
 description: Write documentation, READMEs, code comments, commit messages, release notes and PR text as plain technical prose, by removing the constructions that make unedited LLM prose tiring to read. It targets significance tails, contrastive definition, negation framing, appositive tails, colon explainers and a vocabulary that keeps renaming the same thing. Ships a script that scores prose against Django, Go, Rust and Python documentation. Use when writing or editing docs, a README, a changelog, a blog post or any prose for human readers, when asked to improve, tighten or rewrite writing, when prose "sounds like AI" or "sounds like Claude", and when reviewing documentation in a pull request.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Technical prose style

package/skills/yulin-aws-simulation/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: yulin-aws-simulation
-description: Use the @kensio/yulin in-process AWS simulator well when testing AWS code, using it directly rather than building a harness around it, driving tests, local dev and production from one synthesized CDK template, deploying a whole cdk.out cloud assembly, intercepting SDK clients with SimSdk, controlling simulated time, matching service errors by name, and handling properties Yulin refuses to simulate. Use when writing or reviewing tests that touch AWS, when replacing aws-sdk-client-mock or hand-rolled AWS stubs, when a CDK stack needs testing, when test setup around Yulin is growing helper classes or wrapper functions, and when Yulin refuses a template property or an SDK command.
+description: Use the @kensio/yulin in-process AWS simulator well when testing AWS code, using it directly rather than building a harness around it, driving tests, local dev and production from one synthesized CDK template, deploying a whole cdk.out cloud assembly, intercepting SDK clients with SimSdk, driving HTTP requests into the simulation with SimAwsHttp, controlling simulated time, matching service errors by name, and handling properties Yulin refuses to simulate. Use when writing or reviewing tests that touch AWS, when replacing aws-sdk-client-mock or hand-rolled AWS stubs, when a CDK stack needs testing, when a CloudFront Distribution, its DNS records or its certificate need testing, when test setup around Yulin is growing helper classes or wrapper functions, and when Yulin refuses a template property or an SDK command.
 license: Apache-2.0
 metadata:
-  version: "1.15.0"
+  version: "1.16.0"
 ---
 
 # Testing with Yulin
@@ -213,6 +213,33 @@ scope has), so look on the other scope before concluding a service is missing. E
 plain `{ input: { ... } }` in place of a Command object. An assertion can therefore read a service
 back without adding an `@aws-sdk/client-*` package the production code has no use for.
 
+## Drive requests into the simulation
+
+Reading state back covers the resources. `SimAwsHttp` from `@kensio/yulin/serve` covers the path
+through them, by sending a request into the environment with nothing listening. It takes what the
+global `fetch` takes and answers with a `Response`:
+
+```typescript
+const http = new SimAwsHttp({ simAws });
+const response = await http.fetch("https://www.example.test/docs/x?a=1", { redirect: "manual" });
+
+// Then the apex redirect the CloudFront Function performs has been applied.
+expect(response.status).toBe(301);
+expect(response.headers.get("location")).toBe("https://example.test/docs/x?a=1");
+```
+
+A hostname simulated Route 53 answers for is requested by its own name, with no port to add and no
+`localUrl(...)` adapting (an `https` URL works with no certificate set up for it). That one request
+resolves the hostname, finds the Distribution its alias records point at, and runs the deployed
+CloudFront Function at viewer-request. The certificate, the Hosted Zone records, the Distribution's
+aliases and the function are covered together. A template assertion over the same stack passes with
+every Route 53 record missing.
+
+Reach for `serveSimAws` when the request comes from outside the process, such as a browser, `curl`
+or an SDK client pointed at a local endpoint. Both go through the same routing and service code, and
+`SimAwsHttp` leaves parallel test files no port to collide over. See
+[the serving docs](https://yulinsim.dev/serve/) for the API.
+
 ## Match service errors by name
 
 ```typescript