technical-concept-storyteller

Files (6)

• SKILL.md
• anti-patterns.md · references/
• pattern-engine.md · references/
• quality-rubric.md · references/
• routing-map.json · references/
• voice-profile.md · references/

SKILL.md (first lines)

# Technical Concept Storyteller

Make the reader need the term before naming it.

## Core sequence

1. Start with a situation a practitioner can recognize.
2. Show why the obvious interpretation fails.
3. Explain the mechanism in plain language.
4. Name the technical concept.
5. Give one concrete example with realistic variables or supplied numbers.
6. Explain the decision consequence.
7. State the boundary: when this concept does not answer the question or what evidence is still missing.

## Example pattern

Do not start with:

`Saturation is a nonlinear response phenomenon...`

Prefer the reasoning shape:

`A channel can have the best historical return and still be the wrong place for the next unit of budget. Once additional spend starts producing less incremental response, the question changes. That is the saturation problem.`

Use the user's demonstrated language rather than copying this wording.

## Rules

- No dictionary voice unless requested.
- No fake analogies when the real work example is clearer.
- Do not translate standard professional terms merely to avoid English.
- Do not add jargon that never changes the practical conclusion.
- When uncertainty matters, make it visible.
- One strong example is better than five shallow examples.

## Completion

The reader should leave with a better question or decision rule, not just a memorized definition.

<!-- written-as-spoken:links start (generated by scripts/sync-links.mjs, do not edit by hand) -->

## Linked to Written as Spoken

This skill is a node in the Written as Spoken suite. The front door is `written-as-spoken` (`../../../../SKILL.md`), and the graph lives in `../../../../references/routing-map.json`.

When a request reaches this skill through `written-as-spoken`, Mamdouh's voice rules in `../../../../references/voice-dna.md` and `../../../../references/anti-slop.md` outrank this skill's own style defaults, the house profile is active, and facts come only from the user or from `story-researcher`.

Routes that pass through here:

- `technical_explainer` (explain a technical concept in the voice): first step, hands off to `written-as-spoken`

Hand your output to the next node in the route. When this skill is the last node, return the result to `written-as-spoken` so the draft goes through `../../../../scripts/lint.mjs` before the user sees it. When this skill is called directly, outside the suite, ignore this block.

<!-- written-as-spoken:links end -->

From imMamdouhaboammar/written-as-spoken, MIT.

More from imMamdouhaboammar/written-as-spoken