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
- Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
- Explain after the example, not before.
- Prefer short, direct sentences over padded ones.
- Use specific numbers when available and sourced.
- 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
- Clarify the audience and purpose.
- Build a skeletal outline with one purpose per section.
- Start each section with evidence, example, or scene.
- Expand only where the next sentence earns its place.
- 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
Source: affaan-m/ECC → .cursor/skills/article-writing/SKILL.md
1---
2name: article-writing-2
3description: "Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter."
4category: writing-and-content
5source_repo: affaan-m/ECC
6source_path: ".cursor/skills/article-writing/SKILL.md"
7source_url: https://github.com/affaan-m/ECC/blob/HEAD/.cursor/skills/article-writing/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/affaan-m/article-writing-2
10---
11
12# Article Writing
13
14Write long-form content that sounds like a real person or brand, not generic AI output.
15
16## When to Activate
17
18- drafting blog posts, essays, launch posts, guides, tutorials, or newsletter issues
19- turning notes, transcripts, or research into polished articles
20- matching an existing founder, operator, or brand voice from examples
21- tightening structure, pacing, and evidence in already-written long-form copy
22
23## Core Rules
24
251. Lead with the concrete thing: example, output, anecdote, number, screenshot description, or code block.
262. Explain after the example, not before.
273. Prefer short, direct sentences over padded ones.
284. Use specific numbers when available and sourced.
295. Never invent biographical facts, company metrics, or customer evidence.
30
31## Voice Capture Workflow
32
33If the user wants a specific voice, collect one or more of:
34- published articles
35- newsletters
36- X / LinkedIn posts
37- docs or memos
38- a short style guide
39
40Then extract:
41- sentence length and rhythm
42- whether the voice is formal, conversational, or sharp
43- favored rhetorical devices such as parentheses, lists, fragments, or questions
44- tolerance for humor, opinion, and contrarian framing
45- formatting habits such as headers, bullets, code blocks, and pull quotes
46
47If no voice references are given, default to a direct, operator-style voice: concrete, practical, and low on hype.
48
49## Banned Patterns
50
51Delete and rewrite any of these:
52- generic openings like "In today's rapidly evolving landscape"
53- filler transitions such as "Moreover" and "Furthermore"
54- hype phrases like "game-changer", "cutting-edge", or "revolutionary"
55- vague claims without evidence
56- biography or credibility claims not backed by provided context
57
58## Writing Process
59
601. Clarify the audience and purpose.
612. Build a skeletal outline with one purpose per section.
623. Start each section with evidence, example, or scene.
634. Expand only where the next sentence earns its place.
645. Remove anything that sounds templated or self-congratulatory.
65
66## Structure Guidance
67
68### Technical Guides
69- open with what the reader gets
70- use code or terminal examples in every major section
71- end with concrete takeaways, not a soft summary
72
73### Essays / Opinion Pieces
74- start with tension, contradiction, or a sharp observation
75- keep one argument thread per section
76- use examples that earn the opinion
77
78### Newsletters
79- keep the first screen strong
80- mix insight with updates, not diary filler
81- use clear section labels and easy skim structure
82
83## Quality Gate
84
85Before delivering:
86- verify factual claims against provided sources
87- remove filler and corporate language
88- confirm the voice matches the supplied examples
89- ensure every section adds new information
90- check formatting for the intended platform
91
92---
93
94**Source:** [`affaan-m/ECC`](https://github.com/affaan-m/ECC) → `.cursor/skills/article-writing/SKILL.md`