AI-friendliness benchmark for JS frameworks

What to build

A CLI (plus optional VS Code extension) that scans a frontend repo and scores it on 'AI token-cost efficiency' — boilerplate volume, generated file count, component tree depth — then outputs a report with specific refactors to cut AI-assistant context cost. Paired with a public leaderboard ranking React, Vue, Svelte, and HTMX on the same metric.

Nolan Lawson's viral post proved there's a real, measurable gap in how much context different frameworks force AI coding assistants to chew through — a scoring tool turns that into a stack-selection decision aid.

Demand

Solo builders and small teams now choosing stacks specifically for AI-assisted development want a concrete number to justify framework choice, and the HN thread shows this resonated far beyond the original author's niche.

• Hacker NewsDemand

  'The AI cost of JavaScript frameworks' hit 313 points and 231 comments on HN, indicating high engagement with the idea of measuring framework AI-friendliness.

Stack

• Node.js CLI (commander/oclif)
• tiktoken or similar tokenizer libs
• ts-morph / AST parsers per framework
• GitHub Actions for repo scanning
• VS Code Extension API
• Next.js static site for the public leaderboard

Solo + AI difficulty

The AST parsing and token-counting mechanics are straightforward with existing tokenizer libraries; the hard part is defining a scoring methodology that holds up under scrutiny across very different framework architectures. MVP (CLI scanning one framework, basic token counts) is doable in 1-2 weeks; a credible multi-framework leaderboard takes longer and invites pushback.

Entry threshold

A solo builder can ship a CLI that measures token counts, file counts, and context needed per framework scaffold within a couple of weeks; main effort is building credible benchmarks and keeping them updated as frameworks and models change.

Window

6-12 months

Where to find first users

• Hacker News launch (Show HN)
• r/webdev and r/reactjs
• Twitter/X dev community referencing the original post
• Product Hunt launch

Counter-signals & risks

• Token/context cost may be dominated by codebase size and architecture choices within a framework rather than the framework itself, making cross-framework scoring noisy or misleading.

• Modern AI coding assistants increasingly use larger context windows, retrieval, and caching, which could shrink the relevance of 'AI-friendliness' as a framework selection criterion over time.

• Teams typically choose frameworks based on hiring, ecosystem, and performance needs; AI-assistant token cost is unlikely to be a primary driver of stack decisions, limiting market size and willingness to pay.