This skill captures CTO Field Notes specific patterns that supplement the base blogging skill. Load both when drafting CTOFN posts.
The blogging skill (user-owned) covers Minto Pyramid, Flesch 65–70, ASD-STE100, strict I-voice, and universal delivery conventions. This skill adds CTOFN-specific voice patterns, featured image spec, and drafting workflow lessons.
CTO Field Notes featured images use a two-pane card layout, NOT a standalone infographic.
Two formats required per card — seesocial-media-cards skill for full details:
The diagram should capture ONE concept from the post. Options:
Do NOT generate standalone infographics for CTOFN. The two-pane card is the established format. The left pane carries the diagram; the right pane carries the title and excerpt.
These patterns come from Joseph rewriting Hermes drafts. When the draft feels "correct but flat," apply these.
Joseph uses two-word paragraphs for punch. Not fragments for rhythm (which is AI-slop), but complete thoughts compressed to their minimum.
Example (from "The Engineering Mind"):> Most people would have dismissed the claim.
>
> Not GM.
>
> They sent an engineer to investigate.
Hermes wrote this as one paragraph. Joseph's version creates a beat that the compressed version misses.
Rule: When a sentence delivers the twist or the key decision, let it stand alone.Joseph lists events line-by-line when the sequence matters. Each line is its own paragraph.
Example:> He went with the customer three nights.
> Chocolate Ice Cream. Started.
> Strawberry Ice Cream. Started.
> Vanilla Ice Cream. Wouldn't start.
Hermes wrote this as prose. Joseph's list format makes the pattern visible before the payoff.
Rule: When a sequence builds to a reveal, use one line per step.Joseph uses markdown blockquotes to include someone else's words, with a brief intro.
Example:> After I published last week's field note, Sumit summarized the post on LinkedIn and posted this:
>
> > It's no longer about whether leaders still write code...
Rule: Don't paraphrase when you can quote. Introduce the person, link to the source, let them speak.Joseph's examples come from his actual work, not generic scenarios.
Example: "If the requirement is to build a customer dashboard for e-commerce, an engineer will clarify the specifics: is it all customers in the db or only those who bought in the last 30 days?"Hermes wrote a generic "bug report says the page is slow" example. Joseph's version is more specific, more interesting, and more credible.
Rule: Draw examples from Joseph's known work context ([client], client projects, engineering reviews).Joseph removed an entire debugging section from a draft. The post was tighter without it. Hermes tends to add sections to "cover the topic fully." Joseph cuts to keep the single argument sharp.
Rule: If a section can be removed without losing the main argument, remove it. CTOFN posts are 500–900 words. Every paragraph must earn its place.External references should feel like "a reader said something interesting," not "I researched this topic."
Example: "After I published last week's field note, Sumit summarized the post on LinkedIn..." Rule: Weave in LinkedIn posts, reader comments, and other people's ideas as natural story beats.Joseph uses honest admissions of not knowing something as a structural device. "I didn't know how to respond. It was like asking a fish to describe water." This earns the reader's trust before the framework arrives.
Rule: When Joseph admits he couldn't answer a question at first, that's a feature. Use it as the transition to the framework.Search for existing drafts (produce/hermes/blogs/drafts/), related library concepts (produce/hermes/library/), and prior blog posts on the topic. Read them before proposing an outline. This context shapes which angle to take and what to cut from earlier drafts.
Present a structured outline with:
Joseph reviews the outline before any drafting begins.
Write the draft following the outline. Apply all voice patterns from section 2.
Scan every paragraph for voice consistency. The default is "I" throughout.
"We" in the opening paragraph: "We" is acceptable in the first paragraph when describing shared human behavior (insurance, emergency funds, common habits) as a universal setup. The rule: commit to one pronoun per paragraph. If you open with "we," stay with "we" through the whole paragraph. Use a structural bridge (quote, principle, or section break) to transition to "I" for the personal narrative sections that follow. "We" in the body: In numbered sections and the close, "we" as general humanity is forbidden. Replace with "I" or a specific named group. Common trap: "We all know..." / "We prepare for..." when speaking about engineers or people in general — rewrite as "I know..." / "I prepare for..." or name the group ("The senior engineers I know...").The hardest rule to maintain and the most frequent violation is mid-paragraph voice switching (e.g., "We do X. I should do Y." in the same block).
Merging duplicate sections: When two numbered points cover the same ground with overlapping examples (e.g., "ship things" and "be findable" both listing GitHub/LinkedIn/blog posts), merge them into one section. The stronger heading wins. Renumber all subsequent sections and update the intro count. Tighter essay, no lost content.Check body word count (strip YAML frontmatter and Field Notes block). Target: 500–900 words. If under 500, expand one section with a concrete example or beat. If over 900, cut the weakest paragraph — CTOFN posts tighten, not pad.
Expect Joseph to rewrite significant portions. His version is almost always better. Compare his rewrite to yours and note the differences — they're voice signals for future sessions.
Run the no-ai-slop check. Apply Joseph's specific edits. Save to produce/hermes/blogs/drafts/.
[!hh] comments: These are editorial questions Joseph leaves in drafts. When a comment asks whether to include content or link to an existing post, read the linked post first. If it already covers the topic in depth, add a clean hyperlink in the text and cut the comment. Do not rewrite the same content twice.
Propose image options based on the two-pane card spec (section 1). Show the prompt before generating.
1. Don't generate standalone infographics for CTOFN. The two-pane card is the format. Left pane = diagram, right pane = title + excerpt.
2. Don't make only one format. Always create both landscape (1200×628) and square (1080×1080). Landscape for website OG, square for social posts.
2. Don't over-explain. Joseph's audience is executives and senior leaders. They don't need "what is a microservice" explanations.
3. Don't add sections to "cover the topic." CTOFN posts are tight. If a section can be cut, cut it.
4. Don't use generic examples. Draw from Joseph's consulting work, not hypothetical scenarios.
5. Don't paraphrase quotes. If someone said something worth including, quote them directly with attribution.
6. Expect Joseph to rewrite. His voice is specific. The draft is a starting point, not a final product.
7. Wrong word count method. Body word count excludes YAML frontmatter and Field Notes block. Use sed to strip both before counting. Counting the full file inflates by 30–50 words.
8. Multi-patch overwrite. When applying multiple patches to the same file in sequence, later patches can silently overwrite earlier ones. After applying 2+ patches to one file, re-read the file and verify all changes landed before reporting success.