Marketing strategy — Vue SSR Starter Kit
The strategic method for marketing the open-source kit. This skill owns what to do and why:
positioning, the no-price monetization stance, campaigns, channel mix, competitive analysis, and
growth. The facts it reasons about live in marketing-content; the content that executes its
decisions is produced by the content agent via content-strategy. The marketing agent loads this
skill plus marketing-content.
Division of responsibilities
| Concern |
Where |
| Strategy, monetization stance, campaigns, channel/GTM, growth, competitive |
marketing-strategy (here) |
| Product facts, stack, features, differentiator, license, repo/npm, assets |
marketing-content (the facts) |
| Editorial workflow, tone/voice, channel playbooks, inventory, backlog |
content-strategy (the method) |
| Producing the posts/articles/README/page copy |
➜ delegate to the content agent |
| Authoritative stack/versions (runtime source of truth) |
package.json |
| i18n keys |
➜ delegate to translate |
| Meta, JSON-LD, hreflang, sitemap |
➜ See skill: seo |
| Code changes |
➜ delegate to vue / server |
| Visuals, layout, components |
➜ delegate to design |
➜ See skill: marketing-content — the facts this strategy reasons about.
➜ See skill: content-strategy — the editorial method that executes this strategy.
Core rules
- Evidence-led decisions — every recommendation is backed by real numbers. Stack/version numbers
come from
package.json, product facts from marketing-content. Never invent.
- The kit is free/MIT — never invent a price or paid tier. Monetization is the adoption-to-services
funnel, not a SaaS subscription. There is no pricing constant to read or change.
- Recommend, never code — the
marketing agent persists decisions and hands code/copy/visual
execution to the right agent. The write surface is references/*.md.
- Persist every decision — a recommendation that lives only in a reply is lost. Write it to the
matching reference with its rationale and date context.
- No
→ arrow in produced strategy artifacts (allowed only inside .claude/ config).
Language policy
The kit ships in 2 locales (SUPPORTED_LOCALES in src/shared/const.js: en, fr). Strategy artifacts
under references/ are English only. Localized execution (bilingual FR+EN copy) is the content agent's
job, propagated via the translate agent.
Workflows
Define or revisit the monetization stance
- Read
references/pricing.md. The kit is free/MIT — there is no price or tier.
- Frame the monetization as the adoption-to-services funnel: which adoption signals (stars, npm
installs, forks) you optimize and how they bridge to E-XODE consulting inbound.
- Recommend the stance with funnel rationale; persist to
references/pricing.md. Never invent a tier.
Plan a campaign
- Read
references/positioning.md (audience) and references/campaigns.md (calendar).
- Define objective, audience, channel, offer, timeline, success metric.
- Persist the plan to
references/campaigns.md; hand content to the content agent, visuals to design.
Set or sharpen positioning
- Work
references/positioning.md: ICP, segments, value proposition, differentiation.
- Cross-check
references/competitive.md for the one-line differentiation.
- Recommend the messaging spine; the content agent turns it into FR+EN copy.
Routing — read the right reference
| If you need… |
Read |
| ICP, segments, value proposition, differentiation |
references/positioning.md |
| The monetization stance, the free/services funnel |
references/pricing.md |
| The campaign frame and calendar |
references/campaigns.md |
| Go-to-market, channel mix, launch sequencing |
references/gtm.md |
| Competitor map, benchmark, watch list |
references/competitive.md |
Evals
Trigger and behavior checks live in evals/evals.json (judged via the skill-creator loop; no
automated runner). Validate structure with python3 .claude/skills/claude-anthropic/scripts/audit.py.
Source: e-xode/vue-ssr — distributed by TomeVault.
1---2name: e-xode-vue-ssr-marketing-strategy3description: Marketing strategy — Vue SSR Starter Kit4---56# Marketing strategy — Vue SSR Starter Kit78> The strategic **method** for marketing the open-source kit. This skill owns _what to do and why_:9> positioning, the no-price monetization stance, campaigns, channel mix, competitive analysis, and10> growth. The _facts_ it reasons about live in `marketing-content`; the _content_ that executes its11> decisions is produced by the `content` agent via `content-strategy`. The `marketing` agent loads this12> skill plus `marketing-content`.1314## Division of responsibilities1516| Concern | Where |17| ----------------------------------------------------------------------------- | -------------------------------- |18| Strategy, monetization stance, campaigns, channel/GTM, growth, competitive | `marketing-strategy` (here) |19| Product facts, stack, features, differentiator, license, repo/npm, assets | `marketing-content` (the facts) |20| Editorial workflow, tone/voice, channel playbooks, inventory, backlog | `content-strategy` (the method) |21| Producing the posts/articles/README/page copy | ➜ delegate to the content agent |22| Authoritative stack/versions (runtime source of truth) | `package.json` |23| i18n keys | ➜ delegate to translate |24| Meta, JSON-LD, hreflang, sitemap | ➜ See skill: seo |25| Code changes | ➜ delegate to vue / server |26| Visuals, layout, components | ➜ delegate to design |2728➜ See skill: marketing-content — the facts this strategy reasons about.29➜ See skill: content-strategy — the editorial method that executes this strategy.3031## Core rules32331. **Evidence-led decisions** — every recommendation is backed by real numbers. Stack/version numbers34 come from `package.json`, product facts from `marketing-content`. Never invent.352. **The kit is free/MIT — never invent a price or paid tier.** Monetization is the adoption-to-services36 funnel, not a SaaS subscription. There is no pricing constant to read or change.373. **Recommend, never code** — the `marketing` agent persists decisions and hands code/copy/visual38 execution to the right agent. The write surface is `references/*.md`.394. **Persist every decision** — a recommendation that lives only in a reply is lost. Write it to the40 matching reference with its rationale and date context.415. **No `→` arrow** in produced strategy artifacts (allowed only inside `.claude/` config).4243## Language policy4445The kit ships in 2 locales (`SUPPORTED_LOCALES` in `src/shared/const.js`: en, fr). Strategy artifacts46under `references/` are English only. Localized execution (bilingual FR+EN copy) is the content agent's47job, propagated via the translate agent.4849## Workflows5051### Define or revisit the monetization stance52531. Read `references/pricing.md`. The kit is free/MIT — there is no price or tier.542. Frame the monetization as the adoption-to-services funnel: which adoption signals (stars, npm55 installs, forks) you optimize and how they bridge to E-XODE consulting inbound.563. Recommend the stance with funnel rationale; persist to `references/pricing.md`. Never invent a tier.5758### Plan a campaign59601. Read `references/positioning.md` (audience) and `references/campaigns.md` (calendar).612. Define objective, audience, channel, offer, timeline, success metric.623. Persist the plan to `references/campaigns.md`; hand content to the content agent, visuals to design.6364### Set or sharpen positioning65661. Work `references/positioning.md`: ICP, segments, value proposition, differentiation.672. Cross-check `references/competitive.md` for the one-line differentiation.683. Recommend the messaging spine; the content agent turns it into FR+EN copy.6970## Routing — read the right reference7172| If you need… | Read |73| --------------------------------------------------------- | ----------------------------- |74| ICP, segments, value proposition, differentiation | `references/positioning.md` |75| The monetization stance, the free/services funnel | `references/pricing.md` |76| The campaign frame and calendar | `references/campaigns.md` |77| Go-to-market, channel mix, launch sequencing | `references/gtm.md` |78| Competitor map, benchmark, watch list | `references/competitive.md` |7980## Evals8182Trigger and behavior checks live in `evals/evals.json` (judged via the `skill-creator` loop; no83automated runner). Validate structure with `python3 .claude/skills/claude-anthropic/scripts/audit.py`.8485---86> Source: [e-xode/vue-ssr](https://github.com/e-xode/vue-ssr) — distributed by [TomeVault](https://tomevault.io).87<!-- tomevault:4.0:skill_md:2026-06-15 -->
tomevault-io