content-strategy

Turn content requests into a bilingual editorial workflow for Vue SSR marketing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns “what should we write” into a repeatable, bilingual editorial workflow for marketing the open-source Vue SSR starter kit, while preventing duplicate topics and keeping tone consistent.

Core Features & Use Cases

  • Editorial workflow for real shipping: research, propose angles, draft FR+EN, verify, optimize, then log outputs into an inventory and changelog.
  • Channel-specific playbooks: produce LinkedIn posts and long-form articles in the required structure, plus README and storefront copy guidance.
  • Governance and guardrails: enforce voice rules (including zero arrow characters), anti-duplication via a content inventory, and correct delegation boundaries to other skills for i18n placement, SEO meta, and visuals.

Quick Start

Ask the AI to write a LinkedIn post about wiring email security-code authentication in the Vue SSR starter kit for solo developers, and it will produce both French and English versions with the proper template, voice, and one clear CTA.

Frequently Asked Questions about content-strategy

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

FAQPage Schema
How do I create bilingual LinkedIn posts for marketing an open-source project?

Bilingual editorial workflows turn content requests into structured French and English LinkedIn posts or README copy. The workflow researches angles, drafts text, enforces tone-and-voice rules, verifies FR+EN parity, and logs outputs into an inventory to prevent duplicates.

How do I manage a content inventory to prevent duplicate topics in bilingual marketing?

A content inventory prevents duplicate topics by logging every drafted French and English output into a tracked changelog. The editorial workflow automatically checks this inventory during the proposal phase to ensure new angles do not overlap with previously shipped LinkedIn posts or storefront copy.

What is the best way to maintain tone and voice consistency across French and English content?

Maintaining tone and voice consistency requires applying strict editorial guardrails during the drafting phase. The workflow enforces specific voice rules across both French and English outputs, including prohibitions like zero arrow characters, ensuring bilingual content sounds unified and on-brand.

Does this editorial workflow handle SEO meta and i18n integration for landing pages?

The editorial workflow does not directly handle SEO meta or i18n integration. It verifies FR+EN parity for landing page marketing text and explicitly delegates i18n placement, SEO meta optimization, and visual creation to related specialized skills.

Can I use this workflow to draft README and storefront copy for a Vue SSR starter kit?

Yes, you can use this workflow to draft README and storefront copy for a Vue SSR starter kit. The workflow supports channel-specific playbooks for GitHub README text and landing page marketing copy, ensuring the output maintains bilingual FR+EN parity and tone consistency.

When should I not use an automated bilingual editorial workflow for open-source marketing?

You should not use this workflow for content that skips the FR+EN parity requirement or operates outside open-source marketing channels. It is specifically built to enforce strict tone-and-voice rules, prevent duplicate topics via an inventory, and manage bilingual LinkedIn, README, and storefront copy.