convention.sh
Serves TypeScript coding conventions to AI agents via MCP to reduce token usage and improve code quality.
22 linking domains
Emerging
- For
- Developers using AI coding agents like Claude and Cursor to write TypeScript code
- Price
- Free plan · From $99/yrpricing page, read 2026-09-19
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Runs as
- API
- Reduce token usage and costs when generating TypeScript code
- Teach AI agents to follow coding conventions and best practices
- Pull coding rules on demand instead of stuffing prompts with guidelines
- #18
Kiro
Converts prompts into executable specifications and implements code with parallel agents that validate correctness.
32.7kActiveFrom $20/user/mo - #25
Devin
Executes software engineering tasks including code migrations, bug fixes, testing, and documentation generation across multiple repositories.
30.6kActiveFrom $20/mo - #27
Remy prompt
Builds websites, designs slides, and generates images through conversational AI.
30.9knot read— - #34
Nous Research
Trains and releases open source language models with infrastructure for distributed training.
33.7knot read— - #40
Replit
Builds and deploys web apps, websites, and agents from natural language descriptions.
278knot readFrom $20/mo - #43
Lovable
Builds production-grade web and mobile applications from natural language descriptions.
198knot readFree plan2023
What is convention.sh?
Serves TypeScript coding conventions to AI agents via MCP to reduce token usage and improve code quality.
Who is convention.sh for?
Developers using AI coding agents like Claude and Cursor to write TypeScript code
How much does convention.sh cost?
convention.sh has a free plan; paid plans start at $99/yr, per its pricing page on 2026-09-19.
Do people use convention.sh?
Emerging.
Is convention.sh still maintained?
Maintained.
What are alternatives to convention.sh?
In Developer tools, by use: Kiro, Devin, Remy prompt, Nous Research, Replit, Lovable.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.