Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

content-strategy

Sterne3

Forks0

Aktualisiert6. Juni 2026 um 09:02

Editorial method and content operations for the Vue SSR Starter Kit (e-xode/vue-ssr): the how-to-produce layer on top of the marketing-content facts, for content that markets the open-source kit. Covers the editorial workflow (research, propose, draft FR+EN, verify, optimize), operational tone and voice (Avoid/Prefer, no arrow character, bilingual discipline), per-channel playbooks (LinkedIn posts and long-form articles, landing/contact page copy via i18n, the GitHub/npm README storefront), audience personas and angles, the content inventory glossary (anti-duplication, follow-up radar), the editorial backlog, and the daily growth/SEO advisory playbook. Trigger when writing or improving a LinkedIn post or article, page marketing copy, README/storefront copy, brainstorming content ideas, or asking what to do today for content/SEO. Don't use for: canonical product/stack/feature facts (→ marketing-content), i18n key placement (→ translate), meta/JSON-LD/sitemap (→ seo), visuals or layout (→ design).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

e-xode

e-xode/vue-ssr

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Marktforschungsanalysten und MarketingspezialistenWirtschafts- und Finanzberufe·SOC 13-1161

Datei-Explorer

8 Dateien

SKILL.md

readonly

name

content-strategy

description

Content strategy — Vue SSR Starter Kit

The editorial method for marketing the open-source kit. This skill owns how to research, propose, write, verify, and optimize content across LinkedIn, the landing/contact page copy, and the GitHub/npm storefront. The facts it writes about (what the kit is, its stack, features, differentiator) live in the marketing-content skill. The content agent loads both.

Division of responsibilities

Concern	Skill
What the kit is, stack, features, differentiator, asset locations	`marketing-content` (the facts)
Editorial workflow, tone/voice, channel templates, personas	`content-strategy` (the method)
Content inventory (what's published) and backlog (what's next)	`content-strategy` references
Strategy, monetization stance, campaigns, channel mix, positioning	`marketing-strategy`
i18n key placement	➜ delegate to translate
Meta, JSON-LD, hreflang, sitemap	➜ See skill: seo
Visuals, layout, components	➜ delegate to design

Core rules

These are the canonical content rules; their authoritative source is the marketing-content skill — do not duplicate the facts here.

➜ See skill: marketing-content — bilingual FR+EN always, humble/concrete tone, no → arrow in produced content, back claims with real numbers (re-read package.json for versions), save LinkedIn assets under src/assets/linkedin/, document each piece. The operational how for each rule is in references/tone-and-voice.md.

➜ See skill: marketing-strategy — the strategy layer (positioning, monetization stance, campaigns, channels) that decides what content to produce and why; this skill executes those decisions.

Workflow

Understand the request: channel, audience, goal (adoption, credibility, feature announcement, ideas, daily advisory).
Read the inventory — references/content-inventory.md — before proposing anything. Skip duplicates; surface follow-ups.
Propose 2-3 angles when the topic is open (at least one follow-up, one new idea), pulling from references/editorial-backlog.md.
Load facts from the marketing-content skill; pick the angle from references/audience-messaging.md.
Draft FR + EN using the matching template in references/channel-playbooks.md and the voice in references/tone-and-voice.md.
Verify: both locales native, zero →, real numbers, one CTA. Run the self-checks in the references.
Save to the right path; update references/content-inventory.md and add a CHANGELOG.md entry under ## [Unreleased].
Hand off out-of-scope work: i18n keys ➜ delegate to translate; meta/sitemap ➜ See skill: seo; visuals ➜ delegate to design.

Routing — read the right reference

If you need…	Read
Voice, Avoid/Prefer, bilingual discipline	`references/tone-and-voice.md`
A template for a post, article, page copy, or README	`references/channel-playbooks.md`
The persona and the angle that lands	`references/audience-messaging.md`
What already exists (anti-duplication, follow-ups)	`references/content-inventory.md`
Ideas for what to write next	`references/editorial-backlog.md`
Content that touches SEO, or the daily growth/SEO advisory	`references/content-seo-bridge.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.

Mehr aus diesem Repository

gleiches Repository

vue-ssr-architecture

e-xode/vue-ssr

Architecture reference for the Vue SSR Starter Kit (e-xode/vue-ssr): Vue 3.5+ + Vite 7 + Express 5 + MongoDB 7 + Vuetify 4 + Pinia + Vue Router with locale-prefixed routing. Covers file structure, SSR lifecycle (entry-server/entry-client/renderToString), locale routing system (useLocalePath, /:locale(en|fr)/), layout system (public/minimal/app), shared utilities inventory (apiFetch, parseObjectId, dbHelpers, email, security), API endpoint patterns (setupXRoute), view/component naming, Vuetify gotchas, and environment variables. Trigger on any architecture question, file placement, new feature scaffolding, routing, SSR, or shared utility usage. Don't use for: auth flow details (→ vue-ssr-auth), Docker/CI deployment (→ vue-ssr-deployment), post-task validation (→ vue-ssr-hooks), UI/UX design (→ design agent).

2026-07-183

vue-ssr-hooks

e-xode/vue-ssr

Post-task validation system for the Vue SSR Starter Kit: the hooks agent runs a format → lint → build → test battery via the single `npm run validate` orchestrator, on user opt-in only. Covers the opt-in trigger (never automatic), the validate.mjs orchestrator (parallel stages, prettier/eslint --cache, git-digest sentinel skip), the short-circuit table (skip validation for non-code files, build only on .vue/.js), the dormant settings._json hooks, and the subagent validation blocker. Trigger on: validation failures, understanding why lint/build/test ran or didn't run, modifying the validation pipeline. Don't use for: app code architecture (→ vue-ssr-architecture), auth (→ vue-ssr-auth), deployment (→ vue-ssr-deployment), Claude config governance (→ claude-anthropic).

2026-07-183

brand-art-direction

e-xode/vue-ssr

Material Design 3 / Vuetify 4 art-direction charter for the Vue SSR Starter Kit (e-xode/vue-ssr): the opinionated, screenshot-verifiable brand-identity layer above design-scss and design-ux. Defines the clean-minimal direction (single indigo brand accent, neutral-gray chrome, bordered flat MD3 surfaces, 8px rhythm, restraint over decoration) as DECIDABLE screenshot-checkable systems: quiet surface rhythm, canonical hover/elevation per component archetype with sibling consistency, palette roles, decorative restraint, and an evidence-based pre-delivery checklist graded by the visual-qa agent. Trigger on ANY visual/finition or polish work on rendered views: card hovers, surface backgrounds, elevation, accent usage, hero/CTA styling. Load BEFORE design-scss/design-ux when styling views. Don't use for: SCSS token/mixin mechanics (→ design-scss), UX methodology (→ design-ux), Vuetify component API (→ vuetify-components), design routing (→ vue-ssr-design), marketing copy (→ content-strategy).

2026-06-063

marketing-content

e-xode/vue-ssr

Marketing and product-knowledge FACTS for the Vue SSR Starter Kit (e-xode/vue-ssr): the source of truth for acquisition content that markets the open-source kit itself. Covers the canonical content rules (bilingual FR+EN, humble tone, concrete numbers, never the → arrow character), where assets live (src/assets/linkedin/, page copy via i18n, the GitHub/npm storefront), and product facts: what the kit is (Vue 3.5 + Vite + Express 5 + MongoDB 7 + Vuetify 4 SSR boilerplate with auth, i18n, admin), its stack/version snapshot (authoritative source = package.json), feature inventory, and differentiator (a curated Claude Code agent/skill fleet). Trigger when you need the facts behind acquisition content: what the kit is, its features, stack, positioning, audience, license, repo/npm location, or asset locations. Don't use for: the editorial method, tone/voice, inventory/backlog and writing workflow (→ content-strategy), i18n keys (→ translate), page meta/structured data (→ seo), visual/layout design (→ design).

2026-06-063

marketing-strategy

e-xode/vue-ssr

Pure-marketing strategy for the Vue SSR Starter Kit (e-xode/vue-ssr): the strategic layer above the content factory, for marketing the open-source MIT kit. Owns global strategy, the no-price monetization model (the kit is free; success = developer adoption that funnels inbound to E-XODE services), campaign planning, channel and social strategy (LinkedIn, GitHub, dev.to, Reddit r/vuejs, npm), positioning and ICP, competitive analysis, and growth/funnel thinking (stars, installs, forks). Decisions persist as references (positioning, pricing, campaigns, gtm, competitive) and are handed to the content agent. Trigger when defining strategy, the monetization stance, planning a campaign, choosing channels, analysing competitors, or reasoning about the adoption funnel. Don't use for: writing the actual posts/articles/README/page copy (→ content agent + content-strategy), product facts (→ marketing-content), i18n keys (→ translate), meta/JSON-LD/sitemap (→ seo), code (→ vue/server), visuals (→ design).

2026-06-063

vue-ssr-deployment

e-xode/vue-ssr

Deployment and CI/CD reference for the Vue SSR Starter Kit: Docker multi-stage build, docker-compose split into a base (app, remote DB) plus a docker-compose.local.yml override (local mongo) switched via the COMPOSE_FILE variable in .env, GitHub Actions workflows (npm-publish on tags, npm-test on PR, docker-build to GHCR), production configuration (Helmet CSP, COOKIE_SECRET, graceful shutdown SIGTERM/SIGINT), Dependabot weekly npm updates. Trigger on any deployment, Docker, docker-compose local-vs-remote DB switch, CI/CD, production config, or infrastructure question. Don't use for: app architecture (→ vue-ssr-architecture), auth flow (→ vue-ssr-auth), post-task validation (→ vue-ssr-hooks).

2026-06-063

name

content-strategy

description

Content strategy — Vue SSR Starter Kit

The editorial method for marketing the open-source kit. This skill owns how to research, propose, write, verify, and optimize content across LinkedIn, the landing/contact page copy, and the GitHub/npm storefront. The facts it writes about (what the kit is, its stack, features, differentiator) live in the marketing-content skill. The content agent loads both.

Division of responsibilities

Concern	Skill
What the kit is, stack, features, differentiator, asset locations	`marketing-content` (the facts)
Editorial workflow, tone/voice, channel templates, personas	`content-strategy` (the method)
Content inventory (what's published) and backlog (what's next)	`content-strategy` references
Strategy, monetization stance, campaigns, channel mix, positioning	`marketing-strategy`
i18n key placement	➜ delegate to translate
Meta, JSON-LD, hreflang, sitemap	➜ See skill: seo
Visuals, layout, components	➜ delegate to design

Core rules

These are the canonical content rules; their authoritative source is the marketing-content skill — do not duplicate the facts here.

➜ See skill: marketing-strategy — the strategy layer (positioning, monetization stance, campaigns, channels) that decides what content to produce and why; this skill executes those decisions.

Workflow

Understand the request: channel, audience, goal (adoption, credibility, feature announcement, ideas, daily advisory).
Read the inventory — references/content-inventory.md — before proposing anything. Skip duplicates; surface follow-ups.
Propose 2-3 angles when the topic is open (at least one follow-up, one new idea), pulling from references/editorial-backlog.md.
Load facts from the marketing-content skill; pick the angle from references/audience-messaging.md.
Draft FR + EN using the matching template in references/channel-playbooks.md and the voice in references/tone-and-voice.md.
Verify: both locales native, zero →, real numbers, one CTA. Run the self-checks in the references.
Save to the right path; update references/content-inventory.md and add a CHANGELOG.md entry under ## [Unreleased].
Hand off out-of-scope work: i18n keys ➜ delegate to translate; meta/sitemap ➜ See skill: seo; visuals ➜ delegate to design.

Routing — read the right reference

If you need…	Read
Voice, Avoid/Prefer, bilingual discipline	`references/tone-and-voice.md`
A template for a post, article, page copy, or README	`references/channel-playbooks.md`
The persona and the angle that lands	`references/audience-messaging.md`
What already exists (anti-duplication, follow-ups)	`references/content-inventory.md`
Ideas for what to write next	`references/editorial-backlog.md`
Content that touches SEO, or the daily growth/SEO advisory	`references/content-seo-bridge.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.