Your July 13 Show HN got 2 points. That number says nothing about demand — we went and checked. Every ask below is real, recent, and links to its source; most are still open to a reply from you today. Your launch wasn't the verdict — the room was just empty. These rooms aren't.
“The issue is that a lot of apps hard coded colors against the light background of the widgets. If you can find a solution for that, please share it.”
A literal, explicit ask — “please share it” — for a tool that finds hardcoded colors. The closest thing to a direct product request that exists.
“stylelint beeps you can’t just pass hex colors directly, that color is not in our design system, you need to write a design doc for custom color tokens and get approval from the frontend platform team, open a PR in their repo… ask in their slack channel for approve, ask their manager, wait.”
Works somewhere token enforcement is so heavyweight it’s a meme. TokenDrift’s lightweight audit is the antidote to exactly this bureaucracy.
“Prevent CSS from using hardcoded colors, spacing, or fonts outside the design token system. This is the first line of defense against ‘AI slop’ — generated UIs that use ad-hoc values instead of the system scale.”
Actively speccing ‘vibe design guardrails’ to block hardcoded values — TokenDrift’s exact job, framed around AI-generated CSS drift.
“harness validate runs the design-token drift linter (DRIFT-T001..T004) over every .ts/.tsx/.js/.jsx/.css/.scss file under the project root… In a real monorepo this produces thousands of unavoidable findings.”
A team that built its OWN drift linter (they use the word ‘drift’) and is now drowning in noise. Validated demand plus a free UX lesson: signal-to-noise is the product.
“Multiple components (Upgrade, Dashboard, Community, Chat, Users) used hardcoded hex colors and inline styles instead of the established SCSS variables and Material tokens. Styling should be centralized, adhering to the project’s design system.”
An OSS org manually cataloguing hardcoded-hex violations component by component — a TokenDrift scan produces this issue automatically. Zero comments so far.
“The cost of a weak design system isn’t just inconsistency anymore, it’s bad automation at scale. You should be constantly assessing whether it’s accurate enough to be trusted, because something is now going to generate against it thousands of times a month.”
Design-systems practitioner publicly arguing for continuous design-system auditing in the AI-codegen era — your strategic framing, said by your market.
“Linting Your Design Tokens — The What And The Why. Designers update Figma. Devs sync tokens. Users see issues. Catch the bugs before they ship – add linting to your toolset.”
Author of a 16-part design-tokens series who spent May–June writing specifically about token linting. The category’s educator — one genuine exchange with him reaches your whole market.
“When trying to use with stylelint v17: npm error ERESOLVE could not resolve… While resolving: stylelint-declaration-strict-value@1.10.11 Found: stylelint@17.0.0”
The canonical stylelint plugin for token enforcement keeps breaking on stylelint majors (a second issue followed in Feb). Its users are your warmest audience.
“Here I am with Claude Code… That so far generated a 2000-line CSS file for a 7000-line app consisting of literally three web pages. Where almost every single color, component, class and style is duplicated at least two times.”
AI coding tools are mass-producing hardcoded, duplicated styles — the fastest-growing source of drift. This is TokenDrift’s ‘why now’, in a stranger’s words.
Imagine it every Monday morning: where your buyers asked for your product last week, with reply-ready angles. Free while we onboard the first founders — just send your product URL.
Get a radar for your product →