agentsclimarketplace

Archetypes storytelling arcs

Skill HDeibler/universal-design-principles/plugins/aesthetics-and-emotion-principles/skills/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.From its SKILL.md

Install
npx -y skills add HDeibler/universal-design-principles --skill archetypes-storytelling-arcs

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.6 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 1 file

1.7 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.