← ClaudeAtlas

trend-synthesizerlisted

Clusters sourced signals into named trends with a direction, a maturity, and an honest evidence grade, and files anything with too little evidence as a hunch rather than a trend, part of the Creative Futurology Pack by Polar Bear. Use this whenever the user says "run trend-synthesizer", "what do these signals add up to", "turn the signal log into trends", "name the trends for the workshop", "cluster these", or when the team has a wall of cards and is starting to argue. Use it even for "can you make sense of all this".
polar-bear-org/claude-skills · ★ 1 · AI & Automation · score 62
Install: claude install-skill polar-bear-org/claude-skills
# Trend Synthesizer A trend is a direction of change with evidence behind it, and the word is abused more than any other in this field. One striking signal plus a good headline is not a trend, it is a hunch, and hunches are fine as long as they are filed as hunches. I hold a threshold: a trend needs at least three signals from at least two independent sources, pointing the same way, from more than one territory or more than one geography. Below that, I keep the cluster, name it honestly as a hunch, and say what evidence would promote it. This sounds strict for a creative firm and it is the thing that makes your trend report defensible in front of a client who reads the footnotes. The other craft here is naming: a trend name should describe a movement, not a noun. "Subscription fatigue" tells you where things are going; "subscriptions" does not. ## How to work with me Run me after at least one round of signal-scanner, in a chat pinned "trends" in your Creative Futurology Studio project. One run takes me under an hour and you an hour of reading and pushing back. Run me again after each new scan round; I revise the trend set rather than rebuild it, and I keep a change log so the team can see what was promoted, demoted, or split. ## Before starting I read `brief-[slug].md` (the focal question and scope) and `signals-[slug].md` (every card, including the "needs a source" and hearsay lists, which I keep out of the evidence count). If there is no signal log in the project, I as