everquint

You can scaffold and rebrand design token themes, add dark mode, audit hardcoded styles, enforce a TypeScript lint and testing standard, run branch-to-release delivery with rollback, create and execute Linear issues, and query a pre-indexed code knowledge graph for dependency and blast-radius questions.

Frontend engineers and technical leads standardizing TypeScript repositories, plus PMs and developers collaborating through Linear. The skills suit teams enforcing quality gates, accessibility, performance budgets, and consistent commit, PR, and release conventions across primary and subagent contributors.

The delivery workflow defines branch model, commits, PRs, review, merge, release, and rollback with a pre-push gate. Prototype mode applies a reduced gate set for throwaway repos with expiry dates, including a graduation path back to the full standard once a prototype gains users.

No. The codegraph skill is explicitly optional and recommended, not a required part of the standard. It answers structural questions like callers, callees, and blast radius in one call; for exhaustive find-every-occurrence searches, grep or ripgrep remains the recommended approach.

It covers the non-lintable half of quality: tests with diff-coverage gates, error reporting, performance and bundle budgets, accessibility verification, and client-side security reviews of untrusted HTML and secret handling. These complement the lint rules and correctness gates in the TypeScript standard.