narrator
Use when explaining code to non-engineers, mixed audiences, or when a story-shape explanation beats a technical one. Layered-detail output — top layer is plain English, expand on request.
What this skill does
# narrator
Code-to-story translation. Layered detail. Top is plain English. Each layer below adds technical depth, only as deep as the audience wants.
## Audience modes
- **non-tech** — board / PM / customer. No code. Analogies + outcome focus.
- **mixed** — eng manager / lead. Light code. Architecture-level.
- **tech** — peer engineer who's new to this area. Real code. Patterns named.
If unspecified, ask once: "Who's the audience — non-tech, mixed, or tech?"
## Method
1. **Frame the story.** What's the protagonist (the user, the request, the data)? What problem are they solving?
2. **Top layer.** 1-3 sentences in audience-appropriate language. Outcome-focused.
3. **Layer 2 (offered, not pushed).** "Want the architecture?" — one paragraph, named components, no code.
4. **Layer 3 (offered).** Code-level — actual files, functions, data flow.
5. **Stop when audience stops asking.** Don't push tech depth on someone who got what they needed.
## Output shape
```
[Top — non-tech]
When you click "buy", the order goes through three stages: we check stock,
charge your card, and email you. If any step fails, nothing else fires —
your card isn't charged unless we have stock; you don't get an email unless
the charge worked.
[Want the architecture? — y/n]
[Want the code? — y/n]
```
## Rules
- **Top layer assumes zero domain knowledge.** Test: would your aunt understand it?
- **No code in non-tech mode.** Even snippets break the spell.
- **Analogies > jargon.** "It's like a queue at a coffee shop" beats "we have a FIFO buffer".
- **Don't dump.** Each layer is gated by user pull, not pushed.
- Layered offers are explicit, not implicit. Ask before deepening.
## Anti-patterns
- Starting with "the system has three components..." (tech mode bleeding in)
- Including a code block in non-tech output
- Multiple paragraphs of detail before checking if the audience wanted it
- Hedge words ("kind of", "sort of") that make non-tech think you're guessing
## When NOT to use
- Audience already speaks the codebase fluently — they don't want a story
- Active debugging — narration is a luxury
- Code review — `/review` skill, not narrator
## Subagent dispatch
- `Explore` to map the area before narrating
- `archaeologist` if the story is about why this exists
- Native CC fine for single-file narrations
## Value over native CC
CC will explain code. CC defaults to a level of technical detail it guesses from cues. Narrator forces explicit audience selection + layered pull-don't-push. Useful for: stakeholder reviews, customer-facing docs, onboarding non-eng PMs.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.