RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Design Tokens] Support W3C DTCG compliant JSON format

The plugin's JSON output for design tokens is not compliant with the W3C DTCG specification. The user requests that properties like $type, $value, and $description be used as per the standard to avoid conflicts with token names.

Original Source

@@Pi0up | 0 pts | 11/24/2025

Hi, Great plugin but as your refer to [W3G DTCG](https://www.w3.org/groups/cg/design-tokens/) JSON files are not compliant see [module page](https://www.designtokens.org/tr/drafts/format/#composite-design-token) Expected "$type": "borderRadius", "$value": "2px" "$description": "something" The $ makes sure that properties defined by the spec do not conflict with any token names you might create. [source](https://www.designtokens.org/tr/drafts/format/#character-restrictions)

Discussion

Loading comments...