- add the streaming-pipeline workflow line to Common Workflows, preserving
  the ordered pipeline shape the deleted checklist alone carried
- drop the mnemonist memoization section: third overlapping package with
  no selection criterion beside the two the quick guide recommends
- use a .js entry point in the flame example; TypeScript execution is
  declared out of scope by this skill
- restore the CI-run guarantee for graceful-server.test.ts

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

@@ -48,3 +23,2 @@
 
-- [rules/streams.md](rules/streams.md) - Working with Node.js streams
-- [rules/caching.md](rules/caching.md) - Caching patterns and libraries
+- [rules/streams.md](rules/streams.md) - `pipeline()` composition, async-generator transforms, backpressure

@@ -18,3 +14,3 @@
 - In stream/ETL scenarios, prefer `async-cache-dedupe` for enrichment calls inside an `async function*` transform.
 
-## Memoization with mnemoist
+## Memoization with mnemonist

@@ -13,3 +13,3 @@
 
 ```bash
-pnpx @platformatic/flame app.ts
+pnpx @platformatic/flame run app.ts

@@ -11,3 +9,4 @@
 
 For multi-step processes, follow these high-level sequences before consulting the relevant rule file:
 
+**Streaming a large dataset** (CSV, ETL, ingestion): `createReadStream` → `async function*` transform → cached enrichment (`async-cache-dedupe`) → `await pipeline()` to the destination. See [rules/streams.md](rules/streams.md) and [rules/caching.md](rules/caching.md).

@@ -151,3 +128,3 @@
 ```typescript
 // Invalidate single entry
-await cache.invalidate('getUser', '123');
+await cache.clear('getUser', '123');

@@ -44,3 +20,1 @@
-
-await stop();
-```
+Every run also writes an LLM-friendly markdown hotspot report beside the .pb profile and HTML flamegraph; regenerate outputs from a saved profile with `flame generate <profile.pb>`, passing `--md-format=detailed` for a fuller report.

@@ -206,3 +211,3 @@
 ## Runnable example
 
-[assets/graceful-server.ts](assets/graceful-server.ts) is a complete close-with-grace HTTP server — its health endpoint flips to 503 during shutdown and keep-alive is disabled to drain connections — with the behavior pinned by [assets/graceful-server.test.ts](assets/graceful-server.test.ts), which CI runs.
+[assets/graceful-server.ts](assets/graceful-server.ts) is a complete close-with-grace HTTP server — its health endpoint flips to 503 during shutdown and keep-alive is disabled to drain connections. [assets/graceful-server.test.ts](assets/graceful-server.test.ts) pins that shutdown-state behavior with node:test, and CI runs it.

@@ -206,3 +211,3 @@
 ## Runnable example
 
-[assets/graceful-server.ts](assets/graceful-server.ts) is a complete close-with-grace HTTP server — its health endpoint flips to 503 during shutdown and keep-alive is disabled to drain connections — with the behavior pinned by [assets/graceful-server.test.ts](assets/graceful-server.test.ts), which CI runs.
+[assets/graceful-server.ts](assets/graceful-server.ts) is a complete close-with-grace HTTP server — its health endpoint flips to 503 during shutdown and keep-alive is disabled to drain connections. [assets/graceful-server.test.ts](assets/graceful-server.test.ts) demonstrates testing the same shutdown-state behavior with node:test against its own dependency-free copy of the handler, and CI runs it.

@@ -22,24 +22,6 @@ logger.info({ userId: user.id }, 'User created');
 logger.error({ err, orderId: order.id }, 'Failed to process payment');
 ```
 
-## Log Levels

@@ -40,4 +25,1 @@
-logger.error({ err, orderId: order.id }, 'Failed to process payment');
-```
-
 ## Transports