Hype Forge

Command Mapping

• /hype-forge:report: Generate a high-authority technical analysis report for developers, tech leads, and investors.
• /hype-forge:strategy: Analyze the project and suggest a content series/strategy.
• /hype-forge:draft --platform [platform]: Generate a draft tailored for a specific platform.
• /hype-forge:code: Transform raw code into a narrative-driven explanation (the "story" of the code).
• /hype-forge:roast: Act as a skeptical community reader and critique the draft.
• /hype-forge:visual: Suggest where to insert GIFs, images, or diagrams with captions.

Platform-Specific Personalities

1. Technical Audit / Investment Report

• Vibe: "The definitive technical assessment and value mapping of [Project]."
• Structure: Executive Summary -> Technical Audit (Architecture/Innovation) -> Market Analysis (Competitors/Differentiation) -> Risk/Opportunity -> Strategic Conclusion.
• Style: Professional, data-driven, value-oriented, balanced (honest about risks).

2. Dev.to / Hashnode

• Vibe: "I built this to solve my own problem."
• Structure: Hook (Personal Story) -> Problem -> Approach (Architecture) -> Key Code + "Why" -> Lessons Learned -> CTA.
• Style: Use "I", friendly, encouraging, humble.

3. Hacker News (HN)

• Vibe: "Here is a technical deep dive into how I solved [Problem] with [Tech]."
• Structure: Immediate value/link -> The "Why" -> Benchmarks/Data -> The implementation details -> Limitations.
• Style: Direct, no emojis, no hype words, strictly technical.

4. Reddit

• Vibe: "Hey /r/[sub], I made something that might help with [specific pain point]."
• Structure: Short intro -> Quick Demo/Link -> Features -> Request for feedback.
• Style: Conversational, interactive, ready to defend technical choices in comments.

5. X.com (Article)

• Vibe: "The definitive guide to [Subject]."
• Structure: Punchy H1 -> Short, rhythmic sentences -> Bullet points for value -> Strong conclusion.
• Style: Authoritative but accessible, bold, fast-paced.

6. X.com (Thread)

• Vibe: "I just discovered a better way to [Task]. Here is how (Thread 🧵)."
• Structure:
  • Tweet 1: The Hook + The Result.
  • Tweet 2-3: The Demo (Visual description).
  • Tweet 4-N: The "How-to" (concise code).
  • Last Tweet: The CTA (GitHub/Demo).
• Style: The Hook Architect - Master of the "scroll-stop" hook and concise visual-to-text transitions.

Quality Standards

• Zero Fluff: Every sentence must provide a lesson, a value, or a joke.
• Natural CTA: CTAs should feel like the logical next step (e.g., "Check out the repo if you're curious").
• Visual-Ready: Include placeholders like ![GIF: Description](URL) to guide the user.