lint vs Roo Code

Roo Code's planned feature set is a multi-agent workflow inside VS Code: orchestration across specialized agents, file editing, terminal control and command execution, Git integration for version-aware assistance, task routing rules, code review and optimization, and local processing for privacy with customizable model deployment. Autonomous mode is still coming soon, and the site offers only email updates and a contact form — no demo, no downloadable extension. @shadcn/lint attacks a much narrower slice with shipped functionality: contract-based rules where you declare what your design system permits, with shadcn/no-restyle applying per-component pattern, allow, and deny lists so a CardTitle can change typography while CardContent changes spacing, and shadcn/no-arbitrary-values keeping classes on your theme's spacing scale. Errors explain the violation and suggest a fix drawn from your own components, variants, and theme, with custom messages and contracts, category grouping for layout, spacing and typography, an agent-oriented setup prompt that reads SETUP.md, and both ESLint and Oxlint integrations. One is an unfinished general coding assistant; the other is a finished, design-system-specific linter.

Roo Code publishes no price. The listing is pricing_type: contact, and the product page is a pre-launch landing page with an email signup and contact form — no tier, no trial, no SLA. Budgeting for it today means budgeting for an unknown, and the not-for list explicitly warns off teams needing transparent pricing or SLAs. @shadcn/lint is free and open source, installable through ESLint or Oxlint, with no hosted service, dashboard, or CI product to pay for. If you need a cost you can put in a plan, only one of these gives you a number, and that number is zero. The trade-off for lint's free license is that it is a repo-level linter you maintain yourself, and it assumes a defined design system plus Tailwind v4 — v3 and earlier projects are explicitly unsupported.