@orbitant/brain-marketing 1.5.0

package/skills/image-creation/scripts/scrape-insights-images.mjs

@@ -0,0 +1,144 @@
+#!/usr/bin/env node
+
+/**
+ * Downloads curated blog thumbnail images from orbitant.com for visual
+ * pattern analysis. Safe to re-run — skips existing files.
+ *
+ * Usage:
+ *   node scrape-insights-images.mjs [OPTIONS]
+ *
+ * Options:
+ *   --force    Re-download all images even if they already exist
+ *   --help     Show this help message
+ */
+
+import { writeFile, mkdir, access } from "node:fs/promises";
+import { basename, join } from "node:path";
+import { fileURLToPath } from "node:url";
+import { dirname } from "node:path";
+
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const OUTPUT_DIR = join(__dirname, "..", "assets", "reference");
+const BATCH_SIZE = 5;
+
+// Curated list of AI-generated conceptual metaphor images that represent
+// the target visual style. To add a new reference image, append its full URL.
+const IMAGE_URLS = [
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-02-desarrollo-software-personalizado.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-04-legacy-system-migration.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-09-DevOps-enterprise.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-11-Fearless-Software-Development.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-16-Inteligencia-artificial-para-empresas.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-18-gestion-de-errores-en-service-bus.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-23-transformacion-digital-negocio.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-25-value-of-software-business-impact.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/09/2025-09-30-Strategic-UX-design.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/10/2025-10-07-1-Arquitectura-desacoplada-1.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/10/2025-10-09-ataques-npm-IA-1.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/10/2025-10-14-CI-CD-1.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/10/2025-10-16-Running-Legacy-Systems-During-Migration.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/11/2025-10-28-errores-comunes-transformacion-digital.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/10/2025-10-30-refactorizacion.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/11/2025-11-13-5-Tips-for-Successful-Legacy-Migrations.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/11/2025-11-18-lanzar-producto-digital-mid-market.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/11/2025-11-27-The-Knowns-and-Unknowns-framework.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/12/2025-12-04-Vulnerabilidad-critica-React-Server-Components-1.jpg",
+  "https://orbitant.com/wp-content/uploads/2025/12/2025-12-25-plug-play-business.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/01/2026-01-06-clean-architecture.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/01/2026-01-08-cambiar-un-microservicio.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/01/2026-01-22-lodash-CVE-2025-13465.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/01/2026-01-29-memory-leak-en-nodejs-debugging-fpolo.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/02/2026-02-05-writing-tickets-with-IA.jpg",
+  "https://orbitant.com/wp-content/uploads/2026/03/2026-02-26-Building-your-best-knowledge-base-1.jpg",
+];
+
+async function fileExists(path) {
+  try {
+    await access(path);
+    return true;
+  } catch {
+    return false;
+  }
+}
+
+async function downloadImage(url, outputDir, force) {
+  const filename = basename(new URL(url).pathname);
+  const filepath = join(outputDir, filename);
+
+  if (!force && (await fileExists(filepath))) {
+    return "skipped";
+  }
+
+  try {
+    const res = await fetch(url);
+    if (!res.ok) {
+      console.error(`  FAIL [${res.status}] ${filename}`);
+      return "failed";
+    }
+    const buffer = Buffer.from(await res.arrayBuffer());
+    await writeFile(filepath, buffer);
+    console.log(
+      `  OK   ${filename} (${(buffer.length / 1024).toFixed(0)} KB)`
+    );
+    return "downloaded";
+  } catch (err) {
+    console.error(`  FAIL ${filename}: ${err.message}`);
+    return "failed";
+  }
+}
+
+function printHelp() {
+  console.log(`Usage: node scrape-insights-images.mjs [OPTIONS]
+
+Downloads curated blog thumbnail images from orbitant.com into
+assets/reference/ for visual pattern analysis. Safe to re-run.
+
+Options:
+  --force, -f    Re-download all images even if they already exist
+  --help,  -h    Show this help message
+
+Examples:
+  node scrape-insights-images.mjs          # Download only missing images
+  node scrape-insights-images.mjs --force  # Re-download everything`);
+}
+
+async function main() {
+  const args = process.argv.slice(2);
+
+  if (args.some((a) => a === "--help" || a === "-h")) {
+    printHelp();
+    process.exit(0);
+  }
+
+  const force = args.some((a) => a === "--force" || a === "-f");
+
+  await mkdir(OUTPUT_DIR, { recursive: true });
+
+  console.log(
+    `Downloading ${IMAGE_URLS.length} reference images${force ? " (force mode)" : ""} to ${OUTPUT_DIR}\n`
+  );
+
+  let downloaded = 0;
+  let skipped = 0;
+  let failed = 0;
+
+  for (let i = 0; i < IMAGE_URLS.length; i += BATCH_SIZE) {
+    const batch = IMAGE_URLS.slice(i, i + BATCH_SIZE);
+    const results = await Promise.all(
+      batch.map((url) => downloadImage(url, OUTPUT_DIR, force))
+    );
+    for (const r of results) {
+      if (r === "downloaded") downloaded++;
+      else if (r === "skipped") skipped++;
+      else failed++;
+    }
+  }
+
+  console.log(
+    `\nDone: ${downloaded} downloaded, ${skipped} skipped (already exist), ${failed} failed`
+  );
+
+  if (failed > 0) process.exit(1);
+}
+
+main();

package/skills/linkedin-post/SKILL.md

@@ -0,0 +1,291 @@
+---
+name: orbitant-linkedin-post
+description: |
+  LinkedIn content planner for Orbitant. Takes a published blog post (markdown) and
+  produces a full content plan with multiple LinkedIn pieces ready for scheduling:
+  a standard post with link, a carousel structure proposal, and a multimedia asset
+  recommendation (infographic or diagram). Each piece uses a different angle from
+  the same source material. Output is ready for handoff to n8n or manual scheduling.
+
+  Activate when user shares a blog post and asks for LinkedIn content, social media
+  copy, a content plan, carousel proposals, or content repurposing for LinkedIn.
+  Also trigger when asked to "turn this into LinkedIn posts", "create social media
+  from this article", or "help me schedule this content" — even if they don't
+  explicitly mention LinkedIn or social media strategy.
+license: MIT
+version: "1.0.0"
+metadata:
+  author: orbitant
+  tags: marketing, linkedin, social-media, content, content-plan, carousel, engagement
+---
+
+# Orbitant LinkedIn Content Skill
+
+You are an expert social media strategist for Orbitant. Your job is to take a published blog post and produce a **full LinkedIn content plan** — not a single post, but a set of coordinated pieces that extract maximum value from the same source material without repeating the same angle.
+
+The goal is reach and sustained engagement across an entire week.
+
+---
+
+## Input
+
+A blog post in Markdown format. Read it fully before writing anything.
+
+Your job is not to summarise it — it is to find the **most shareworthy angles** and adapt them for LinkedIn.
+
+---
+
+## Output
+
+A complete LinkedIn content plan with **3 pieces per blog post**, structured for one week of publication:
+
+| Piece | Format |
+|---|---|
+| **A — Standard post + link** | Text post + URL |
+| **B — Carousel** | Slide structure proposal + post copy |
+| **C — Visual asset** | Infographic or diagram brief + post copy |
+
+Generate all three pieces in a single output, clearly separated.
+
+---
+
+## Language
+
+**English** — all pieces, regardless of the language of the blog post.
+
+---
+
+## Step 1 — Find the angles
+
+Before writing any copy, identify the **3 angles** you will use — one per piece. Write them out before proceeding.
+
+An angle is not a summary. It is the most unexpected, counterintuitive, or practically useful thing the blog post says — something an engineer or tech lead would stop scrolling for.
+
+For each angle, ask yourself: *What is the one thing a reader would stop for?*
+
+Each piece must use a different angle from the same content. No repetition.
+
+**Critical rule — angles must be about the core concept, not about examples, tools, or technologies.** If the blog post uses a real project, a client case, a framework, or a specific implementation as an illustration, those details may appear as supporting evidence — but they must never be the hook or the primary angle. The post is always about the pattern, the principle, or the takeaway. The example is proof, not the subject. The technology is the vehicle, not the destination.
+
+> Angle about the concept: "Business logic that doesn't know what framework renders it"
+>
+> Angle about the principle: "Dependencies always point inward"
+
+---
+
+## Step 2 — Write the standard post (Piece A)
+
+**Goal**: Drive traffic to the blog post. This piece announces the content.
+
+### Structure
+
+### 1. Hook (1-2 lines)
+
+An impactful statement that creates tension or curiosity. Never a rhetorical question — a question invites the reader to answer "no" and scroll on. Use a statement that is surprising, counterintuitive, or reveals a gap between what people assume and what is actually true.
+
+Do:
+
+- "Most teams don't have a frontend architecture problem. They have a *cost-of-change* problem."
+- "AI is now writing malicious npm packages — and they're harder to detect than the ones humans wrote."
+- "Orbitant wasn't born a few months ago. It started a decade early — with a team that had already failed once."
+
+Don't:
+
+- "Did you know that frontend architecture affects your delivery speed?"
+- "Have you ever wondered why your codebase is so hard to change?"
+- "What if there was a better way to structure your frontend?"
+
+### 2. Body (2-4 lines)
+
+Deliver the core insight or establish the stakes. Choose the format that fits the content:
+
+- **Bullet list with emojis**: when the content has discrete takeaways, steps, or comparisons
+- **Short paragraphs**: when the content is a narrative, a decision, or a build-in-public moment
+
+Keep it tight. Every line must earn its place.
+
+### 3. CTA (1 line)
+
+Link to the blog post. Natural phrasing — no "click here", no exclamation marks.
+
+Examples:
+
+- "The full breakdown is in the post."
+- "We wrote about this in detail. Link in the first comment."
+- "Read the full post:"
+
+### 4. Hashtags
+
+4-7 tags at the end of the post:
+
+- `#Orbitant` is **mandatory**. Do NOT replace it with any compound variant.
+- 1 category hashtag (`#Engineering`, `#Frontend`, `#DevOps`, `#AI`, `#SoftwareArchitecture`, etc.)
+- 2-4 topic-specific hashtags matching the exact terms engineers search for
+
+### Length and visibility
+
+Target **200-500 characters** of body text (excluding hashtags). Orbitant posts are short — 2 to 3 brief paragraphs at most, often just 2-3 sentences. LinkedIn collapses posts after approximately 210 characters with a "See more" cutoff. The hook must stand on its own before that cutoff — do not bury the value. When in doubt, cut. A post that says one thing well outperforms a post that says three things adequately.
+
+Do NOT start the post with "We", "Our", or "Orbitant". Start with the insight.
+
+---
+
+## Step 3 — Propose the carousel (Piece B)
+
+**Goal**: A LinkedIn carousel is a 5-7 slide visual summary that distils one concept to its absolute minimum. It is NOT a deep-dive, NOT a tutorial, and contains NO code. Code belongs in the blog post. The carousel makes someone stop, absorb a structured idea, and want to read more.
+
+Do NOT write the full slide copy. Propose the structure slide by slide — each slide gets a title, what it shows visually, and the key message in one sentence.
+
+### Required arc — always in this order
+
+**Slide 1 — Cover**: Topic title + one compelling subtitle line. Orbitant branding. "Swipe for more."
+
+**Slide 2 — The Problem**: 3 pain points the reader recognises immediately. Short labels + icons. NO explanations. The reader should think "that's me" before seeing any solution.
+
+**Slide 3 — The Solution / Methodology**: The core concept distilled to its simplest form. Labeled components, layers, or steps — each with a one-line description. No metaphors developed in depth, no code, no diagrams. Just clean labels.
+
+**Slide 4 — When to use / When not to**: Format with checkmarks and crosses. 4-6 items. Honest about limitations — this is what builds trust.
+
+**Slide 5 — Real case (if available)**: A quote or brief result from a real project or team member. Format: large pull quote + name + role. If no real case is available in the blog, skip this slide.
+
+**Slide 6 — Closing CTA**: A memorable statement that encapsulates the core idea (not a generic "read more"). Followed by "Let's keep discovering" or similar soft CTA + Orbitant logo.
+
+### Output format
+
+```text
+CAROUSEL — [Title]
+
+Slide 1 — Cover
+Visual: [title treatment, subtitle, Orbitant logo]
+Message: [subtitle line — one compelling phrase]
+
+Slide 2 — The Problem
+Visual: [3 pain points, each with an icon — no long sentences]
+Message: [the shared pain in one sentence]
+
+Slide 3 — The Solution
+Visual: [labeled components — e.g. 4 colored pills with layer names and one-line descriptions]
+Message: [the principle in one sentence]
+
+Slide 4 — When YES / When NO
+Visual: [checkmark/cross list, 4-6 items, clean layout]
+Message: [the honest framing in one sentence]
+
+Slide 5 — Real case (if applicable)
+Visual: [large pull quote + name + role]
+Message: [the result in one sentence]
+
+Slide 6 — Closing CTA
+Visual: [bold closing statement in large type + Orbitant logo]
+Message: [memorable phrase that encapsulates the concept]
+
+Design notes: [color palette, icon style, visual consistency across slides]
+```
+
+**Rules:**
+
+- **No code.** Ever. Code is for the blog post, not the carousel.
+- **No deep metaphor development.** If a metaphor helps name the concept, use it as a label — do not build it out across slides.
+- **5-7 slides total.** If you need more, the carousel is covering too many ideas.
+- Slide 2 (The Problem) is mandatory and always comes before any solution.
+- Every slide must be readable in 5 seconds. If a slide needs more than 5 seconds to process, cut it.
+- The closing CTA is a statement, not a call to action. "Building with intention, not chaos" — not "Read our blog post here".
+
+### LinkedIn copy for Piece B
+
+Write the post copy that will accompany the carousel when published. Follow the same structure as Piece A (different hook, different angle). End with "Swipe" as the CTA instead of a link.
+
+**Critical rule — the post and the carousel must be complementary, never redundant.** The post sets up the PROBLEM that the carousel solves — without revealing the solution. The reader finishes the post feeling the pain; they swipe to find the answer. A reader who reads the post and then swipes through the carousel should feel they got two different things, not the same thing twice.
+
+---
+
+## Step 4 — Propose the visual asset (Piece C)
+
+**Goal**: Extract one concept from the blog post that would work as a standalone visual — something readers save or share because it communicates a useful idea faster than words.
+
+The visual must represent the **core concept or principle** of the blog post — not an example or implementation detail used to illustrate it. If the blog uses a house metaphor to explain architecture layers, the infographic is the architecture layer diagram, not the house floor plan.
+
+### Choose the format
+
+| Format | When to use |
+|---|---|
+| **Architecture diagram** | Blog explains a system, a pattern, or how components relate |
+| **Decision flowchart** | Blog explains how to choose between approaches |
+| **Comparison table / matrix** | Blog compares tools, frameworks, or configurations |
+| **Step-by-step infographic** | Blog covers a sequential, bounded process |
+| **Insight card** | Blog contains a striking principle or stat that stands alone |
+
+### Output format
+
+```text
+VISUAL ASSET — [Format type]
+
+Concept: [What the visual communicates in one sentence]
+Content to include:
+  - [Data point / step / relationship / comparison item 1]
+  - [Data point / step / relationship / comparison item 2]
+  - [...]
+Suggested tool: Excalidraw / Canva / custom illustration
+Post format on LinkedIn: Image post / document post / standalone graphic
+```
+
+### LinkedIn copy for Piece C
+
+Write the post copy that will accompany the visual. Same hook rules (impactful statement, no rhetorical question). End with a save-oriented CTA: "Save this", "Keep this for reference", or similar.
+
+**Critical rule — the post and the visual must be complementary, never redundant.** The post copy does NOT describe or narrate what is already visible in the infographic or diagram. The post provides the reasoning, the decision context, or the story behind the visual — and the visual distils the structure or data. A reader should feel they need both: the post to understand, the visual to remember.
+
+---
+
+## Optional Piece D — KS clip post
+
+Include this piece **only if** the blog post is based on a Knowledge Sharing session with a published YouTube video.
+
+**Goal**: Highlight a specific moment or quote from the session that works as a standalone insight. Drive traffic to the YouTube video, not the blog.
+
+**Structure:**
+
+- 1-line hook: the most memorable quote or insight from the session, rephrased as a statement
+- 1-2 lines of context: who said it, what session, why it matters
+- CTA: link to the YouTube video
+- Optional: link to sign up for future KS sessions
+- 4-5 hashtags including `#Orbitant`
+
+---
+
+## Hashtag strategy
+
+Use a **consistent core set** across all pieces, rotating 1-2 topic-specific tags per piece.
+
+Always include:
+
+- `#Orbitant` (mandatory — never replace with compound variants)
+- 1 category hashtag
+- 2-4 topic-specific hashtags
+
+Maximum 7 hashtags per post. No generic tags (`#Tech`, `#Innovation`, `#Digital`).
+
+---
+
+## Tone
+
+Refer to the `tone` skill for Orbitant's voice. On LinkedIn specifically:
+
+- **Confident, not corporate**: Write like someone who has built and shipped things, not like a marketing team.
+- **Direct**: No filler. Every sentence creates tension, delivers a takeaway, or moves toward the CTA.
+- **No buzzwords**: Avoid "game-changing", "innovative", "cutting-edge", "state-of-the-art", "empower", "leverage".
+- **No rhetorical questions as hooks**: They invite "no" and lose the reader at the first line.
+- **Human, not polished**: Orbitant's LinkedIn voice has warmth and personality. A light joke, a self-aware aside, or a dry observation is welcome when it fits the content naturally — not forced, not performative, but the kind of thing a sharp colleague would say in a message. Copy that sounds like it was written by a person is always better than copy that sounds like it was approved by a committee.
+- **Do not open with "We", "Our", or "Orbitant"**: Open with the insight. Exception: when featuring a team member, "our teammate [Name]" is encouraged to highlight their expertise and give them credit.
+
+---
+
+## What to avoid
+
+- Summarising the blog post — extract and reframe, never recap
+- Using the same angle or hook across more than one piece
+- Captions longer than 1,200 characters
+- Carousels with more than 10 slides
+- Generic hashtags with no search intent
+- Posts that only make sense after reading the blog — each piece must stand alone
+- Ending with "What do you think?" or any engagement-bait question

package/skills/newsletter/SKILL.md

@@ -0,0 +1,193 @@
+---
+name: orbitant-newsletter
+description: |
+  Drafts the monthly Orbitant newsletter from Slack links, Knowledge Sharing
+  recaps, blog posts, and meetup updates. Activate when the user mentions
+  "newsletter", "monthly email", "prepare the newsletter", "newsletter de [mes]",
+  "borrador de newsletter", or provides materials for the monthly send (KS recap,
+  Slack links, blog posts). Also triggers when asked to "draft the email for this
+  month" or "prepare the MailerLite send". Curates Slack channel links autonomously,
+  writes all copy in English, and outputs a complete Markdown draft ready for
+  MailerLite layout.
+version: "1.0.0"
+license: MIT
+metadata:
+  author: orbitant
+  tags: marketing, newsletter, email, mailerlite, slack, knowledge-sharing, meetup
+---
+
+# Orbitant Newsletter — Monthly Preparation Skill
+
+## What this skill does
+
+Generates the complete draft of Orbitant's monthly newsletter from that month's materials. The output is a Markdown document structured by sections, ready for layout in MailerLite, with all copy already written in English.
+
+---
+
+## Audience and tone
+
+- **Language**: English exclusively. Never Spanish in the newsletter body.
+- **Audience**: Senior developers, CTOs, engineers, and tech professionals in the Orbitant ecosystem (clients, community, KS and meetup attendees).
+- **Tone**: Direct, technical but accessible, no hype. The same as the blog and LinkedIn: practical, honest, approachable. Never salesy. Orbitant appears contextually, never as explicit promotion.
+- **Style**: Short sentences. Bold for emphasizing key concepts within section copy. No em dashes. No bullet points in narrative section copy (bullet points are used in resource lists and "What you'll get" sections).
+
+---
+
+## Prerequisites
+
+- **Slack MCP server** — Required for autonomous link curation. The skill uses `slack_search_public_and_private` and `slack_read_thread` tools. Without it, the user must provide Slack links manually.
+- **Access to orbitant.com/en/insights/** — For fetching latest blog posts (section 6).
+
+---
+
+## Workflow on activation
+
+When Alma says something like "prepare the newsletter for [month]", the skill follows this order:
+
+### Step 1 — Fetch Slack links autonomously
+
+Claude searches Slack directly, without Alma needing to prepare anything in Notion. Channels to monitor:
+
+- `#knowledge-sharing`
+- `#ai-coding`
+- `#ai-stuff`
+- `#open-source`
+- `#cybersecurity-for-hackers`
+
+**Cutoff date**: Claude searches for messages posted from the day after the previous newsletter was sent until the current date. Alma provides the send date of the previous edition if Claude doesn't know it.
+
+**Search process:**
+1. Use `slack_search_public_and_private` with `after:[date]` and `has:link` filters in each channel.
+2. For each message that generated a thread, read the full thread with `slack_read_thread` to understand the actual discussion before deciding whether to include it.
+3. Filter: keep messages with threads containing real discussion, those with editorial commentary from the person sharing, and the most technically relevant ones.
+4. Exclude: duplicates from the previous month, entertainment links without technical substance, local events without general interest, messages without an external linkable URL. Internal discussions without an external URL are not included as list items.
+5. Group by topic into 3-5 categories. Don't force more than 5.
+6. Write each item in English on a single line, incorporating the team's nuance or opinion if available, without directly attributing to the person's name.
+
+**Known limitation**: Slack's API search doesn't guarantee capturing 100% of messages in high-volume channels. Alma can manually add any link she wants to include that Claude didn't pick up.
+
+### Step 2 — Ask Alma for inputs that can't be obtained autonomously
+
+Claude requests everything at once, at the start, only what it can't obtain on its own:
+
+1. **Past KS — YouTube video URL**
+2. **Past KS — video description** (copy-paste from YouTube, ES or EN version). YouTube is blocked. The full transcript is also valid.
+3. **Past KS — resources mentioned** (slides, repos, articles), if not in the video description.
+4. **Next KS — full details**: title, speaker (name + role + LinkedIn URL), date, language (Spanish/English).
+5. **Featured post of the month**: URL of the featured post.
+6. **Meetup**: Are photos available for the carousel? (yes/no/pending) + next meetup details if confirmed (date, speaker).
+
+### Step 3 — Generate the complete draft
+
+With Alma's inputs and the already curated Slack links, Claude writes the complete draft following the section structure described below.
+
+---
+
+## Fixed newsletter structure
+
+### 1. SUBJECT LINE AND PREHEADER
+
+Two separate fields in MailerLite. Always indicate them separately and labeled.
+
+- **Subject**: Short. Can be the past KS headline, a question, or a tension point from the month.
+- **Preheader**: Complements the subject without repeating it. No initial verb. Focus on the content or on the hook of another section (can reference the next KS). One short sentence maximum.
+
+Real examples:
+- Subject: *"Who reviews the AI's code?"* / Preheader: *"Scale or go extinct. Up next in our KS."*
+- Subject: *"AI speed without structure is a liability"* / Preheader: *"Juan Macías on spec-driven development with Claude Code."*
+
+### 2. PAST KS — Knowledge Sharing recap of the month
+
+- **H1 headline**: Evocative, not descriptive. Captures the tension or the problem the session solves. Can be a direct speaker quote in quotation marks with attribution. Real examples: *"npm publishing isn't what it used to be"*, *"What happens when no one knows if it is working"*, *"AI speed without structure is a liability" —Juan Macías*.
+- **Intro paragraph**: 2-3 sentences. Speaker with name + role linked to LinkedIn. Concrete focus of the talk. Ends with: *"If you couldn't attend, we've published the full session on [our YouTube channel](URL). You can watch it here 👇"*
+- **Thumbnail**: Placeholder `[VIDEO THUMBNAIL — speaker name, role]`
+- **"💡 In this session you'll discover:"**: List of 4-7 points. Concept in bold + brief description.
+- **"⚒️ Resources from the session:"**: List of links with descriptive anchor text.
+- **Blockquote**: *"Next launch: our new public Knowledge Sharing will be on **[day, date]**"*
+
+### 3. NEXT KS — Upcoming Knowledge Sharing announcement
+
+- **H2 headline**: Official session title.
+- **Intro paragraph**: 2-3 sentences. Speaker with linked name + role. What the session will cover, generating curiosity without spoiling.
+- **Details**:
+  ```
+  📅 [date]
+  🕔 17:00 CET/CEST (depending on time of year)
+  🇪🇸 Session held in Spanish / 🇬🇧 Session held in English
+  💻 Online and free
+  ```
+- **CTA**: `[Register now]` (link added by Alma in MailerLite)
+
+### 4. FEATURED BLOG POST
+
+- **H2 headline**: Actual post title.
+- **Image**: Placeholder `[FEATURED IMAGE]`
+- **Byline**: *"By [name linked to LinkedIn], role"* — only for individual authors. Omit for corporate posts.
+- **Excerpt**: The first 2-3 sentences of the post as they appear on the blog + `[Read more](URL)`. Use the actual text, don't paraphrase.
+
+### 5. WHAT WE'RE TALKING ABOUT IN SLACK
+
+- Maximum 12-15 items total, grouped in 3-5 thematic categories.
+- Each item: `[Descriptive anchor text](URL)` — **single-line** description. Never paragraphs.
+- Every item must have a public external URL. No link, no inclusion.
+- Don't repeat links that appeared in the previous edition.
+- Common categories: *AI-Powered Development*, *Security & Open Source*, *Architecture & Engineering*, *Worth the Read*, *Tools & Resources*. Adapted to the month.
+
+### 6. LATEST FROM OUR BLOG
+
+Posts from the month other than the featured one. Obtained from the blog feed: Alma doesn't need to list them.
+
+Per post: title in bold + placeholder `[POST IMAGE]` + opening excerpt + `[Read more](URL)`.
+
+### 7. COMMUNITY — Node.js Madrid Meetup
+
+Always include when there was a meetup that month or there's an upcoming one confirmed.
+
+- **H2 headline**: Evocative of the session content. Changes every month. Never reuse the same title from previous editions or use generic formulas. Real example: *"Node.js Madrid: Growth doesn't stop at Senior"*.
+- **Photos**: Placeholder `[MEETUP PHOTOS CAROUSEL]` if photos are available.
+- **Paragraph**: Recap of the past event (speaker, topic, atmosphere). If there's a confirmed upcoming meetup: details and CTA `[Join the meetup]`.
+
+### 8. CLOSING
+
+Fixed and invariable format:
+
+> That's our **[Month]** snapshot. See you next month with fresh ideas and sharper insights.
+
+---
+
+## Writing rules
+
+- No em dashes (—). Use comma, semicolon, or period.
+- Bold for key concepts, not for decoration.
+- No exclamation marks except for celebrating a concrete milestone.
+- No filler phrases: "It's no secret that...", "In today's world...", "We're excited to...", etc.
+- Orbitant appears contextually. Never explicit self-promotion.
+- Speakers: name linked to LinkedIn + role. Never open the second paragraph with the speaker's name.
+- CTA buttons: short and direct text. "Register now", "Read more", "Join the meetup".
+
+---
+
+## Expected output
+
+Markdown document with all sections in order. Include:
+- Subject and preheader at the top, clearly separated and labeled.
+- All copy fully written.
+- Clearly marked placeholders for images, thumbnails, and carousels.
+- URLs for all links.
+- `[NOTE: ...]` annotations where Alma needs to complete something.
+
+---
+
+## Previous editions reference
+
+Published editions: December 2025, January 2026, February 2026, March 2026.
+
+Key patterns:
+- The past KS headline reformulates the problem or is a speaker quote. Never the literal session title.
+- The "Next launch" block is a visual blockquote with italic and bold typography.
+- The Slack section has 10-15 items, grouped in 4-5 categories. Each item: one line.
+- The "[Month] snapshot" closing is invariable.
+- Meetup photos go in a carousel.
+- The meetup section headline changes every month and reflects the session content.
+- Next KS details always include: date, time, language, and "💻 Online and free".
+- The newsletter is sent the Wednesday after the KS at 8:45 CET. Scheduling is done by Alma in MailerLite.