Identify Your Top Developer Trends

Use this prompt, replacing [COMPANY] with your company name:

I need to decide which developer trends [COMPANY] should map to this month.

Use the Plushcap MCP tools to research the company and current developer trends before making recommendations. Show the actual dates, counts, and calculations behind the ranking. Do not rely on general knowledge when Plushcap data is available.

First, resolve the correct company in Plushcap. Review its description and its blog posts from the last 90 days to understand its products, technical strengths, recent launches, and themes it already discusses. Do not assume a product capability that the evidence does not support.

Next, pull 16 weeks of data for all tracked developer trends. Treat the current week as incomplete unless it has ended, and exclude incomplete weeks from comparisons. For every serious candidate, measure:

• Current size: total mentions during the latest four complete weeks, along with the latest complete week's mention count and company count.
• Recent momentum: the percentage change in average weekly mentions for the latest four complete weeks versus the preceding four complete weeks, supported by the latest complete week-over-week change.
• Durability: whether growth appears across multiple complete weeks or is only a one-week spike.
• Company fit: how directly the trend connects to [COMPANY]'s documented products, expertise, audience, and recent work.

If the earlier comparison period has zero mentions, label the candidate as new or emerging instead of reporting an infinite growth rate.

Investigate the strongest candidates with their individual trend data and recent matching blog posts. For each finalist, identify the companies publishing relevant work, then inspect recent Hacker News submissions for [COMPANY] and at least five of those companies when the data allows it. Count submissions from the last 30 days whose titles or URLs clearly relate to the trend, and report their total points plus up to three representative titles, dates, and point counts. Reject incidental keyword matches. Do not treat a company's general Hacker News activity as evidence for a trend, and do not imply that full Hacker News discussion text was searched if Plushcap only provided submission metadata. Keep submissions with missing point values separate instead of treating those points as zero.

Score each trend out of 100 using these weights:

• 30 points for sustained recent momentum.
• 25 points for current size and breadth across companies.
• 20 points for relevant Hacker News recency and engagement.
• 25 points for credible fit with [COMPANY].

Normalize each component across the candidate set and explain the scoring method. Do not let a huge percentage increase from a tiny base outrank a meaningfully large trend without calling out that tradeoff. Do not recommend a large but shrinking trend merely because it is popular. If Hacker News evidence is absent or the sample is small, say so and lower confidence rather than filling the gap with assumptions.

Return:

1. A short research audit listing the Plushcap tools used, analysis date, date windows, and any incomplete period or missing data.
2. A comparison table with the top 10 candidates. Include rank, weighted score, four-week mentions, latest complete-week company count, four-week growth, latest week-over-week change, relevant 30-day Hacker News post and point totals, company-fit score, and confidence.
3. The five trends [COMPANY] should map to this month. For each, explain the evidence, the specific connection to the company, a differentiated angle it can credibly own, and one concrete action for this month such as a technical article, benchmark, demo, launch narrative, or community contribution.
4. A "do not chase yet" watchlist of three trends that are rising too fast from a small base, are large but losing momentum, lack Hacker News confirmation, or do not fit the company. State what evidence would change the decision.

Rank by the combined evidence, not by raw growth rate or total size alone.

You should get a prioritized list that separates durable opportunities from short-lived spikes and explains why each trend is relevant to your company.