| name | sales-devhunt |
| description | DevHunt platform help — open-source developer tool launch platform ('Product Hunt for developers'). Covers free submission (DR57-62 dofollow backlink), paid featured placement, GitHub-authenticated voting, weekly rankings, 25+ developer categories (DevOps, AI, CI/CD, API, Database, Open Source), newsletter promotion, and OSS Friends directory. Use when you want your dev tool listed on DevHunt, wondering if the DevHunt backlink is worth it, not sure how to get votes or featured placement, or deciding between DevHunt and other developer directories. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt launches (use /product-hunt-launch). |
| argument-hint | [describe what you need help with on DevHunt] |
| license | MIT |
| version | 1.0.2 |
| tags | ["sales","product-launch","startup","directory","developer-tools","platform"] |
| github | https://github.com/MarsX-dev |
DevHunt Platform Help
Helps the user submit to, optimize listings on, and get the most from DevHunt — an open-source developer tool launch platform built by developers for developers.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
-
What do you need help with?
- A) Submitting a developer tool to DevHunt
- B) Understanding the backlink value (DR57-62 dofollow)
- C) Getting featured ($49 promoted placement)
- D) Comparing DevHunt with other directories
- E) Optimizing my DevHunt listing for votes
- F) Something else — describe it
-
What's your product?
- A) Developer tool / CLI / SDK
- B) API / infrastructure service
- C) SaaS with developer audience
- D) Open-source project
- E) Something else
-
What's your primary goal?
- A) SEO backlinks (dofollow)
- B) Developer community visibility
- C) Early users and feedback from devs
- D) All of the above
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
Step 2 — Route or answer directly
If the request maps to a different skill, route:
- Multi-directory launch strategy →
/sales-launch-directory
- Product Hunt launch →
/sales-producthunt
- Email marketing to subscribers →
/sales-email-marketing
- Landing page optimization →
/sales-checkout
- Audience growth strategy →
/sales-audience-growth
- Other specific directory platforms → hand off to that platform's skill
Otherwise, answer directly from the DevHunt reference below.
Step 3 — DevHunt platform reference
Read references/platform-guide.md for the full platform reference — overview (DR/DA, backlink type,
categories, traffic), key features, the submission process, how DevHunt compares to peer directories, and
when it does and doesn't make sense.
Answer using only the relevant section. Don't dump the full reference.
