agentleFS
LittlpinguinLittlpinguin/marketing-cockpit-template/.claude/skills/copywriting/SKILL.md

copywriting

Skill9 starsChanged 14 days agoMITView on GitHub

Rédaction de pages web, landing pages et contenus longs pour {{COMPANY_NAME}}, appuyée sur le design system et les templates de sections réutilisables. À utiliser pour écrire ou réécrire le texte d'une page.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use parasite-seo, paywalls and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaznilmuzammil12-progSkill

    parasite-seo

    When the user wants to choose or execute third-party platform SEO (high-authority sites for rankings or backlinks). Also use when the user mentions "parasite SEO," "parasitic SEO," "barnacle SEO," "hosted content," "third-party publishing," "Medium SEO," "Reddit SEO," "GitHub parasite SEO," "LinkedIn Pulse SEO," "high-authority platforms," "distributed authority," "borrow domain authority," or "rank without own website." For GitHub-specific playbooks, use github. For Medium.com posts, use medium-posts. For Grokipedia, use grokipedia-recommendations. For AI answer-engine visibility (not platform selection), use generative-engine-optimization.

    Also in 4 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 18 projects that use this

  • CesarjoquinSkill

    free-tools

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    Also in 18 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 40 projects that use this

  • roerohanSkill

    emails

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

    Also in 22 projects that use this

  • ukunal91appSkill

    community-marketing

    Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel.

    Also in 25 projects that use this

  • +4 more from Cesarjoquin

The file

Files
SKILL.md

copywriting — rédaction web {{COMPANY_NAME}}

Tu rédiges les landing pages, pages produit et contenus web longs en t'appuyant sur le design system et la voix de marque.

Étape 0 — Doctrine de marque (OBLIGATOIRE)

Avant d'écrire la moindre ligne de copy :

  1. Charger 01-brand/checklist-pre-composition.md — règles de voix, anti-style-IA, typographie, assets, réutilisation.
  2. Charger 01-brand/voice.md — position de voix, vocabulaire, interdits.

Ne jamais produire sans. Si l'un des deux fichiers manque ou contient encore des {{...}}, arrêter et lancer /start-cockpit. Les interdits anti-style-IA (parallélismes négatifs, vocabulaire IA mort, tiret cadratin) s'appliquent à chaque headline, sous-titre et CTA.

Préflight obligatoire

  1. Lire 01-brand/voice.md — ton, vocabulaire, interdits.
  2. Lire 01-brand/style-guide.md — système visuel, tokens.
  3. Lire 05-web-content/CLAUDE.md — structure et conventions techniques.
  4. Parcourir les pages existantes dans 05-web-content/ pour calibrer le ton.
  5. Récupérer la matière source :
    • Lire 01-brand/messaging-framework.md — positionnement, formulations canoniques, chiffres clés.
    • Consulter _templates/inventory.md et scanner 05-web-content/ pour les pages similaires : structures qui ont fonctionné, sections réutilisables.
    • Piocher dans les archives des autres canaux (04-email/newsletter/editions/, 03-social-media/*/examples/) les formulations validées et les accroches qui résonnent.
    • Chaque chiffre utilisé doit venir de 01-brand/messaging-framework.md, de _sources/reports/ ou d'une référence externe citée.

Référence rapide du design system

ÉlémentValeur
Police principale{{BRAND_FONT_PRIMARY}}
Couleur principale{{BRAND_COLOR_PRIMARY}}
Accent{{BRAND_COLOR_ACCENT}}
Sombre{{BRAND_COLOR_DARK}}
Clair{{BRAND_COLOR_LIGHT}}
Dégradé{{BRAND_GRADIENT}}
Border-radius{{BRAND_BORDER_RADIUS}}
Style d'illustration{{BRAND_ILLUSTRATION_STYLE}}

Catalogue des templates de sections

Chaque landing page s'assemble à partir de sections modulaires :

SectionUsage
HeroHeadline principale + sous-titre + CTA principal
Énoncé du problèmePoints de douleur du persona
Solutions / FonctionnalitésProposition de valeur en 3-4 blocs
Preuve socialeLogos clients, chiffres, témoignages
Timeline / ProcessusÉtapes du processus
Tableau comparatifvs alternatives
Vitrine de chiffresGros chiffres
TémoignagesCitations avec portrait
FAQ accordéonQuestions fréquentes
Étude de casRésultats concrets
Pour quiBlocs par persona
CTA finalBloc de conversion avec dégradé

Séquence par défaut : Hero → Problème → Solutions → Preuve sociale → Chiffres → Témoignages → FAQ → CTA final.

Principes d'écriture

La clarté avant la créativité

S'il faut choisir entre clair et malin, choisir clair. Chaque page répond à UNE question.

La donnée en héros

Les chiffres sont l'élément visuel principal. Un gros chiffre vaut mieux qu'un paragraphe.

Le bénéfice avant la fonctionnalité

« Trouvez le bon expert en 48 heures » > « Accès à notre réseau de 100+ experts »

La précision avant le vague

« 8,8/10 de satisfaction (n=136) » > « Grande satisfaction »

Scannable

  • Un H2 par section
  • 2-3 phrases max par paragraphe
  • Blancs généreux
  • Un CTA max par section
  • Mobile-first (tester à 375px de large)

Bilinguisme (le cas échéant)

{{BILINGUAL_RULES}}

Personnalisations spécifiques à la marque

{{COPYWRITING_SPECIFIC_RULES}}

Règles état de l'art (2026)

Synthèse actionnable — voir docs/etat-de-lart/email.md pour le détail sourcé :

  1. Structure descendante : l'information la plus importante en premier, toujours. Aucun préambule institutionnel en ouverture (« Chez X, nous sommes fiers de… ») — la première phrase porte la promesse, la donnée ou la tension, le contexte vient après. Le contenu « entonne » vers le CTA : accroche → idée principale → preuve → CTA → secondaire.

Checklist avant livraison

  • Pages existantes relues pour calibrer le ton
  • Une proposition de valeur claire par page
  • La donnée en héros (chiffres visibles, pas enterrés)
  • Chaque chiffre vérifié contre la doctrine de marque (01-brand/messaging-framework.md, _sources/reports/) ou source externe citée
  • Scannable (titres, paragraphes courts, blancs)
  • Un CTA clair et unique par section
  • Design system respecté (couleurs, polices, border-radius)
  • Pas de photos stock ({{BRAND_BANNED_VISUALS}})
  • Vocabulaire de marque respecté
  • Versions bilingues si applicable
  • Rendu mobile testé
  • Entrée du calendrier éditorial mise à jour (02-strategy/calendar/calendar.md — statut + lien livrable)
  • Livrable indexé dans _templates/inventory.md (skill inventory, mode incrément)

Skills associées

  • copy-editing — relecture en 7 passes
  • image-generation — visuels de page
  • seo — optimisation on-page
  • brand-check — validation finale obligatoire

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.