marketing-content

Produce verified bilingual EN+FR marketing facts for the Vue SSR Starter Kit.

3|Updated Jan 14, 2023
One-click install
npx skills add https://github.com/e-xode/vue-ssr --skill marketing-content-e-xode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marketing-content
Source: https://github.com/e-xode/vue-ssr/tree/main/.claude/skills/marketing-content
Command: npx skills add https://github.com/e-xode/vue-ssr --skill marketing-content-e-xode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a single, reliable source of truth for the product facts needed to write accurate bilingual acquisition content for the Vue SSR Starter Kit, preventing version drift and invented metrics.

Core Features & Use Cases

  • Bilingual EN+FR acquisition facts: Ensures every acquisition asset is written with native French and English while keeping a humble, professional developer tone.
  • Canonical product inventory: Supplies verified kit identity, stack/version snapshot guidance (via package.json), and differentiator positioning for adoption-focused messaging.
  • Asset and i18n placement rules: Defines where LinkedIn marketing content lives in src/assets/linkedin/ and how landing/page copy is handled through i18n.
  • Hard constraints for safe, accurate publishing: Enforces constraints like never using the → arrow character in published copy, and documenting new pieces in content-inventory plus CHANGELOG.

Quick Start

Ask marketing-content to produce acquisition-ready facts for a specific claim (for example, “What does the kit include and which asset folders should I use for LinkedIn posts?”) so you can draft bilingual EN+FR content without inventing numbers.

Frequently Asked Questions about marketing-content

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create bilingual acquisition content for a Vue SSR starter kit?

To create bilingual acquisition content for a Vue SSR starter kit, you need verified product facts covering kit identity, stack versions, and differentiators to support native English and French developer adoption messaging.

Where should marketing assets and i18n copy be stored in a Vue SSR project?

Marketing assets and i18n copy in a Vue SSR project should be stored in dedicated directories, specifically placing LinkedIn marketing content in src/assets/linkedin/ and handling landing page copy through the i18n system.

How do I verify stack versions for developer adoption marketing materials?

You verify stack versions for developer adoption marketing materials by checking the package.json file, ensuring your acquisition facts reflect the accurate, current snapshot of the kit's technology stack to prevent version drift.

What constraints apply when publishing bilingual marketing content for developers?

When publishing bilingual marketing content for developers, strict constraints apply: never use the arrow character in published copy, maintain a humble professional tone, and document all new pieces in a content inventory and CHANGELOG.

Can I use this approach to prevent invented metrics in technical marketing copy?

Yes, using a canonical product inventory prevents invented metrics in technical marketing copy by providing a single reliable source of truth for product facts, ensuring all bilingual acquisition messaging remains accurate and verifiable.

What is the best way to maintain accurate product facts across multiple marketing channels?

The best way to maintain accurate product facts across multiple marketing channels is establishing a canonical inventory that supplies verified kit identity, positioning, and feature documentation, updated alongside every CHANGELOG entry.