+ notes app. +
diff --git a/.claude/skills/social-post/SKILL.md b/.claude/skills/social-post/SKILL.md index 47111e2..cc08c13 100644 --- a/.claude/skills/social-post/SKILL.md +++ b/.claude/skills/social-post/SKILL.md @@ -1,100 +1,214 @@ --- name: social-post -description: Generate a paper-and-ink carousel HTML post for the inode project, focused on story and meaning rather than feature pitches. Use when the user wants to share what the project is FOR, who it's FOR, or why it exists — not what it does or what's coming next. +description: Generate a paper-and-ink carousel HTML post for the inode project, in the voice of a developer talking to other developers — dry wit, real code, opinionated takes, and visual variety (terminal blocks, architecture sketches, stack callouts). Use when the user wants to share what the project is and convince a developer to spend 5 minutes on it. NOT for marketing pitches and NOT for plain philosophy essays. --- -# Social post generator (story-style) +# Social post generator (developer-blog style) ## What this skill is for -Generate a 1080×1080 carousel HTML in `social/` for posts about *meaning* — -what the tool exists for, who it's for, why anyone would care. The reader -is the protagonist; the project is the supporting character. +A post a developer reads through because: + +1. They recognize the pain in the first 2 pages. +2. The author shows technical chops fast (real code, real stack, real + commands). +3. They can *see* the thing working (terminal output, architecture). +4. The voice has personality — dry wit, opinions, mild sarcasm — without + being a marketing pitch or a beige philosophical essay. + +If a developer would close the tab thinking *"yeah, I'd actually try +this,"* the skill did its job. ## What this skill is NOT for -- **Dev logs / debugging stories** → write manually using `social/day-2-debug-and-ship.html` as the model -- **Feature launches / roadmaps** → use `social/post-templates.html` as the model -- **Technical breakdowns** → not the right tone - -If the user asks for one of those, decline this skill and offer the -manual path instead. - -## Process - -1. **Get the angle.** Ask the user in one sentence who the reader is — - not the demographic ("developers"), the *moment* ("the dev who lost a - stripe key at 11pm"). Skip if they've already given it. If they say - "you decide," default to: *the engineer who has 7 untitled notes apps, - none trusted.* - -2. **Read the design system.** Open `social/post-templates.html` and - `social/day-2-debug-and-ship.html`. Reuse verbatim: - - The entire ` + +
+ +