[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVVAH5MM4AJSRVDMPDQASN":3,"skill-same:01M6JVVAH5MM4AJSRVDMPDQASN":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":57,"linkOnly":58,"markdownContent":59,"markdownBody":60,"frontMatter":61,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6JVVAH5MM4AJSRVDMPDQASN","archetypes-storytelling-arcs",null,"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.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002FSKILL.md",[18,23,28,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000038","人力资源",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56],"archetypes storytelling arcs","archetypes","storytelling","campaigns","when","launch campaign","frame","flows","case","narrative","how to","trigger","pages","writing","campaign","use","sales","landing","read","marketing","how","customer","2026-11-10 10:12:30",false,"---\nname: archetypes-storytelling-arcs\ndescription: '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.'\n---\n\n# Storytelling arcs and the hero's journey\n\nStories 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.\n\n## The hero's journey (Campbell, 1949)\n\nJoseph Campbell distilled cross-cultural mythology into a single recurring pattern. The full version has 17 stages; the simplified product-narrative version has roughly 8:\n\n1. **Ordinary world** — the user's status quo (their pain, their constraint).\n2. **Call to adventure** — the product is introduced.\n3. **Hesitation** — the natural skepticism, the reasons not to.\n4. **Mentor** — the product (or its team) offers guidance.\n5. **Crossing the threshold** — first use, signing up.\n6. **Trials** — the work of using the product.\n7. **Reward** — the outcome, the transformation.\n8. **Return \u002F sharing** — the user becomes an advocate.\n\nThis arc structures most successful marketing campaigns, customer case studies, and product launches.\n\n## Applying to product narratives\n\n### Customer case studies\n\nA typical case study before applying the arc:\n\n> \"Acme Corp uses our product. They report 40% productivity improvement.\"\n\nSame case study with the arc:\n\n> \"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.\"\n\nThe arc gives the data emotional shape: pain → adventure → mentor → trials → reward.\n\n### Onboarding flows\n\nOnboarding can follow the arc:\n\n- Welcome screen acknowledges the pain (ordinary world).\n- Setup is the call (adventure).\n- Tutorial is the mentor.\n- First successful task is the threshold-crossing.\n- Building momentum is the trials.\n- Achievement screen is the reward.\n- \"Invite teammates\" is the return \u002F sharing.\n\n### Landing pages\n\nLanding pages often follow a compressed arc:\n\n- Hero section: the call.\n- Problem section: the ordinary world.\n- Solution section: the mentor (your product).\n- Social proof: testimonials of others who completed the journey.\n- CTA: cross the threshold.\n\n### Marketing campaigns\n\nA multi-touch campaign can play out across emails, ads, and content over weeks:\n\n- Week 1: name the problem (ordinary world).\n- Week 2: introduce the solution (call).\n- Week 3: address objections (hesitation).\n- Week 4: demo \u002F trial (mentor + threshold).\n- Week 5: success stories (reward).\n\n## Picking the user's role\n\nIn product narratives, who is the hero? Three typical positionings:\n\n### The user is the hero; the product is the mentor\n\nThe 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.\n\n### The product is the hero\n\nLess 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.\n\n### A different character is the hero\n\nCase studies often position a specific named customer as the hero. Their transformation is the story.\n\nThe user-as-hero positioning is generally most effective because it lets the prospect insert themselves into the story.\n\n## Other arc patterns\n\nThe hero's journey isn't the only arc:\n\n- **Three-act structure** (setup, confrontation, resolution) — used in films, drama, and many product demos.\n- **Problem-Agitation-Solution** (PAS) — common in copywriting.\n- **Before-After-Bridge** (BAB) — present current state, desired state, the path between.\n- **Story Brand framework** (Donald Miller) — a 7-part framework derived from Campbell's work, applied to brand messaging.\n\nEach is a structured way to give content emotional shape.\n\n## Anti-patterns\n\n- **All features, no narrative.** Bullet lists of features without the story of what they enable.\n- **Inflated narrative.** Treating routine product use as a hero's journey produces hyperbolic copy that erodes credibility.\n- **No transformation.** Stories that don't show change (\"Customer uses our product. End.\") fail to engage.\n- **Hero confusion.** Who is the protagonist? If unclear, the story flattens.\n- **Skipping the trials.** Stories that go directly from problem to triumph feel unrealistic; users know real adoption involves friction.\n\n## Heuristics\n\n1. **The \"what's the transformation?\" check.** Every effective narrative has a before\u002Fafter. If your story has no transformation, it's not yet a story.\n2. **The hero clarity test.** Read your narrative. Who is the protagonist? If you can't tell in 3 seconds, fix.\n3. **The trial honesty.** Skipping over the work makes the story unbelievable. Brief acknowledgment of the friction makes the triumph credible.\n\n## Related sub-skills\n\n- **`archetypes`** (parent).\n- **`archetypes-brand-voice`** — voice consistency reinforces narrative.\n- **`storytelling`** (cognition) — narrative as memory aid.\n- **`framing`** (cognition) — how the story is framed affects user judgment.\n","# Storytelling arcs and the hero's journey\n\nStories 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.\n\n## The hero's journey (Campbell, 1949)\n\nJoseph Campbell distilled cross-cultural mythology into a single recurring pattern. The full version has 17 stages; the simplified product-narrative version has roughly 8:\n\n1. **Ordinary world** — the user's status quo (their pain, their constraint).\n2. **Call to adventure** — the product is introduced.\n3. **Hesitation** — the natural skepticism, the reasons not to.\n4. **Mentor** — the product (or its team) offers guidance.\n5. **Crossing the threshold** — first use, signing up.\n6. **Trials** — the work of using the product.\n7. **Reward** — the outcome, the transformation.\n8. **Return \u002F sharing** — the user becomes an advocate.\n\nThis arc structures most successful marketing campaigns, customer case studies, and product launches.\n\n## Applying to product narratives\n\n### Customer case studies\n\nA typical case study before applying the arc:\n\n> \"Acme Corp uses our product. They report 40% productivity improvement.\"\n\nSame case study with the arc:\n\n> \"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.\"\n\nThe arc gives the data emotional shape: pain → adventure → mentor → trials → reward.\n\n### Onboarding flows\n\nOnboarding can follow the arc:\n\n- Welcome screen acknowledges the pain (ordinary world).\n- Setup is the call (adventure).\n- Tutorial is the mentor.\n- First successful task is the threshold-crossing.\n- Building momentum is the trials.\n- Achievement screen is the reward.\n- \"Invite teammates\" is the return \u002F sharing.\n\n### Landing pages\n\nLanding pages often follow a compressed arc:\n\n- Hero section: the call.\n- Problem section: the ordinary world.\n- Solution section: the mentor (your product).\n- Social proof: testimonials of others who completed the journey.\n- CTA: cross the threshold.\n\n### Marketing campaigns\n\nA multi-touch campaign can play out across emails, ads, and content over weeks:\n\n- Week 1: name the problem (ordinary world).\n- Week 2: introduce the solution (call).\n- Week 3: address objections (hesitation).\n- Week 4: demo \u002F trial (mentor + threshold).\n- Week 5: success stories (reward).\n\n## Picking the user's role\n\nIn product narratives, who is the hero? Three typical positionings:\n\n### The user is the hero; the product is the mentor\n\nThe 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.\n\n### The product is the hero\n\nLess 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.\n\n### A different character is the hero\n\nCase studies often position a specific named customer as the hero. Their transformation is the story.\n\nThe user-as-hero positioning is generally most effective because it lets the prospect insert themselves into the story.\n\n## Other arc patterns\n\nThe hero's journey isn't the only arc:\n\n- **Three-act structure** (setup, confrontation, resolution) — used in films, drama, and many product demos.\n- **Problem-Agitation-Solution** (PAS) — common in copywriting.\n- **Before-After-Bridge** (BAB) — present current state, desired state, the path between.\n- **Story Brand framework** (Donald Miller) — a 7-part framework derived from Campbell's work, applied to brand messaging.\n\nEach is a structured way to give content emotional shape.\n\n## Anti-patterns\n\n- **All features, no narrative.** Bullet lists of features without the story of what they enable.\n- **Inflated narrative.** Treating routine product use as a hero's journey produces hyperbolic copy that erodes credibility.\n- **No transformation.** Stories that don't show change (\"Customer uses our product. End.\") fail to engage.\n- **Hero confusion.** Who is the protagonist? If unclear, the story flattens.\n- **Skipping the trials.** Stories that go directly from problem to triumph feel unrealistic; users know real adoption involves friction.\n\n## Heuristics\n\n1. **The \"what's the transformation?\" check.** Every effective narrative has a before\u002Fafter. If your story has no transformation, it's not yet a story.\n2. **The hero clarity test.** Read your narrative. Who is the protagonist? If you can't tell in 3 seconds, fix.\n3. **The trial honesty.** Skipping over the work makes the story unbelievable. Brief acknowledgment of the friction makes the triumph credible.\n\n## Related sub-skills\n\n- **`archetypes`** (parent).\n- **`archetypes-brand-voice`** — voice consistency reinforces narrative.\n- **`storytelling`** (cognition) — narrative as memory aid.\n- **`framing`** (cognition) — how the story is framed affects user judgment.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs",{"tool":78,"command":79},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs",{"tool":81,"command":82},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill archetypes-storytelling-arcs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002FSKILL.md",true,[86],{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fnarrative-frameworks.md","REFERENCE","参考文档",1770,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Faesthetics-and-emotion-principles\u002Fskills\u002Farchetypes-storytelling-arcs\u002Freferences\u002Fnarrative-frameworks.md",[93,101,108,115,141,166],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":100},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":57},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,131,132,39,133,134,135,136,137,138,139,140],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":57},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[148,149,150,136,151,152,153,154,155,156,157,158,159,160,127,161,162,163,164,165],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":181,"publishedAt":57},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[172,175,178],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":179,"categoryName":180,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[168,182,183,184,185,186,187,162,188,128,189,190,191,192,39,193,194,195,196,197],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]