A
Front-End-Checklist
92.7
74,760 stars · MIT
AI Agents
taste-skill leads by 4.7 · narrow
A
92.7
74,760 stars · MIT
B · leads
97.4
117,459 stars · MIT
Front-End-Checklist versus taste-skill is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Front-End-Checklist is written mainly in MDX; taste-skill is written mainly in JavaScript. The composite score is 92.7 for Front-End-Checklist and 97.4 for taste-skill.
taste-skill has 117,459 GitHub stars to Front-End-Checklist's 74,760, a gap of 42,699 (1.57×). Forks are 6,781 for Front-End-Checklist and 7,858 for taste-skill. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 98 versus 100.
Push history: Front-End-Checklist was last pushed on 31 October 2026 (17 days ago), and taste-skill was last pushed on 08 November 2026 (8 days ago). Open issues stand at 22 for Front-End-Checklist (0.000 per star) and 10 for taste-skill (0.000 per star). Issue-health scores are 96 and 96; activity scores are 78 and 92.
Both Front-End-Checklist and taste-skill are listed as MIT. A permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In AI Agents, both Front-End-Checklist (74,760 stars) and taste-skill (117,459 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Front-End-Checklist is open source, taste-skill is open source.
taste-skill is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 14 points (78 vs 92), and the tightest is self-hosting at 0 points (100 vs 100).
taste-skill finishes ahead at 97.4 against Front-End-Checklist at 92.7, a 4.7 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Front-End-Checklist | taste-skill |
|---|---|---|
| GitHub stars | 74,760 | 117,459 |
| Forks | 6,781 | 7,858 |
| Open issues | 22 | 10 |
| Adoption | 96 | 100 |
| Activity | 78 | 92 |
| Community | 98 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.7 | 97.4 |
🗂 The essential checklist for modern web development, for humans and AI agents
Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
taste-skill has more GitHub stars: 117,459 versus 74,760 for Front-End-Checklist. The gap is 42,699 stars.
taste-skill was pushed more recently: 08 November 2026 versus 31 October 2026 for Front-End-Checklist. That is 9 days apart.
Yes. This catalog marks both Front-End-Checklist and taste-skill as self-hostable. Confirm each project's deploy docs before you plan a migration.
Front-End-Checklist is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. taste-skill is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
taste-skill scores 97.4 and Front-End-Checklist scores 92.7. This page calls that a narrow lead for taste-skill.