article-writing
This Claude Code skill generates long-form content like blog posts, guides, tutorials, and newsletters that maintain a consistent voice matching provided examples or brand guidance. Use it when you need polished written content longer than a paragraph and want to ensure voice consistency, logical structure, concrete examples, and credibility without generic AI phrasing or invented facts.
git clone --depth 1 https://github.com/affaan-m/ECC /tmp/article-writing && cp -r /tmp/article-writing/.cursor/skills/article-writing ~/.claude/skills/article-writingSKILL.md
# Article Writing Write long-form content that sounds like a real person or brand, not generic AI output. ## When to Activate - drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues - turning notes, transcripts, or research into polished articles - matching an existing founder, operator, or brand voice from examples - tightening structure, pacing, and evidence in already-written long-form copy ## Core Rules 1. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block. 2. Explain after the example, not before. 3. Prefer short, direct sentences over padded ones. 4. Use specific numbers when available and sourced. 5. Never invent biographical facts, company metrics, or customer evidence. ## Voice Capture Workflow If the user wants a specific voice, collect one or more of: - published articles - newsletters - X / LinkedIn posts - docs or memos - a short style guide Then extract: - sentence length and rhythm - whether the voice is formal, conversational, or sharp - favored rhetorical devices such as parentheses, lists, fragments, or questions - tolerance for humor, opinion, and contrarian framing - formatting habits such as headers, bullets, code blocks, and pull quotes If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype. ## Banned Patterns Delete and rewrite any of these: - generic openings like "In today's rapidly evolving landscape" - filler transitions such as "Moreover" and "Furthermore" - hype phrases like "game-changer", "cutting-edge", or "revolutionary" - vague claims without evidence - biography or credibility claims not backed by provided context ## Writing Process 1. Clarify the audience and purpose. 2. Build a skeletal outline with one purpose per section. 3. Start each section with evidence, example, or scene. 4. Expand only where the next sentence earns its place. 5. Remove anything that sounds templated or self-congratulatory. ## Structure Guidance ### Technical Guides - open with what the reader gets - use code or terminal examples in every major section - end with concrete takeaways, not a soft summary ### Essays / Opinion Pieces - start with tension, contradiction, or a sharp observation - keep one argument thread per section - use examples that earn the opinion ### Newsletters - keep the first screen strong - mix insight with updates, not diary filler - use clear section labels and easy skim structure ## Quality Gate Before delivering: - verify factual claims against provided sources - remove filler and corporate language - confirm the voice matches the supplied examples - ensure every section adds new information - check formatting for the intended platform
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
>
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
>
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.