mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-10 03:13:29 +08:00
4813ed753f
Ports functionality from 10+ separate plugins into ECC so users only need one plugin installed. Consolidates: pr-review-toolkit, feature-dev, commit-commands, hookify, code-simplifier, security-guidance, frontend-design, explanatory-output-style, and personal skills. New agents (8): code-architect, code-explorer, code-simplifier, comment-analyzer, conversation-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer New commands (9): commit, commit-push-pr, clean-gone, review-pr, feature-dev, hookify, hookify-list, hookify-configure, hookify-help New skills (8): frontend-design, hookify-rules, github-ops, knowledge-ops, lead-intelligence, oura-health, pmx-guidelines, remotion Enhanced skills (8): article-writing, content-engine, market-research, investor-materials, investor-outreach, x-api, security-scan, autonomous-loops — merged with personal skill content New hook: security-reminder.py (pattern-based OWASP vulnerability warnings on file edits) Totals: 36 agents, 69 commands, 128 skills, 29 hook scripts
157 lines
5.1 KiB
Markdown
157 lines
5.1 KiB
Markdown
---
|
|
name: content-engine
|
|
description: 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.
|
|
origin: ECC
|
|
---
|
|
|
|
# Content Engine
|
|
|
|
Turn one idea into strong, platform-native content instead of posting the same thing everywhere.
|
|
|
|
## When to Activate
|
|
|
|
- writing X posts or threads
|
|
- drafting LinkedIn posts or launch updates
|
|
- scripting short-form video or YouTube explainers
|
|
- repurposing articles, podcasts, demos, or docs into social content
|
|
- building a lightweight content plan around a launch, milestone, or theme
|
|
|
|
## First Questions
|
|
|
|
Clarify:
|
|
- source asset: what are we adapting from
|
|
- audience: builders, investors, customers, operators, or general audience
|
|
- platform: X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform
|
|
- goal: awareness, conversion, recruiting, authority, launch support, or engagement
|
|
|
|
## Core Rules
|
|
|
|
1. Adapt for the platform. Do not cross-post the same copy.
|
|
2. Hooks matter more than summaries.
|
|
3. Every post should carry one clear idea.
|
|
4. Use specifics over slogans.
|
|
5. Keep the ask small and clear.
|
|
|
|
## Platform Guidance
|
|
|
|
### X
|
|
- open fast
|
|
- one idea per post or per tweet in a thread
|
|
- keep links out of the main body unless necessary
|
|
- avoid hashtag spam
|
|
|
|
### LinkedIn
|
|
- strong first line
|
|
- short paragraphs
|
|
- more explicit framing around lessons, results, and takeaways
|
|
|
|
### TikTok / Short Video
|
|
- first 3 seconds must interrupt attention
|
|
- script around visuals, not just narration
|
|
- one demo, one claim, one CTA
|
|
|
|
### YouTube
|
|
- show the result early
|
|
- structure by chapter
|
|
- refresh the visual every 20-30 seconds
|
|
|
|
### Newsletter
|
|
- deliver one clear lens, not a bundle of unrelated items
|
|
- make section titles skimmable
|
|
- keep the opening paragraph doing real work
|
|
|
|
## Repurposing Flow
|
|
|
|
Default cascade:
|
|
1. anchor asset: article, video, demo, memo, or launch doc
|
|
2. extract 3-7 atomic ideas
|
|
3. write platform-native variants
|
|
4. trim repetition across outputs
|
|
5. align CTAs with platform intent
|
|
|
|
## Deliverables
|
|
|
|
When asked for a campaign, return:
|
|
- the core angle
|
|
- platform-specific drafts
|
|
- optional posting order
|
|
- optional CTA variants
|
|
- any missing inputs needed before publishing
|
|
|
|
## Content Types by Platform
|
|
|
|
### X/Twitter Content Mix
|
|
|
|
| Type | Frequency | Example |
|
|
|------|-----------|---------|
|
|
| Educational/tips | 3-4/week | "5 mistakes with [tool]", model selection, config tips |
|
|
| News/commentary | 2-3/week | CVE breakdowns, industry news, product launches |
|
|
| Milestones | 1-2/week | Star counts, test counts, download numbers |
|
|
| Personal/journey | 2-3/week | Builder life, founder diary, lessons learned |
|
|
| Ship logs | 2/week (weekends) | "sunday ship log: [list]" |
|
|
| Engagement bait | 1-2/week | "what's one thing you want [product] to do better?" |
|
|
|
|
### Engagement Bait Formats
|
|
- "what's your [X]?" (config sharing, stack sharing)
|
|
- "hot take: [contrarian opinion]" (disagreement drives engagement)
|
|
- "[thing] vs [thing]. go." (tribalism)
|
|
- "what am I missing?" (vulnerability + question)
|
|
|
|
### Viral Mechanics
|
|
- Large specific numbers: "1,184 malicious AI plugins"
|
|
- Security scares: "your AI has access to your SSH keys"
|
|
- Zero-X framing: "zero marketing budget. zero ads. just useful open source."
|
|
- Before/after comparisons: default vs configured
|
|
- Personal vulnerability: "ran the scan on my own config. grade B."
|
|
- Contrarian takes: "stop using [expensive thing] for everything"
|
|
|
|
### TikTok Script Structure
|
|
```
|
|
HOOK (0-3s): [visual/verbal pattern interrupt]
|
|
PROBLEM (3-10s): [what's broken, what people don't know]
|
|
SOLUTION (10-40s): [demo, walkthrough, the thing]
|
|
CTA (40-60s): [what to do next]
|
|
```
|
|
|
|
### YouTube Script Structure
|
|
- Hook (first 15s): Show the result, then explain how
|
|
- Intro (15-30s): Who you are, what this covers, why it matters
|
|
- Chapters (2-3 min each): One concept per chapter, new visual every 30 seconds max
|
|
- Outro: Clear CTA (star repo, subscribe, try product)
|
|
- Description: first 2 lines matter (above fold), include links, chapters
|
|
|
|
## Content Recycling Flow
|
|
|
|
```
|
|
YouTube (highest effort)
|
|
-> Newsletter (long-form written adaptation)
|
|
-> LinkedIn (professional 3-takeaway version)
|
|
-> X/Twitter (atomic tweet units)
|
|
-> TikTok (15-60s visual snippet)
|
|
```
|
|
|
|
Adapt, don't duplicate. Each platform version should feel native.
|
|
|
|
## Posting Schedule
|
|
|
|
| Slot | Time | Content Type |
|
|
|------|------|-------------|
|
|
| Morning (7-8am) | - | Primary: educational, technical, news |
|
|
| Midday (11:30am-12:30pm) | - | Engagement: question, hot take, QT |
|
|
| Evening (5-6pm) | - | Secondary: ship log, personal, lighter |
|
|
| Throughout day | - | 5-10 replies to relevant accounts |
|
|
|
|
## Quality Gate
|
|
|
|
Before delivering:
|
|
- each draft reads natively for its platform
|
|
- hooks are strong and specific
|
|
- no generic hype language
|
|
- no duplicated copy across platforms unless requested
|
|
- the CTA matches the content and audience
|
|
- no hashtags on X (they signal inauthenticity on dev X)
|
|
- no links in X tweet body (kills reach)
|
|
- hook in first 7 words (X) or first line (LinkedIn)
|
|
- numbers are specific and sourced
|
|
- at least one parenthetical aside per post for personality
|