Architecture linter built specifically for AI-written code
Build a lightweight architecture linter that scans codebases generated or edited by AI coding assistants (Cursor, Claude, Copilot) for structural smells that LLMs commonly introduce: duplicated logic, circular dependencies, inconsistent layering, dead abstractions. Sell it as a CLI tool or CI/pre-commit check with a hosted dashboard, targeted at solo developers and small teams shipping fast with AI-generated code.
What to build
A CLI + hosted dashboard that scans AI-assisted codebases (Cursor, Claude, Copilot) for LLM-typical architecture smells: duplicated logic, circular dependencies, inconsistent layering, dead abstractions. Targeted at solo devs and small teams shipping fast with AI-generated code, as a pre-commit/CI check plus a visual dashboard to track architecture drift over time.
AI coding assistants ship fast but introduce a distinct pattern of structural debt; a dedicated linter for that debt is a narrow but real niche, as shown by RepoGuard's Show HN launch.
Demand
Solo developers and small teams using Cursor/Claude/Copilot to ship quickly are accumulating architecture debt faster than they can review it, and existing linters aren't tuned to catch AI-specific smells like duplicated logic or dead abstractions.
- Hacker NewsLaunch post
Show HN: RepoGuard – Architecture linter for AI-generated code (Cursor, Claude) — 3 points, 0 comments on HN.
- Hacker NewsLaunch post
Low initial traction (3 points, 0 comments) suggests early-stage, unproven demand rather than a validated rush of interest.
Stack
- Tree-sitter
- dependency-cruiser
- madge
- Node.js CLI (Commander/oclif)
- Supabase (dashboard + auth)
- GitHub Actions API
Solo + AI difficulty
Parsing and dependency-graph analysis across multiple languages is the hard part; a single-language (e.g. TypeScript/JS) CLI with basic circular-dependency and duplication checks is achievable in 1-2 weeks using existing graph/AST libraries. The hosted dashboard and CI integration add another 1-2 weeks.
- Entry threshold
- Buildable solo in weeks using existing static analysis libraries plus custom rules; low capital needed, main cost is time to tune rules against real AI-generated codebases and avoid false positives.
- Window
- 6-12 months
Where to find first users
- Show HN relaunch with clearer traction proof
- r/ClaudeAI and r/cursor communities
- Cursor/Claude Discord servers
- Indie Hackers and Product Hunt launch
Competitors
Counter-signals & risks
Cursor, Anthropic, and GitHub could build equivalent architecture-smell detection directly into their coding assistants, removing the need for a standalone third-party tool.
General-purpose static analysis tools (dependency-cruiser, SonarQube, ESLint plugins) can likely be reconfigured to catch the same smells without a new dedicated product.
The core claim that LLM-generated code has a distinct, consistent 'smell signature' is asserted in marketing but not independently validated with data.
The Show HN launch itself got minimal traction (3 points, 0 comments), which is weak evidence of real market pull.
Original title: Show HN: RepoGuard – Architecture linter for AI-generated code (Cursor, Claude)
Related signals
- Developer tools#4
MCP Connector Library for AI Coding Agents
Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.
Demand7/10est.Buildability7/10est.Competition7/10est.via Product Hunt22 competitors - Developer tools#7
Plan State Persistence Layer for Claude Code Re-Runs
Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.
Demand6/10est.Buildability8/10est.Competition8/10est.via Product Hunt11 competitor - Developer tools#8
Developer Context Save and Restore Tool as Micro-SaaS
Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.
Demand1/10measuredBuildability7/10est.Competition6/10est.via Hacker News33 competitors