菜单
Creates VALUE content: blog posts, tutorials, articles, educational material, onboarding/lifecycle emails. Goal = build trust and attract audience. Triggers ONLY when: user asks to create content, write an article, or prepare educational material. Do NOT trigger when: writing code documentation, README files, landing page copy, or ad copy.
| name | content-create |
| description | Creates VALUE content: blog posts, tutorials, articles, educational material, onboarding/lifecycle emails. Goal = build trust and attract audience. Triggers ONLY when: user asks to create content, write an article, or prepare educational material. Do NOT trigger when: writing code documentation, README files, landing page copy, or ad copy. |
This skill (content-create) = VALUE content. Goal is to build trust and attract audience. Covers: blog posts, tutorials, articles, educational material, onboarding email sequences (welcome, activation, value delivery, social proof), and platform-specific content.
Not this skill — use copy-craft instead for CONVERSION copy: landing pages, CTAs, ad copy, microcopy, sales/upgrade/win-back emails. Goal there is to get someone to ACT.
Use "They Ask, You Answer" (Marcus Sheridan). Every piece of content must answer a REAL question the target audience is already asking.
Prioritize the Big 5 content types:
Action: Ask the user what question they want to answer. If unclear, search the web for common questions in the target niche using forums, Reddit, Quora, and "People Also Ask" on Google.
For email sequences that educate and build trust (not sell), use this structure (source: Encharge, HubSpot):
| Timing | Purpose | Subject line rule | |
|---|---|---|---|
| Welcome | Instant | Confirm signup, set expectations, one quick-win action | Use their name + what they just did |
| Activation | Day 1 | Guide to first meaningful action (Time to First Value) | Verb + specific outcome ("Create your first X") |
| Value delivery | Day 3 | Show what's possible, share a power-user tip | Question format ("Did you know you can...?") |
| Social proof | Day 7 | Customer story with specific results | Name-drop or result number in subject |
For upgrade/sales/win-back emails, use copy-craft.
Each platform has specific constraints. Match format to platform:
| Platform | Format | Length | Style |
|---|---|---|---|
| Dev.to / Hashnode | Technical tutorial | 800-1500 words | Code blocks, step-by-step, practical outcomes |
| Medium | Narrative essay | 1000-2000 words | Storytelling, personal experience, clear takeaways |
| Twitter/X | Thread | 5-10 tweets | Data-driven, opinionated, one idea per tweet |
| Professional insight | 300-500 words | Lessons learned, career relevance, formatted for mobile | |
| Answer-format | 200-800 words | Genuinely helpful, zero self-promotion in the post body | |
| Hacker News | Show HN only | Brief description | Working product required, factual, non-promotional |
| Blog (SEO) | Long-form guide | 1500-3000 words | Topic cluster model, keyword-optimized |
Action: Confirm platform with user before writing. If blog/SEO, identify the target keyword first.
This is the most common failure mode. Content must use the CUSTOMER'S vocabulary, not the developer's.
Rules:
If the content targets search traffic:
Use web search to verify keyword volume and competition before committing to a keyword.
Before delivering the content, verify ALL of the following:
If any check fails, rewrite the failing section before delivering.
After content is created and approved, store in memory/content_log.md:
This builds a content library for future reference and prevents duplicate topics.
When publishing to API-allowed platforms (Dev.to, Medium, Hashnode):
For platforms where automation is NOT allowed (Reddit, HN): draft the content in a local file and instruct the user to post manually.
Report to user: "Content created: [title]. Platform: [target]. Word count: [N]"
Suggested next steps (user decides):
Reviews code quality before staging. Triggers ONLY when: implementation of a feature or fix is complete and code is ready to stage. Do NOT trigger after every small edit — only when a logical unit of work is done.
Evaluates business viability for a new product idea. Triggers ONLY when: the user asks to evaluate a business idea, asks what product to build, or says to run biz-think. Do NOT trigger when: discussing business concepts in passing, talking about existing product improvements, or during development work.
Prints the complete SOP flowchart. Triggers when: user asks to see the SOP, asks 'where are we?', asks 'what's next?', or says '/sop'. Always available.
Runs iterative hypothesis validation loop. Triggers ONLY when: biz-think acid test fails, user explicitly asks to validate a business assumption, or user says to pivot. Do NOT trigger when: discussing business strategy casually or during product development.
Develops brand positioning and Build in Public strategy. Triggers ONLY when: user asks to define brand, plan Build in Public content, or establish positioning. Do NOT trigger during development or content creation for specific pieces.
Manages community presence and engagement strategy. Triggers ONLY when: user asks to find communities, plan community engagement, or draft community responses. Do NOT trigger when: creating content (use content-create) or distributing content (use content-distribute).
