Archetypes Storytelling Arcs logo

Archetypes Storytelling Arcs

Community
Deibler
archetypes-storytelling-arcs

Use this skill when designing narrative content — landing pages, case studies, onboarding flows, marketing campaigns, sales decks, ad arcs. Trigger when picking how to frame a customer story, when writing a launch campaign, or when the user mentions "this campaign feels flat" or "we need a better narrative." Sub-aspect of `archetypes`; read that first.

Overview

PublisherDeibler
Repositoryuniversal-design-principles
Skill namearchetypes-storytelling-arcs
Stars
9
Forks
3
Bundled files
1
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Deibler on GitHub. Read the source before you install it.

Installation

Install the Archetypes Storytelling Arcs AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Deibler/universal-design-principles/tree/main/plugins/aesthetics-and-emotion-principles/skills/archetypes-storytelling-arcs
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Deibler/universal-design-principles.git /tmp/universal-design-principles
mkdir -p .claude/skills
cp -r /tmp/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/archetypes-storytelling-arcs .claude/skills/archetypes-storytelling-arcs
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Archetypes Storytelling Arcs in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Archetypes Storytelling Arcs on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Archetypes Storytelling Arcs is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Storytelling arcs and the hero's journey

Stories are the most efficient way to convey emotional truth. A list of features is forgotten; a story of a user transformed by a product is remembered. Archetypes structure stories — the hero's journey is the most-cited template — and using them deliberately makes marketing, onboarding, and case studies dramatically more effective.

The hero's journey (Campbell, 1949)

Joseph Campbell distilled cross-cultural mythology into a single recurring pattern. The full version has 17 stages; the simplified product-narrative version has roughly 8:

  1. Ordinary world — the user's status quo (their pain, their constraint).
  2. Call to adventure — the product is introduced.
  3. Hesitation — the natural skepticism, the reasons not to.
  4. Mentor — the product (or its team) offers guidance.
  5. Crossing the threshold — first use, signing up.
  6. Trials — the work of using the product.
  7. Reward — the outcome, the transformation.
  8. Return / sharing — the user becomes an advocate.

This arc structures most successful marketing campaigns, customer case studies, and product launches.

Applying to product narratives

Customer case studies

A typical case study before applying the arc:

"Acme Corp uses our product. They report 40% productivity improvement."

Same case study with the arc:

"Acme Corp's marketing team was spending 4 days a week on reports — too much manual work, too little strategy. They tried our product as an experiment. After two weeks of integration, they automated 70% of their reporting workflow. Today, the team spends those reclaimed days on campaigns that have driven a 30% increase in qualified leads."

The arc gives the data emotional shape: pain → adventure → mentor → trials → reward.

Onboarding flows

Onboarding can follow the arc:

  • Welcome screen acknowledges the pain (ordinary world).
  • Setup is the call (adventure).
  • Tutorial is the mentor.
  • First successful task is the threshold-crossing.
  • Building momentum is the trials.
  • Achievement screen is the reward.
  • "Invite teammates" is the return / sharing.

Landing pages

Landing pages often follow a compressed arc:

  • Hero section: the call.
  • Problem section: the ordinary world.
  • Solution section: the mentor (your product).
  • Social proof: testimonials of others who completed the journey.
  • CTA: cross the threshold.

Marketing campaigns

A multi-touch campaign can play out across emails, ads, and content over weeks:

  • Week 1: name the problem (ordinary world).
  • Week 2: introduce the solution (call).
  • Week 3: address objections (hesitation).
  • Week 4: demo / trial (mentor + threshold).
  • Week 5: success stories (reward).

Picking the user's role

In product narratives, who is the hero? Three typical positionings:

The user is the hero; the product is the mentor

The user's transformation is the story; the product enables it. Most user-facing marketing positions this way. The user sees themselves in the story; the product is the magical artifact.

The product is the hero

Less common in modern marketing; more common in early advertising. The product itself is presented as the protagonist conquering the user's problem. Can feel inflated in modern contexts.

A different character is the hero

Case studies often position a specific named customer as the hero. Their transformation is the story.

The user-as-hero positioning is generally most effective because it lets the prospect insert themselves into the story.

Other arc patterns

The hero's journey isn't the only arc:

  • Three-act structure (setup, confrontation, resolution) — used in films, drama, and many product demos.
  • Problem-Agitation-Solution (PAS) — common in copywriting.
  • Before-After-Bridge (BAB) — present current state, desired state, the path between.
  • Story Brand framework (Donald Miller) — a 7-part framework derived from Campbell's work, applied to brand messaging.

Each is a structured way to give content emotional shape.

Anti-patterns

  • All features, no narrative. Bullet lists of features without the story of what they enable.
  • Inflated narrative. Treating routine product use as a hero's journey produces hyperbolic copy that erodes credibility.
  • No transformation. Stories that don't show change ("Customer uses our product. End.") fail to engage.
  • Hero confusion. Who is the protagonist? If unclear, the story flattens.
  • Skipping the trials. Stories that go directly from problem to triumph feel unrealistic; users know real adoption involves friction.

Heuristics

  1. The "what's the transformation?" check. Every effective narrative has a before/after. If your story has no transformation, it's not yet a story.
  2. The hero clarity test. Read your narrative. Who is the protagonist? If you can't tell in 3 seconds, fix.
  3. The trial honesty. Skipping over the work makes the story unbelievable. Brief acknowledgment of the friction makes the triumph credible.

Related sub-skills

  • archetypes (parent).
  • archetypes-brand-voice — voice consistency reinforces narrative.
  • storytelling (cognition) — narrative as memory aid.
  • framing (cognition) — how the story is framed affects user judgment.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Archetypes Storytelling Arcs AI skill do?

Use this skill when designing narrative content — landing pages, case studies, onboarding flows, marketing campaigns, sales decks, ad arcs. Trigger when picking how to frame a customer story, when writing a launch campaign, or when the user mentions "this campaign feels flat" or "we need a better narrative." Sub-aspect of `archetypes`; read that first.

Why use Archetypes Storytelling Arcs on TypingMind?

Because you install it once and use it with any model. Archetypes Storytelling Arcs is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Archetypes Storytelling Arcs in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Deibler/universal-design-principles/tree/main/plugins/aesthetics-and-emotion-principles/skills/archetypes-storytelling-arcs. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Archetypes Storytelling Arcs?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Archetypes Storytelling Arcs?

As many as you like. As long as a model supports skills, you can use Archetypes Storytelling Arcs with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Archetypes Storytelling Arcs AI skill free?

It is published on GitHub by Deibler. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇