/new-post Skill Implementation Plan

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: Create a Claude Code skill that automates bilingual blog post creation with AI drafting and translation.

Architecture: A single prompt-based skill file at .claude/skills/new-post.md. No scripts or dependencies — Claude handles drafting, formatting, translation, and file creation using built-in tools.

Tech Stack: Claude Code skills (markdown prompt), Jekyll blog conventions

Design doc: docs/plans/2026-03-08-new-post-skill-design.md

Task 1: Create the .claude/skills/ directory

Files:

• Create: .claude/skills/ (directory)

Step 1: Create the directory

Run: mkdir -p .claude/skills

Step 2: Commit

git add .claude/skills/.gitkeep
git commit -m "chore: add .claude/skills directory"

Note: If git doesn’t track empty dirs, skip the commit and it will be committed with the skill file.

Task 2: Write the /new-post skill file

Files:

• Create: .claude/skills/new-post.md

Step 1: Write the skill file

Create .claude/skills/new-post.md with the following content. This is the complete skill — it instructs Claude on how to handle the two-phase post creation flow.

The skill must include:

1. Metadata header — name: new-post, description that triggers on post creation requests
2. Context section — blog structure, file paths, front matter template, existing post conventions
3. Input detection logic — instructions to detect idea vs full post, and detect language
4. Phase 1 instructions — draft/format the post, generate front matter, present for review using AskUserQuestion
5. Phase 2 instructions — translate, create both files with Write tool, show summary
6. Reference content — the exact front matter template and file naming convention

Key details the skill must encode:

• Posts live in _posts/en/ and _posts/es/
• Filename format: YYYY-MM-DD-slug.md
• Permalink format: /en/YYYY/MM/DD/slug.html (and /es/...)
• Author is always Elio Rincón
• Layout is always single
• Categories should include posts as the first category
• The blog’s tone: technical but conversational, direct, uses casual language (especially in Spanish)
• Existing posts use markdown with ## for sections
• No images directory — posts are text-only for now

Step 2: Commit

git add .claude/skills/new-post.md
git commit -m "feat: add /new-post Claude Code skill for bilingual post creation"

Task 3: Test the skill manually

Step 1: Test idea mode

Run /new-post with a short idea like: “quiero escribir sobre cómo usar MCP servers para automatizar tareas de desarrollo”

Verify:

• It drafts a full Spanish post
• Front matter is correct (all fields present, permalink format correct)
• It asks for approval before creating files
• After approval, it creates both _posts/en/ and _posts/es/ files
• Both files have correct front matter with matching slugs

Step 2: Test full post mode (Spanish)

Run /new-post with a full Spanish post (copy content from an existing post).

Verify:

• It uses the content as-is (doesn’t rewrite it)
• Generates correct front matter
• Translation to English preserves technical terms and tone

Step 3: Test full post mode (English)

Run /new-post with English content.

Verify:

• Creates Spanish translation
• Both files are correct

Step 4: Clean up test files

Delete any test posts created during testing.

Task 4: Add the skill to CLAUDE.md (if exists) or document usage

Files:

• Create or modify: CLAUDE.md or .claude/settings.json if needed

Step 1: Verify skill is discoverable

The skill should appear in Claude Code’s skill list automatically from .claude/skills/new-post.md.

Step 2: Commit any configuration changes

git add -A .claude/
git commit -m "docs: configure /new-post skill discovery"