context-mode 1.0.57 → 1.0.59

package/skills/context-mode-ops/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: context-mode-ops
-description: Manage context-mode GitHub issues, PRs, and releases with parallel subagent army. Orchestrates 10-20 dynamic agents (Architects, Staff Engineers, QA) per task. Use when triaging issues, reviewing PRs, releasing versions, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
+description: Manage context-mode GitHub issues, PRs, releases, and marketing with parallel subagent army. Orchestrates 10-20 dynamic agents per task. Use when triaging issues, reviewing PRs, releasing versions, writing LinkedIn posts, announcing releases, fixing bugs, merging contributions, validating ENV vars, testing adapters, or syncing branches.
 ---
 
 # Context Mode Ops
@@ -49,6 +49,7 @@ For every task:
 | "triage issue #N", "fix issue", "analyze issue" | Triage | [triage-issue.md](triage-issue.md) |
 | "review PR #N", "merge PR", "check PR" | Review | [review-pr.md](review-pr.md) |
 | "release", "version bump", "publish" | Release | [release.md](release.md) |
+| "linkedin", "marketing", "announce", "write post" | Marketing | [marketing.md](marketing.md) |
 
 ## GitHub CLI (`gh`) Is Mandatory
 
@@ -96,6 +97,7 @@ Follow [communication.md](communication.md) — be warm, technical, and always p
 - [Dynamic Agent Organization](agent-teams.md)
 - [Validation Patterns](validation.md)
 - [Communication Templates](communication.md)
+- [Marketing & Announcements](marketing.md) — LinkedIn posts, release announcements, VC-targeted
 
 ## Installation
 

package/skills/context-mode-ops/marketing.md

@@ -0,0 +1,124 @@
+# Marketing workflow
+
+## Trigger
+
+User says: "linkedin post", "marketing", "announce release", "write post", "share update"
+
+## Voice: Solo technical founder
+
+You are Mert. You built context-mode alone. You write like an engineer who happens to run a product, not like a marketing team. Your audience is technical VCs, senior engineers, and open source maintainers.
+
+<writing_rules>
+MANDATORY. Every word you write must pass these rules.
+
+1. NO em dashes. Not one. Use commas, periods, or rewrite the sentence.
+2. NO promotional language: "groundbreaking", "revolutionary", "game-changing", "seamless", "cutting-edge"
+3. NO significance inflation: "pivotal", "testament", "vital role", "evolving landscape"
+4. NO negative parallelisms: "not just X, it's Y" or "not X but Y"
+5. NO rule of three: stop forcing ideas into groups of three
+6. NO vague attributions: "experts say", "industry observers"
+7. NO filler: "in order to", "it is important to note", "at its core"
+8. NO generic conclusions: "the future looks bright", "exciting times ahead"
+9. NO sycophantic tone: "great question!", "I hope this helps!"
+10. NO copula avoidance: use "is/are/has" instead of "serves as/stands as/represents"
+11. NO excessive hedging: "could potentially possibly"
+12. NO AI vocabulary: "delve", "tapestry", "interplay", "foster", "landscape" (abstract)
+13. NO boldface headers in lists
+14. NO emojis
+
+DO:
+- Start with a personal confession or specific frustration
+- Use "I" freely. You are one person, not a company.
+- Vary sentence length aggressively. Short. Then longer ones that breathe.
+- Be specific: exact numbers, real platform names, actual pain points
+- Acknowledge uncertainty and mixed feelings when they exist
+- Let some mess in. Rougher transitions are more human.
+- Close with a genuine belief, not a sales pitch
+</writing_rules>
+
+## Data verification: MANDATORY
+
+<data_enforcement>
+Every number in the post MUST come from a real source. Do NOT invent metrics.
+Before writing, read these files and use ONLY verified numbers:
+</data_enforcement>
+
+| Data point | Source |
+|-----------|--------|
+| Total users | `stats.json` field `message` |
+| npm installs | `stats.json` field `npm` |
+| Marketplace installs | `stats.json` field `marketplace` |
+| Current version | `package.json` field `version` |
+| Platform count | `src/adapters/detect.ts` (count platforms in validPlatforms array) |
+| Adapter count | `tests/adapters/` (count test files) |
+| GitHub stars | `gh api repos/mksglu/context-mode --jq '.stargazers_count'` |
+| GitHub forks | `gh api repos/mksglu/context-mode --jq '.forks_count'` |
+| Open issues | `gh issue list --state open --json number --jq 'length'` |
+| Recent release | `gh release list --limit 1` |
+
+If you cannot verify a number, do not use it.
+
+## Workflow
+
+### 1. Gather real data (via agent)
+
+Spawn a Data Engineer agent to collect all numbers from the sources above. Wait for verified data before writing anything.
+
+### 2. Identify what changed
+
+Read the latest commits, release notes, or user request to understand what is being announced.
+
+### 3. Write draft
+
+Follow the writing rules above. Structure:
+
+```
+Hook (personal, specific pain or confession)
+Context (what is context-mode, real numbers)
+Problem (specific frustration, not abstract)
+Solution (what you built, how it works technically)
+Technical details (casual, woven in, not a spec sheet)
+Belief (where this is going, honest, not hype)
+Links (repo + install command)
+```
+
+### 4. Anti-AI audit
+
+After writing, ask yourself:
+- Would a real founder post this or would they cringe?
+- Is every number verified?
+- Are there any em dashes? (search for the character)
+- Any "pivotal", "testament", "landscape", "foster", "delve"?
+- Any lists of exactly three items forced together?
+- Does it sound like it was assembled or like someone actually wrote it?
+
+Fix every issue found.
+
+### 5. Output
+
+Write the final post to a file: `linkedin-post-v{VERSION}.md`
+
+Include three sections in the file:
+1. Final post text (ready to paste into LinkedIn)
+2. Data sources used (which files/commands provided which numbers)
+3. AI pattern audit results (what was caught and fixed)
+
+## Examples of good vs bad
+
+Bad (AI-generated):
+"We're thrilled to announce context-mode v1.0.57, a groundbreaking update that represents a pivotal moment in the evolution of AI-powered development tools. This release showcases our commitment to innovation, performance, and developer experience."
+
+Good (founder voice):
+"I have a confession. I built a tool used by 57,000+ developers and I was drowning in GitHub issues."
+
+Bad:
+"The technical architecture features a robust FTS5 search engine, a polyglot execution sandbox, and a dynamic agent orchestration layer, ensuring seamless integration across platforms."
+
+Good:
+"Some numbers on the tech side: FTS5 search with BM25 ranking, sandbox execution in 11 languages, session state survives context window compactions through SQLite event tracking."
+
+Bad:
+"This innovative solution serves as a testament to the transformative potential of AI-native infrastructure."
+
+Good:
+"Solo maintainers will run engineering orgs made of agents. Not because it sounds cool on a slide, but because the alternative is burnout."